Open Bug 1460484 Opened 6 years ago Updated 2 years ago

Consider having out-of-flow frames contribute to the overflow area of their placeholder

Categories

(Core :: Layout, enhancement, P2)

enhancement

Tracking

()

Tracking Status
firefox62 --- affected

People

(Reporter: mattwoodrow, Unassigned)

Details

For display list purposes, we almost always want to know the overflow area of a given frame, including that of any placeholder descendants.

We currently have workarounds (nsDisplayListBuilder::MarkOutOfFlowFrameForDisplay), and bug 1453541 to deal with the current state.

We should consider trying to include the overflow area of OOF frames during reflow, as it would simplify display list code (but possible make other things more complicated).

Dbaron mentioned that the layout of OOFs can depend on the in-flow content, so we'd need to layout the normal content, layout the OOFs, and then do a post-processing pass to update the overflow areas of the normal content.

We also probably should do a full audit on the other (non-display list) consumers of overflow area, and see which they need.
The post-processing would be needed for absolutely-positioned frames, but floats could be handled in the primary pass.  I think there are a few other edge-cases of out-of-flows that would need to be considered.
Priority: -- → P2
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.