Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalizations in “States of the type attribute” #7162

Closed
j9t opened this issue Oct 5, 2021 · 4 comments
Closed

Generalizations in “States of the type attribute” #7162

j9t opened this issue Oct 5, 2021 · 4 comments

Comments

@j9t
Copy link
Contributor

j9t commented Oct 5, 2021

4.10.5.1, “States of the type attribute” goes through all the different input types. However, close to each state has a sentence starting with “The input element represents a…”, where what really seems to be meant is “This input element [type] represents a…”. That is, these sentences seem to generalize what really only relates to the specific type of input.

For example, 4.10.5.1.3 says “The input element represents a control for editing a telephone number given in the element's value.” This looks like a statement about the input element in general, and is false.

It seems by switching to “This…” all of these cases could be made clearer. (I’d be happy to prepare a PR.)

@Kaiido
Copy link
Member

Kaiido commented Oct 5, 2021

No, it is not the type that does represent [xxx] it's the "input element" whose type is in [yyy] state.
E.g

When an input element's type attribute is in the Telephone state, the rules in this section apply.

The input element represents a control for editing a telephone number given in the element's value.

Here it says that with <input type=telephone>, this input element will represent a control for editing a telephone number [...].

@j9t
Copy link
Contributor Author

j9t commented Oct 6, 2021

I’m not sure what you’re suggesting, as you’re ending up emphasizing how “this” could be clearer.

An addition to the original suggestion, if we feel even more clarity could be useful, we could also spell each case out entirely, as in “An input element with the type tel …”. That would solve the problem of “The input element …” reading like it was meant in general.

@Kaiido
Copy link
Member

Kaiido commented Oct 6, 2021

"This" here would refer to the state the type attribute.
"The" is the proper term to refer to this input element, i.e "the" one we defined above, whose type we're discussing. I don't see how the current text is confusing.
Repeating "An input element ..." seems to only add redundancy, and I think this would introduce confusion.

@j9t
Copy link
Contributor Author

j9t commented Oct 6, 2021

"This" here would refer to the state the type attribute.
"The" is the proper term to refer to this input element

“The” is not the proper term for “this”, because then “the” would be called “this”.

I don’t understand the resistance against even smallest changes, but I will not comment on this. If you and the group don’t want it, discard it. I’m not here to argue.

@domenic domenic closed this as completed Oct 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants