Closed Bug 101741 Opened 23 years ago Closed 23 years ago

z-index is all screwed up

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 87839

People

(Reporter: Joel.Turner, Assigned: attinasi)

References

(
URL
)

Details

Tested on: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4+) Gecko/20010919
and Netscape 6.1

Reproducible: Always

Steps to Reproduce:
1. Goto http://www.revenue.state.il.us/Netscape6Debug/
2. Hold mouse cursor over down arrows on right
3. You will see scoll div ecclipse graphics above
4. Hold mouse cursor over up arrows on right
5. You will see further damage in Moz

Actual Result: z-index of divs is all screwed up

Expected Results: proper z-indexing of divs like Netscape 4.x and IE does.						
Comments: It appears that this works slightly better in recents builds than in
Netscape 6.1, but it is still unacceptable.  Some other bug reports are similiar
to this, but nothing exactly like it.  Perhaps they are related, but my
scrolling example better illustrates exactly what is going wrong.  By the way,
this is also a good example of how slow the javascript in moz is compared to
Netscape 4.x and IE.  I would be interested in a work-around if someone knows of
one.
This looks to me like bug 87839, but I'm unsure. Someone please confirm.

Reporter, I've had better luck using overflow:hidden than clip, you might try
that as a workaround.
bug 87839 says "clipped layers seem to erase other layers below in the z-stack
", but my example has clipped layers erasing layers that are actually higher in
the z-stack.  I've tried using overflow:hidden but it has other problems.
In your testcase there are no layers higher in the stack than the clipped layer:

<div id="phone" style=" ... z-index:6">
<div id="phonesearch" style=" ... z-index:7">
<div ID="scrollarea" style="z-index:30; ... ">

It really looks like bug 87839 to me, but I'll leave this open if you can come
up with a testcase showing elements higher in the stack being obscured.


Your right..... I was thinking backwards for some reason.  I rebuilt my testcase
changing the z-orders around and it works much better.  Thanks.


*** This bug has been marked as a duplicate of 87839 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.