Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#8987 closed defect (fixed)

shift-tab doesn't work (Safari 4 beta, chrome 2)

Reported by: bill Owned by: Becky Gibson
Priority: high Milestone: 1.4
Component: Accessibility Version: 1.3.0rc2
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

Not sure if there's anything we can do about this, but on test_Menu.html and test_Toolbar.html, shift-tab isn't going backwards through the tab stops. Tab correctly goes forwards through the tab stops.

It leads to failures in the Menu automated test.

I sent a bug report to apple although it didn't give a tracking number, so there's no way to know if they are working on it or if there's a workaround.

Attachments (1)

SafariTabIndex.html (2.6 KB) - added by Becky Gibson 10 years ago.
HTML file that demonstrates the problem

Download all attachments as: .zip

Change History (17)

comment:1 Changed 11 years ago by bill

Description: modified (diff)

comment:2 Changed 11 years ago by Adam Peller

Does it happen on Chrome2, also? If so, probably best to file the bug at bugs.webkit.org, or check with Alex.

comment:3 Changed 11 years ago by bill

Summary: shift-tab doesn't work (Safari 4 beta)shift-tab doesn't work (Safari 4 beta, chrome 2)

Ah so it does... chrome 1 has a different set of problems which I filed under #8988 and #8989 but I guess that's irrelevant now that chrome 2 is beta.

comment:4 Changed 11 years ago by bill

Filed #24840 against webkit.

comment:5 Changed 11 years ago by bill

Also causing [some of] the failures on Spinner_a11y.html and Slider_a11y.html, the a11yTabFocus tests.

comment:6 Changed 10 years ago by Douglas Hays

Still failing with Safari 4.0 (4530.17) on latest trunk.

comment:7 Changed 10 years ago by Becky Gibson

This seems to be related to _keyNavContainer.js as the only places where I see this as a problem is with toolbar and menu which are the only two widgets that use this. Not sure if it is related to removing /adding the tabindex on the container or not.

Changed 10 years ago by Becky Gibson

Attachment: SafariTabIndex.html added

HTML file that demonstrates the problem

comment:8 Changed 10 years ago by Becky Gibson

This seems to be related to removing and resetting the tabindex programmatically. I have attached a non-dojo HTML file that demonstrates the problem.

comment:9 Changed 10 years ago by Becky Gibson

(In [18626]) refs #8987 instead of removing tabindex in _onContainerFocus just change it to -1. This works better in safari than removing it.

comment:10 Changed 10 years ago by Becky Gibson

[18626] partially fixes the problem. Now, on the first toolbar, if you arrow over to any button and press shift-tab, you go to the previous button IF there is no other focusable item before the toolbar. If you add an anchor tag before the first toolbar on the page, pressing shift-tab with focus on an inner button of the toolbar will take you to the anchor tag (as it should). Thus, I believe this is still a Safari 4 problem. I don't know if we will be able to work around this new behavior or not. Note that you have to have the advanced preference "press tab to highlight each item on a web page" set in order to be able to tab to anchor elements.

comment:11 Changed 10 years ago by bill

(In [18800]) Enable robot tests on Chrome now that it's working. Thanks Mark! (refs #9526).

Also disabling keyboard tests on safari 4 / chrome 2 until the keyboard bugs are fixed (refs #8987, #9506).

comment:12 Changed 10 years ago by Becky Gibson

Milestone: tbd1.3.2

comment:13 Changed 10 years ago by Adam Peller

Milestone: 1.3.21.4

Safari never had keyboard support. Consider for 1.4

comment:14 Changed 10 years ago by bill

(In [19099]) Add test for tabbing and shift-tabbing around the Editor widget. Working on FF and IE, although not safari (but that seems to be a problem with DOH rather than w/the editor?)

Refs #9558, #9612, #8987.

comment:15 Changed 10 years ago by bill

Resolution: fixed
Status: newclosed

Cool, this is working on the latest safari (4.0.3) and chrome (version 3) now, just due to bug fixes in the browser code.

comment:16 Changed 10 years ago by bill

(In [20113]) Keyboard is more-or-less working for safari and chrome. Enabling the keyboard tests for all browsers. Refs #9506, #8987.

Note: See TracTickets for help on using tickets.