I think the root of the problem is this. We have a frame tree at the top when `NormalizeChildLists` is called, and the frame tree at the bottom after that call. That later results in the assertion b/c `0x7feff987fde8` (green) being the childNIF isn't in one the expected child lists; rather it's still in the EOC of the container's prev-in-flow. (It's worth noting that this assertion is fairly harmless - when this container reflows its children the reflow of `0x7feff987f520` (blue) should take care of it (as described above).)
Bug 1405813 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think the root of the problem is this. We have a frame tree at the top when `NormalizeChildLists` is called, and the frame tree at the bottom after that call. That later results in the assertion b/c `0x7feff987fde8` (green) being the childNIF isn't in one of the expected child lists; rather it's still in the EOC of the container's prev-in-flow. (It's worth noting that this assertion is fairly harmless - when this container reflows its children the reflow of `0x7feff987f520` (blue) should take care of it (as described above).)
I think the root of the problem is this. We have the frame tree at the top when `NormalizeChildLists` is called, and the frame tree at the bottom after that call. That later results in the assertion b/c `0x7feff987fde8` (green) being the childNIF isn't in one of the expected child lists; rather it's still in the EOC of the container's prev-in-flow. (It's worth noting that this assertion is fairly harmless - when this container reflows its children the reflow of `0x7feff987f520` (blue) should take care of it (as described above).)