first tree item should be in the tab order - not the tree container

[Becky Gibson]

Currently the tree container element is in the tab order of the page. When the tree is created, the first tree item should be in the tab order rather than the tree container element. Only one tree item should ever be in the tab order at any one time. The last tree item with focus is the one which remains in the tab order. This way if someone tabs out of the tree control and then tabs back into the tree control, focus goes to the last tree item node accessed.

[davidb]

There are two approaches I'm thinking of: 1 - when a user tabs to the tree, automatically move focus to the first child 2 - programmatically set only the first child to be in the tab order

1 - is simple to implement. 2 - requires us to keep checking to make sure the first tree item hasn't changed (on add child etc.) and might be a bit heavy.

Both approaches have a bit of an odd smell to them.

[davidb]

fix (based on approach 1)

[davidb]

as before but removes tree root dom node from tab order.

[davidb]

added fix for 3335 but not yet 3333

[davidb]

fix for: 3304 3333 3335

[davidb]

fix for: 3304 3333 3335 (updated against a fresher trunk to resolve conflicts)

[bill]

(In [9105]) Fixes for focus/keyboard support for tree. Fixes #3304, #3333, #3335. Patch from David Bolter (CLA on file)