This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It's a little confusing that attributes which have a strong semantic implying an ARIA property are mixed in with elements. It might help readability to put them in a separate table, with the ARIA properties they map to.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: That would be a pain to do — in practice the mix is not element vs attribute, but very much a mixture.
(In reply to comment #1) > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. If > you have additional information and would like the editor to reconsider, please > reopen this bug. If you would like to escalate the issue to the full HTML > Working Group, please add the TrackerRequest keyword to this bug, and suggest > title and text for the tracker issue; or you may create a tracker issue > yourself, if you are able to do so. For more details, see this document: > http://dev.w3.org/html5/decision-policy/decision-policy.html > Status: Rejected > Change Description: no spec change > Rationale: That would be a pain to do — in practice the mix is not element vs > attribute, but very much a mixture. being a pain to do is not a reason for not doing it, in some cases it is mix and match in other cases its not, the reason to do it is does it make it clearer for authors? I think it does. Also the current spec text DOES NOT provide requirments for these attributes on all of the elements they are applicable to, so authors could easily miss the requirement to use them as its not explicitly stated. Note: will be adding the global attribute to the table: draggable
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It wouldn't be a pain for me, it would be a pain for readers. > Also the current spec text DOES NOT provide requirments for these attributes on > all of the elements they are applicable to, so authors could easily miss the > requirement to use them as its not explicitly stated. > Note: will be adding the global attribute to the table: draggable Please file separate bugs for each issue.
The bug-triage sub-team thinks this is task force priority as it is closely related to ARIA mapping. Assigning the bug to Cynthia Shelly so that is handled in ISSUE-129.
wontfix accepted as part of http://www.w3.org/html/wg/tracker/issues/129