Manual test of DOM accessKey reflecting the HTML accesskey attribute value
There is a button, with accesskey="a". After 10 seconds, a script changes the button's HTML accesskey attribute (using setAttribute) to "g".
Expected result
A shortcut based on "a" plus modifiers should either activate or focus the button in the first 10 seconds after the page is loaded. After about 10 seconds, the button should add text describing the shortcut activation assigned, and the paragraph below the button identify the accesskey value as "g". The button will try to open a window with the Github repo for this test, so you can update the results section :)
Vivaldi 1.0.303.52 beta, MacOS 10.10.5 (based on Chromium)
Trying to use either key plus modifiers does not do anything.
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
Opera 12, 64-bit Ubuntu Linux 14.04
In the first 10 seconds Opera shows the shortcut as "(A) (null)", after the 10-second timeout as "(G) (null)"
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
Firefox 42, Windows 7
Firefox 42, 64-bit Windows 7
Firefox 42, MacOS 10.10.5
Firefox 42, 64-bit Ubuntu Linux 14.04
Within the first 10 seconds of loading, ctrl-alt-a on Mac or Alt-Shift-a on Windows/Linux presses the button, opening the github page. Afterward, ctrl-alt-g / Alt-Shift-g does so instead.
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
After the timeout Firefox adds "activation: Alt+Shift+g" on Windows/Linux, "activation: ^⌥g" on Mac to the button, showing it successfully updates the value of the accessKeyLabel DOM attribute
Chromium 46, 64-bit Windows 7
Internet Explorer 11, 64-bit Windows 7
Epiphany 3.10.3, 64-bit Ubuntu Linux 14.04
Within the first 10 seconds of loading, alt-"a" presses the button, opening the github page. Afterward, alt-g does so instead. The attempt to open a window is blocked by the pop-up manager, as if it were not triggered by a user action
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
Internet Explorer 11, Windows 7
Chrome 46, Windows 7
Trying to use either key plus modifiers does not do anything until after the update, when pressing Alt+Shift+g activates the button, opening the github page.
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
Button value does not update.
Safari 9.01, MacOS 10.10.5
Within the first 10 seconds of loading, ctrl-alt-"a" presses the button, opening the github page. Afterward, ctrl-alt-g does so instead.
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.
Yandex browser 15.4.2272.3909 beta, MacOS 10.10.5 (based on Chromium)
Within the first 10 seconds of loading, ctrl-alt-"a" presses the button. Afterward, ctrl-alt-g does so instead. The attempt to open a window is blocked by the Yandex pop-up manager, as if it were not triggered by a user action, but the button retains focus.
After the timeout, the paragraph below the button gives "g" for the value of the accesskey, showing that the DOM accessKey has been successfully updated.