Bug 1739561 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

In our current fragmentation architecture, each container are required to handle `break-inside` property. We currently do not handle `break-inside` property in flex container at all. 

We should do something similar like [this part](https://searchfox.org/mozilla-central/rev/6c8d325e61b0b445ed2e04899da38c3a4c266cba/layout/forms/nsFieldSetFrame.cpp#636-645) in `nsFieldSetFrame::Reflow` by using [`ShouldAvoidBreakInside()`]() and return `SetInlineLineBreakBeforeAndReset()` status to the parent.
In our current fragmentation architecture, each container are required to handle `break-inside` property. We currently do not handle `break-inside` property in flex container at all. 

We should do something similar like [this part](https://searchfox.org/mozilla-central/rev/a6d25de0c706dbc072407ed5d339aaed1cab43b7/layout/forms/nsFieldSetFrame.cpp#645-653) in `nsFieldSetFrame::Reflow` by using [`ShouldAvoidBreakInside()`](https://searchfox.org/mozilla-central/rev/a6d25de0c706dbc072407ed5d339aaed1cab43b7/layout/generic/nsContainerFrame.cpp#2719-2750) and return `SetInlineLineBreakBeforeAndReset()` status to the parent.

Back to Bug 1739561 Comment 7