Closed
Bug 1248402
Opened 8 years ago
Closed 8 years ago
Transition of an absolute element not working when it's inside a flex element
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: rmmpaderes, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0 Build ID: 20160210153822 Steps to reproduce: Box 1 and box 2 should be an absolute element. 1. Insert box a inside a flex container. 2. Have box 1 react a transition when box 2 is inserted inside the flex container. 3. When box 2 is inserted, do a keyframe animation. See this demo in jsfiddle - https://jsfiddle.net/rmejabLy/1/ Actual results: Box 1 never does the transition animation while box 2 does the animation. If you remove the display: flex inside the .container element, the box 1 transition will work when box 2 is inserted. Expected results: Box 1 should do the transition animation when box 2 is inserted. I tested this in Safari, Chrome, and IE and they all work fine.
Reporter | ||
Comment 1•8 years ago
|
||
Typo on the first step for reproducing, it should be: "1. Insert box 1 inside a flex container."
Comment 3•8 years ago
|
||
This seems similar to bug 625289, except it can't be exactly that bug because that bug is fixed.
Comment 4•8 years ago
|
||
Updated•8 years ago
|
Attachment #8719511 -
Attachment description: 1248402.html → testcase 1 (reporter's testcase)
Comment 5•8 years ago
|
||
I believe bug 874718 will fix this, because it'll mean we don't have to wrap abspos flex children in anonymous flex items anymore, which means we won't have to do frame-reconstruction when a new wrappable child (like raw text or another abspos flex item) gets inserted.
Depends on: 874718
Comment 6•8 years ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #5) > I believe bug 874718 will fix this Yup -- I confirmed locally that this was broken in Nightly 2016-10-31 & working in Nightly 2016-11-01. (And the functionality associated with bug 874718 first shipped in the 2016-11-01 nightly.) Hence, closing this as FIXED by bug 874718. (I'm not marking this as a duplicate, because there's some more complex stuff going on here (presence/absence of frame reconstruction), and it's kinda just a lucky accident that bug 874718 helps here.)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•