[Bug 10774] fallback for accesskey insufficiently defined

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

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

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

--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-28 07:00:34 UTC ---
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: 

1.1: The spec makes allowances for that already, by exposing the key to the DOM
and by suggesting that access keys be made known in the menus. Doing more than
that would be requiring UI, which is inappropriate.

1.2: I disagree; the user agent is the _user's_ agent, not the author's, and
can therefore ignore the author's wishes if the user so desires (or if the user
agent's implementor supposes that the user would so desire).

-- 
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, 28 September 2010 07:00:37 UTC