[Bug 10251] Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10251


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WORKSFORME




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-08-18 18:02:20 ---
Please file separate bugs for separate issues.

For your "ISSUE 1", the answer is that either the author exposes it with
accessKeyLabel, or the user agent exposes it in a menu, or (ideally) both.

For your "ISSUE 2", the spec already seems abundantly clear about this; see the
definition of "assigned access key". Each accesskey="" attribute is processed
independently.

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: Accepted
Change Description: no spec change
Rationale: The spec seems to already handle these cases.

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

Received on Wednesday, 18 August 2010 18:02:25 UTC