Closed
      
        Bug 1224560
      
      
        Opened 9 years ago
          Closed 9 years ago
      
        
    
  
Cursor still displayed after leaving input field focus
Categories
(Firefox :: Untriaged, defect)
Tracking
()
        RESOLVED
        WORKSFORME
        
    
  
People
(Reporter: lnk741, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421
Steps to reproduce:
I tabbed out an input field...
OS: OSX 10.11.1
Test Case:
https://jsfiddle.net/93uc46vL/
1. Set your focus to the input field
2. Tab to the button
The Cursor "|" is now displayed on the center of the button
Actual results:
The cursor is still displayed after changeing the foucus to anoter field.
Expected results:
The cursor should not be displaied after leaving foucus.
          Comment 1•9 years ago
           
         | 
      ||
This does not happen with Mac OS X 10.10.5.
Status: UNCONFIRMED → NEW
Has STR: --- → yes
Ever confirmed: true
          Updated•9 years ago
           
         | 
      
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
          Updated•9 years ago
           
         | 
      
          Updated•9 years ago
           
         | 
      
Component: General → Untriaged
          Comment 3•9 years ago
           
         | 
      ||
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20151203030226
Hi,
I tested this issue on Mac OS X 10_11 with Firefox Nightly 45.0a1, and I can't reproduce the problem.
Please download from here latest nightly: https://nightly.mozilla.org/ and retest the problem.
Hardware: Unspecified → x86
I just tested the case with a new profile and determined the problem in the prefs.js file in addition the broken prefs file.
          Comment 6•9 years ago
           
         | 
      ||
user_pref("accessibility.browsewithcaret", true);
this should not be set, otherwise you get the cursor ;) Therefore resolving as WORKSFORME. Thanks for reporting though!
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•