- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Dec 2014 13:38:22 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294
--- Comment #12 from Anne <annevk@annevk.nl> ---
(In reply to James Craig from comment #9)
> Because roles and labels are not specific to HTML. Unless every display
> language inherits from HTMLElement, these should be on Element.
With "display language" you mean SVG and HTML? Unless role="" is supported
regardless of namespace, putting them on Element might not be a good idea. (We
are trying to see if this can work for class="" and id="" but nobody has
implemented that so I'm not sure why we would go there for role...)
> > And why can't computedRole just be role?
>
> role should be a the read/write reflected attribute. computedRole is the
> readonly calculated value of the matched role.
I think it would be fine for role to serve both those purposes. That's what
e.g. <input>.type does too. If you want the actual value you can just use
getAttribute("role").
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 18 December 2014 13:38:24 UTC