50617 - fixed positioning and top:auto [FIX POS]

Status: RESOLVED FIXED

(Core :: Layout, defect, P3)

Description

[Marcus.Brinkmann]

There is something strange happening with top:auto and everything else :0 for a
fixed positioned block element. It isn't handled according to 10.6.4of CSS2.
I would expect the h2 element and following text appears in a scrollale area
below the h1.
INstead, only the h1 is displayed and the rest is not rendered at all. This test
case stems from a larger page I wrote where several fixed blocks are positioned.
But this is the smallest test case I can give.

I hope this isn't me misunderstanding the standard.

Happy hacking,
Marcus
PS: bugzilla sucks. I need to register to report a bug, the forms are slow,
and how would I know which component is right?

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Confirming, changing to Layout, but cc:ing robert.  Robert, if this is fixed
with the new nsViewManager, please take the bug.

Comment 2

[Robert O'Callahan (:roc) (email my personal email if necessary)]

It is not fixed by the new view manager.

This is not a problem with "position: fixed". There seems to be a general 
problem with "top: auto". There may be other interacting problems too.

I will attach a tiny testcase for "top: auto". I think that in the testcase, the 
"subtitle" DIV should be positioned just under "Test Title" and extend all the 
way down to the bottom of the page.

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Attachment: Invalid behavior for "top: auto"?

Comment 4

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Yup... it is a problem with top: auto.  Unfortunately the spec doesn't define
top:auto for fixed positioned elements.

Comment 5

[Robert O'Callahan (:roc) (email my personal email if necessary)]

"position: fixed" is not the problem. My testcase uses "position: absolute".

Comment 6

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Triage

Comment 7

[Johnny Stenback (:jst)]

Layout problem, reassigning to buster.

Comment 8

[Hixie (not reading bugmail)]

Netscape's standard compliance QA team reorganised itself once again, so taking 
remaining non-tables style bugs. Sorry about the spam. I tried to get this done 
directly at the database level, but apparently that is "not easy because of the 
shadow db", "plus it screws up the audit trail", so no can do...

Comment 9

[karnaze (gone)]

Moving to m1.1 and reassigning to attinasi.

Comment 10

[Koike Kazuhiko]

worksforme. <http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/test.html>
and attachment 18400 [details] don't show any problem.

Comment 11

[Boris Zbarsky [:bzbarsky]]

This was fixed by the checkin for bug 98579.