Open Bug 585278 Opened 13 years ago Updated 5 months ago

Edition of XUL tree element corrupts keyboard navigation

Categories

(Firefox :: Keyboard Navigation, defect)

Product:
Firefox
Component:
Keyboard Navigation
Platform:
x86
Linux
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: pitrasw, Unassigned)

Details

Attachments

(1 file)

Test case. Can be run with real-time xul editor.
2.44 KB, application/vnd.mozilla.xul+xml
Details 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 Ubuntu/10.04 (lucid) Firefox/3.6.8

After successful or canceled "direct" edition of xul tree's element label, up/down arrow keyboard navigation within xul tree is corrupted and focus is passed outside the tree to it's container.

Reproducible: Always

Steps to Reproduce:
Simple test case attached to this report. Run it with real-time xul editor. The same issue exists in xul trees with enabled direct edition.

Having xul tree (placed in the FF sidebar) you can navigate through its elements with keyboard arrows up, down, left and right (the last 2 for open and close tree's container nodes).

1. Edit any tree element node by mouse action, change or not the element's label, confirm or not with enter or esc key.

2. After successfull or canceled edition, navigation within tree with up/down keys is corrupted. Press up or down arrow keys and you will see that in some cases, especially around the edited tree row, the focus is passed outside the tree. In attached test case the focus is passed to the "parent" container - to the tabpanel. Pressing up/down keys again causes navigation through tab panels.
Actual Results:  
Focus is passed outside the tree. Navigation with arrow keys don't work anymore.

Expected Results:  
Navigation within tree should work as it does before edition.

    
    

    
      
  

    
  
Severity: normal → S3

          You need to log in
          before you can comment on or make changes to this bug.