Closed
Bug 991314
Opened 11 years ago
Closed 11 years ago
Absolute position pseudo-element :after ignores relative position of the selected element
Categories
(Core :: General, defect)
Tracking
()
People
(Reporter: alexmoreno, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140314220517
Steps to reproduce:
Several <A> elements are styled as table-cells (for vertical centering) and have position: relative. There is a style of:
a::after {
content: "";
border: 1px solid #fff;
position: absolute;
display: block;
top: 3px;
left: 3px;
width: 78px;
height: 68px;
}
Actual results:
All the ::after elements appear on top of each other, not on top of their respective <A> elements.
It appears as if ::after is ignoring the position: relative of the <A> as table-cells and it takes the next available relative-position element up the tree.
If the <A> elements have display: block, the ::after elements behave as expected.
Expected results:
The ::after elements should appear as decorative elements on top of each <A> button, regardless of whether the <A> has display block or table-cell.
Comment 1•11 years ago
|
||
I think this was recently fixed. Can you reproduce the problem in Nightly?
http://nightly.mozilla.org/
Flags: needinfo?(alexmoreno)
Reporter | ||
Updated•11 years ago
|
Flags: needinfo?
Reporter | ||
Comment 3•11 years ago
|
||
Correct! This is no longer an issue in nightly.
Reporter | ||
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?
Resolution: --- → WORKSFORME
Reporter | ||
Comment 4•11 years ago
|
||
Tested Aurora and the fix is not there yet. So as of today, the fix is only on Nightly.
Also, I'm not sure what's the correct way of resolving this issue. Invalid, since it's already fixed? That's my best guess at the moment.
Resolution: WORKSFORME → INVALID
Comment 5•11 years ago
|
||
We use WORKSFORME for valid bugs that we believe have been fixed recently, only we don't
know the exactly what fixed it. In this case though I'm pretty sure bug 63895 fixed this
so duping there. Thanks for your report and following up with testing Nightly!
Resolution: INVALID → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•