Open
      
        Bug 1326709
      
      
        Opened 8 years ago
          Updated 3 years ago
      
        
    
  
Findbar draws additional focus outline (for 2 items)
Categories
(Toolkit :: Find Toolbar, defect)
        Toolkit
          
        
        
      
        
    
        Find Toolbar
          
        
        
      
        
    Tracking
()
        NEW
        
        
    
  
People
(Reporter: arni2033, Unassigned)
Details
>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open about:about
2. Open findbar, enable "Highlight All"
3. Type "add" in findbar, press Tab to focus "Previous" button, press Enter
4. Click on free place on the page, press Tab key
AR:  2 elements on the page look focused
ER:  1 element should look focused
STR_2:
1. Open about:about
2. Open findbar, enable "Highlight All"
3. Type "add" in findbar, press Enter
4. Click on free place on the page, press F3 key
5. Press Tab key
AR:  2 elements on the page look focused
ER:  1 element should look focused
This is regression between 2016-11-19 and 2016-12-12.
First of all, test normal (old) findbar, i.e. with prefs "findbar.highlightAll" and
"findbar.modalHighlight" disabled. But new broken findbar is also affected by slightly different steps
Component: Untriaged → Find Toolbar
Product: Firefox → Toolkit
|   | ||
| Comment 1•8 years ago
           | ||
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
I have tested this issue on Windows 7 and Windows 10 x64 with the latest Firefox release (53.0.2) and the latest Nightly (55.0a1-20170511030301) and managed to reproduce it.
The issue is not reproducible on Firefox versions where the old functionality of the findbar was enabled eg: Nightly(52.0a1-20161001030430).
From what I've observed the issue is present in all Firefox builds with the new findbar functionality.
Keywords: regression, 
          
            regressionwindow-wanted
| Updated•3 years ago
           | 
Severity: normal → S3
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•