[Bug 10452] Consider documenting attributes that map to ARIA properties in a separate table


steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
                 CC|                            |faulkner.steve@gmail.com
         Resolution|WONTFIX                     |

--- Comment #2 from steve faulkner <faulkner.steve@gmail.com>  2010-08-31 13:19:48 ---
(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

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 31 August 2010 13:19:54 UTC