-
Notifications
You must be signed in to change notification settings - Fork 127
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
removed references to <range> #1652
Conversation
<range> is not currently in html.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
other roles that reference their HTML input counterpart include the type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
@michael-n-cooper not sure how the IPR resolution works. Can I just click the 'mark as non-substantive' link on the repo-manager page linked above? (Also do we ignore the gh-page issue?) |
Yes - if it doesn't impact normative text then you can mark as non-substantive |
Ideally no - it should build and I don't know why this is failing right now. @michael-n-cooper ? |
I think this should now be fixed (via #1648) |
Thanks! |
pkra marked as non substantive for IPR from ash-nazg. |
@estelle to rebase the branch or can we go ahead and merge this one? |
This is simple enough that I think we can just merge it |
I think that was correct -- the merged commit didn't fail. |
Replaces references to `<range>` (not currently in html) with references to `<input type="range">` Co-authored-by: Estelle Weyl @scottaohara
<range>
is not currently in HTML.min, max, and value are attributes in input, meter, and progress.
changed the related concept for aria-valuemin, aria-valuemax, and aria-valuenow to input (from range)
Diff