RESOLVED INVALID 121061
AX: Let ARIA override the value of an input type=range 
https://bugs.webkit.org/show_bug.cgi?id=121061
Summary AX: Let ARIA override the value of an input type=range
Attachments
test case (524 bytes, text/html)
2014-02-07 11:55 PST, James Craig 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2013-09-09 17:11:02 PDT
<rdar://problem/14950066>
chris fleizach
Comment 2 2013-09-09 17:39:27 PDT
James, does this idea look accurate to you
James Craig
Comment 3 2013-09-10 16:21:10 PDT
No, it's a bad patch. Only aria-valuetext should be used on range. The other attrs are identical semantically to the aria attrs (e.g. @max vs @aria-valuemax, and @value vs @aria-valuenow) so the host language attrs should win. From the ARIA spec: http://www.w3.org/WAI/PF/aria/complete#host_general_conflict "When a host language declares a WAI-ARIA attribute to be in direct semantic conflict with a native attribute for a given element, user agents MUST ignore the WAI-ARIA attribute and instead use the host language attribute with the same implicit semantic."
Dominic Mazzoni
Comment 4 2013-09-10 23:44:45 PDT
Thanks for correcting me. I misinterpreted the spec. I think the aria-valuetext part of the patch is still good - it wasn't working on an input type=range previously. I'll revert the rest.
James Craig
Comment 5 2013-09-11 00:11:54 PDT
(In reply to comment #4) > I think the aria-valuetext part of the patch is still good - it wasn't working on an input type=range previously. Are you sure? I demoed this working in a WWDC 2011 presentation. Are you saying it regressed or that it didn't look like it was working at all?
James Craig
Comment 6 2014-02-07 11:55:07 PST
Created attachment 223479 [details] test case
James Craig
Comment 7 2014-02-07 11:55:45 PST
Attaching working test case and closing. If you have a test case that does not work, please reopen.
Note You need to log in before you can comment on or make changes to this bug.