Closed AlexLloyd0 closed 3 years ago
Makes sense to me to add "or a missing or invalid type", but I think the type
attribute should still be first, even though it may lead to slightly awkward language. The consistency makes it easier for a person scanning the document to find what they are looking for.
@scottaohara Do you agree?
OLD
input type=text, with no list attribute
NEW
input with no list attribute, and with type=text, or a missing or invalid type.
NEW with type first
input type=text or a missing or invalid type, with no list attribute
OLD
input type=text, search, tel, url, or email with a list attribute
NEW
input with a list attribute and with type=text, search, tel, url, email, or a missing or invalid type.
NEW with type first
input type=text, search, tel, url, email or a missing or invalid type, with a list attribute
@carmacleod yes, would prefer the type staying first. that was my initial reaction to reviewing the PR prior to seeing your additional comment. But at a high level, agree this clarity is helpful here.
cc @AlexLloyd0
Fair point, I was optimising for local readability rather than global consistency. Updated to the suggested wording :)
According to https://html.spec.whatwg.org/multipage/input.html,
type=text
is both themissing value default
and theinvalid value default
.Preview | Diff