- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Dec 2014 11:07:29 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294
--- Comment #8 from Robin Berjon <robin@w3.org> ---
(In reply to Domenic Denicola from comment #6)
> They almost certainly should be on HTMLElement, not Element.
> 
> They also probably should be getters, not methods.
> 
> As for name, I think it'd be confusing if `el.role` doesn't match
> `el.getAttribute("role")`.
> 
> (As to whether you need an `el.role` at all, I don't care: I personally
> think reflected attributes are useless and `getAttribute`/`setAttribute`
> work fine, but hey, we've reflected so many attributes already, what's one
> more?)
My understanding is that this isn't a reflected attribute but returns the
effective role (the first non-abstract role that is understood in the list).
Of course it's still nicer to call it role and have it be a getter. I don't see
this as an HTML feature so I don't understand why it was cloned there. This is
usable by SVG for instance. I reckon it could go into the DOM, or in its own
spec extending the DOM (depending on who does the work).
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 18 December 2014 11:07:30 UTC