[Bug 10777] user agent assignment of modifier keys subset of accesskey processing subset

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

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:03:38 UTC ---
> 1. does this subset require a user agent to automatically determine 
> a modifier or combination of modifier keys?

No. If it did, it would say so.

> 2. if so, is this so as to avoid conflicts with application and 
> operating system hotkeys?

n/a

> 3. if the user agent automatically determines a modifier or combination
> of modifier keys, how will this information be conveyed to the user

This is discussed in other parts of the specification.

> 4. does the user retain control over which modifier key or combination
> of modifier keys the user agent uses?

The user and user agent in concert do so, yes.


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: As far as I can tell this is all addressed already.

-- 
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:03:45 UTC