281112 - Firefox doesnt like "position: fixed" when using upper layer with an offset

Status: RESOLVED INCOMPLETE

(Core :: Layout, defect)

Description

[Tepel]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041118 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041118 Firefox/1.0

As you can see in the example there seems to be a minor flaw in the way the
fields are rendered. The top-left box is the one that doesnt work right. As far
as i have tested it is platform independant. 
There seem to be more positioning problems (at least not as critical as in IE
which _really_ doesnt like my latest design :) but i havent seen anything like
this in the reports.

Explenation of the boxes to make it extra clear.

Top-left:
Consists of two layers, the bottom layer has a fixed position. the upper layer
is relatively positioned on it with a offset to the left en top. Its this offset
that makes the bug in the field.

Top-right:
Also two layers, but this time both are positioned relatively. no problems here

Bottom-left:
Again two layers, this time fixed but no offset. Works fine.

Bottom-right:
This time a bigger offset, now i cant even see the cursor (carrot?) blink

Reproducible: Always

Steps to Reproduce:
1. See example
2. Focus on top-left box
3. See the offset with the cursor (carrot?)

Actual Results:  
Slightest offset with the cursor (carrot?)

Expected Results:  
No offset with the cursor (carrot?) :)

Comment 1

[Tepel]

hmm seems like cursor is the right word :)
dont know how i got carrot in my head though :)

Comment 2

[Phil Ringnalda (:philor)]

The word you were looking for, for the blinking insertion point, is caret.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Boris Zbarsky [:bzbarsky]]

Testcase never got attached to the bug, and now it's gone, so not much we can do with this as-is.  Please reopen if there is a page showing the problem, ok?