Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#5830 closed defect (fixed)

tree: FF3 issue keyboard is broken. Items which have been expanded remain in the tab order

Reported by: Becky Gibson Owned by: Becky Gibson
Priority: high Milestone: 1.1
Component: Dijit Version: 1.0
Keywords: FF3 a11y Cc: Becky Gibson, Douglas Hays
Blocked By: Blocking:

Description

once a tree item has been expanded it remains in the tab order. When focus leaves a tree item that has been expanded tabindex is not being reset back to -1

Change History (6)

comment:1 Changed 11 years ago by Becky Gibson

Actually more is broken. Last item focused is not properly getting set into the tab order when the tree loses focus.

steps to reproduce first case:

  1. open dijit/tests/test_Tree.html
  2. tab to Continents then down arrow until Asia is reached
  3. press right arrow to expand Asia
  4. press left arrow to close Asia
  5. now press down arrow so focus is on Australia
  6. press shift-tab - focus will to go Asia - it should not.

steps to reproduce second case:

  1. open dijit/tests/test_Tree.html
  2. tab to Continents then down arrow until Africa is reached
  3. press right arrow to open Africa
  4. press down arrow to focus Egypt
  5. press tab (focus should go to the destroy button)
  6. press shift-tab - focus should go back to the last focused item in the tree (which in this case should be Egypt) and it does not.

#5784 depends upon this ticket

comment:2 Changed 11 years ago by Becky Gibson

Owner: set to Becky Gibson
Status: newassigned

This seems to only be an issue in FF3 - I'll file a ticket

comment:3 Changed 11 years ago by Becky Gibson

Keywords: FF3 a11y added

comment:4 Changed 11 years ago by Becky Gibson

Summary: tree: regression keyboard is broken. Items which have been expanded remain in the tab ordertree: FF3 issue keyboard is broken. Items which have been expanded remain in the tab order

comment:5 Changed 11 years ago by Becky Gibson

Resolution: fixed
Status: assignedclosed

(In [12514]) fixes #5830, #5784 added onfocus event handler to the labelNode so that focus does not have to bubble to the tree. Tree.focusNode() remains and the labelNode onfocus event handler calls _onTreeFocus so as not to modify the api. Also added support for wai selected state. !strict

comment:6 Changed 11 years ago by Becky Gibson

(In [12520]) refs #5830 attach the onfocus event in the template rather than via dojo.connect in the code. !strict

Note: See TracTickets for help on using tickets.