[Webkit-unassigned] [Bug 70911] Access keys on non visible DOM elements can still be accessed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Nov 24 12:15:15 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=70911


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #116492|review?, commit-queue?      |review-, commit-queue-
               Flag|                            |




--- Comment #6 from Alexey Proskuryakov <ap at webkit.org>  2011-11-24 12:15:15 PST ---
(From update of attachment 116492)
View in context: https://bugs.webkit.org/attachment.cgi?id=116492&action=review

r- since this implements logic that's substantially different from Firefox. I did not test IE and did not check the spec - please feel free to re-nominate and explain why this is what we want.

> Source/WebCore/ChangeLog:8
> +        Access key should only work with visible(visually) elements.

This is incorrect. Access keys work just fine with display:none elements in Firefox.

The difference with WebKit is that Gecko does not immediately click an element with accesskey when there are multiple ones with the same assigned key. Firefox only focuses such elements, and it cycles over others as you repeatedly press the same access key combination.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list