Closed Bug 276154 Opened 20 years ago Closed 20 years ago

position: fixed; breaks on layout re-calculations

Categories

(Core :: Layout, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 268111

People

(Reporter: jon, Unassigned)

References

()

Details

(Keywords: regression, testcase)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8a6) Gecko/20041227 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8a6) Gecko/20041227 Fixed positioned elements seem to change their state to absolutely positioned when elements on a page change their appearance, in this case initiated by a:hover::after inserting some generated content, a "*". Should the page be scrolled so the fixed element is outside the viewport, this change of state completely removes the element from showing on the page at all. The effected element can be brought back to it's correct fixed position state by triggering a layout state change, eg: hover over an anchor which creates generated content. With some non-exhaustive testing, it's not just generated content which can cause such issues, but also changes to outline (well, -moz-outline), border, margin, padding, font-* which are dynamically changed via :hover, :active, :focus. This bug doesn't manifest itself in Mozilla 1.7.5 (Mozilla Suite or Firefox) nor Mozilla 1.8 up till about Alpha4.
please file layout bugs in the core component and not inside the application components
Component: General → Layout
Product: Mozilla Application Suite → Core
Assignee: general → nobody
QA Contact: general → core.layout
Attached file Testcase
I've seen this bug at http://www.cleansoftware.org/ This is a testcase based from that site. This bug happens with position:fixed elements with auto-offsets. I don't see the bug, using: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/2004110305 I can see the bug, using: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5) Gecko/20041104 Firefox/0.9.1+ 11:53am I think this could be a regression from fixing bug 266968.
Isn't this a duplicate of bug 268111?
Blocks: 268111
I'd say it's a duplicate though steps needed to reproduce the effect is different. It (fixed positioning) appears to have broke during the same set of builds, between Gecko/20041103 and Gecko/20041104.
Yes, a duplicate. Sorry about that, didn't find that previous bug.
*** This bug has been marked as a duplicate of 268111 ***
No longer blocks: 268111
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: