Should “Naming form controls” section include a warning about names overriding form properties? #2720
Labels
clarification
Standard could be clearer
good first issue
Ideal for someone new to a WHATWG standard or software project
topic: forms
Example:
This will effectively break all the corresponding form properties, e.g.
form.tagName
will refer to the input, instead of returning"FORM"
. This can cause bugs, so I’m wondering if the spec should actively warn against this.Maybe it would make sense to add a warning to the “Naming form controls” section, to make sure that authors don’t create form controls with names that would collide with built-in form properties.
The text was updated successfully, but these errors were encountered: