This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 1010 [details] testcase Per the spec accesskey is registered to some element even if the element isn't the document tree. Only changing the accesskey attribute or moving the element to another document should change the assigned access key. That is not what browsers seem to do. If element isn't in the document tree, one cannot activate the element using accesskey. (Tested on Gecko and Webkit) So, the spec should mention that the elements which aren't in the document tree should not have assigned access key.
mass-move component to LC1
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: Partially Accepted Change Description: see diff given below Rationale: They still have an assigned access key, otherwise the actual assigned key might change as the element is moved around, and scripts couldn't find the assigned key's label while the element was briefly outside of a document. However, you are entirely correct that those keys should be ignored when pressed, shouldn't be exposed in the UA UI, etc. I've fixed that.
Checked in as WHATWG revision r6480. Check-in comment: Make sure commands aren't exposed when not in a document. http://html5.org/tools/web-apps-tracker?from=6479&to=6480