455858 - No caret with two items at same location (position:fixed)

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Sheldon Glickler]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16

Click in textarea.  No caret shows, but text can be entered.  Presence of a div with visibility:hidden in same position (position:fixed) causes the problem.  Removal of this invisible block eliminates the problem.  (Is there a workaround to make this not happen? On the page I am working with in my real app, there are three such blocks that are dynamically chosen with only one visible depending upon which button on the form is clicked, and all must be in the same screen position with position:fixed)

Reproducible: Always

Steps to Reproduce:
1. Click in textarea
2. Type text

Actual Results:  
Text is there but no caret indicating focus.

Expected Results:  
Always shown a caret indicating focus.

Similar in some respects to 130418.  I would like to know if there is something I can specify in css or elsewhere so that this doesn't happen.

Comment 1

[Sheldon Glickler]

Looking at www.sheldonlg.com/focus/index1.php we see that it also exhibits this same behavior for a text boxes.

Comment 2

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

I see indeed this problem with Firefox 2, but it is fixed in Firefox 3.

Comment 3

[Sheldon Glickler]

What can be done in FF2 as a workaround so that this does not happen?  
Is there anything I can specify?  
Why did it happen in FF2?  If it is fixed in FF3, then they must have found the reason.

Comment 4

[Ria Klaassen (not reading all bugmail)]

I think it would be best to upgrade to Firefox 3. Firefox 2 will only be updated with security and stability fixes and bad regressions, and I see the bug also in older versions so it is not a regression. 

There will definitely be a bug that has fixed this, but at the moment I don't know the bug number.

Comment 5

[Ria Klaassen (not reading all bugmail)]

(In reply to comment #4)
> Firefox 2 will only be
> updated with security and stability fixes and bad regressions
> 
Sorry, I meant that bad regressions will be fixed in Firefox 2 (e.g. something worked correctly in Firefox 2.0.0.15 but broke in Firefox 2.0.0.16) and security & stability problems.

Comment 6

[Sheldon Glickler]

Upgrading to FF3 is not an answer.  I cannot control what browser/version users will employ.  Yes, if there is a complaint I can say thare is a known bug in FF2 and earlier and that FF3 has fixed it.  However, this is less than optimum.  What I am seeking is if there is a workaround that I can put into my code such that it doesn't happen in FF2.

BTW, most people that I have spoken to that have upgraded to FF3 say they wish they had stayed with FF2.

Comment 7

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 8

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.