Closed
Bug 647494
Opened 14 years ago
Closed 4 years ago
z-index changes behaviour with CSS tranform
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: zefling, Unassigned)
Details
(Whiteboard: [mozfr-community])
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:2.2a1pre) Gecko/20110402 Firefox/4.2a1pre
Build Identifier:
I presume that the ancient behaviour was okay. See following test:
Reproducible: Always
![]() |
||
Comment 3•14 years ago
|
||
http://www.w3.org/TR/css3-2d-transforms/#introduction says:
Any value other than ‘none’ for the transform results in the creation of both a
stacking context and a containing block.
so the behavior you see is correct as far as I can tell.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Okay, the behavior of Presto is similar, but Gecko 1.9.x et Webkit are a behavior different.
It is strange to see like that with floating ojects.
![]() |
||
Comment 7•14 years ago
|
||
I think that creating a stacking context is not enough for z-index to apply. For example, z-index does not apply to an element with opacity:0.5 but position:static.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INVALID → ---
![]() |
||
Comment 9•14 years ago
|
||
OK. Note that Opera, IE9, and we all apply z-index to transformed content (presumably because the spec says it needs to act like position:relative).
I guess we should see where the discussion on www-style ends up.
Reporter | ||
Comment 10•4 years ago
|
||
The problem is no longer present.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•