User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021204 Debian/1.2.7-4
Build Identifier: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021204 Debian/1.2.7-4
If an element A with a fixed position and z-index=1 is inside another element B
with z-index=0, A does not receive mouse events such as "onclick".
Steps to Reproduce:
Of course it is, it is effect of "overflow: auto;" properity. If you change it
to hidden or remove it, all be as you wish. But auto there is mean visible, so
bigger area with z-index: 0 overflow lesser area with z-index: 1.
Yet, I find it strange that an element with a bugger z-index is "behind" one
with a lower z-index. CSS2 specs says "Boxes with greater stack levels are
always formatted in front of boxes with lower stack levels". So there's a
I think this bug should be named: "z-index vs overflow: visible priority"
please reopen if you disagree.
*** This bug has been marked as a duplicate of 78087 ***
Created attachment 110122 [details]
Overflow:Auto vs z-index
Sorry, I little misguided. Where is ther root of all overflow:auto bugs? I just
like to show, that overflow:auto is not working properly. Look at this testase
to see difference between Auto, Hidden and Visible. All 3 states should be
visible, because of z-index:1
Sounds like css to me. I dont know if this is a dupe or not, ian, can you take a
It is not CSS, I sure. It is bug inside overflow:auto. Please, reopen this bug
-- it have nothing with negative z-index bug.
reopening per coments.
Moving to layout, which really does sound more appropriate. I can confirm the
bug on Win2k build 2002-12-20-08-trunk, OS-All. This is definately a bug
because it used to work on 7.01 build, at least on mac.
Created attachment 110192 [details]
Overflow: Auto and z-index case
This testcase show, that Overflow: Auto boxes are on top of all other boxes,
even if z-index made another order.
*** Bug 188502 has been marked as a duplicate of this bug. ***
resummarizing to make the problem clear
Created attachment 111179 [details]
Overflow:Auto and Scroll overrided z-index
Small change of previous testcase, included overflow:scroll box.
I think I found -- it is backfire from bug 39621.
Created attachment 112571 [details] [diff] [review]
The problem is that scrolling frames don't get their content parent hooked up
correctly when their view is created. This patch makes nsCSSFrameConstructor
pass the content-parent frame down into BuildScrollFrame so that the scrolling
view gets its zparent set right.
Comment on attachment 112571 [details] [diff] [review]
we need to fix this file to not suck....
Does this patch also fix
No, that testcase is not fixed.
That is a weird one...
Created attachment 113469 [details] [diff] [review]
Updating patch to trunk
Hixie: that testcase is fixed by my patch in bug 182107.
Fix checked in.