- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Dec 2014 22:40:17 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294 --- Comment #28 from Alice Boxhall <aboxhall@chromium.org> --- (In reply to Anne from comment #25) > (In reply to Alice Boxhall from comment #23) > > I agree, but I don't see how that affects this proposal. > > It does if we want to make .role return the mapping that ends up being used, > but accept a sequence of mappings as input. It would be weird for it to > return something you cannot set. And I think that's the only API that makes > sense for .role, similar to <input>.type. I see. I think `role` would be best simply reflecting the string "role" attribute verbatim, regardless of what is applied - this is why we need `computedRole` as, as you point out, this may be quite different to `role` or even return a value if `role` is not set. Regarding reflecting ARIA attributes: there have been proposals kicking around for this on the PFWG bug tracker (https://www.w3.org/WAI/PF/Group/track/issues/438) for some time - if this is something we'd like to discuss here, I can file a separate bug for it as I think these distinct (albeit related) issues (since, as Dominic points out, we can always use getAttribute to get the verbatim string attribute). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 December 2014 22:40:18 UTC