Spinning this off from bug 1901233, for the unusual situation that we ran into there. tl;dr: adding and then removing a text node in a flex container will cause us to add and then remove an anonymous flex item wrapper-box, EXCEPT that if the text is linewrapped, we fail to remove the anonymous flex item, for some reason. The straggling anon box can cause trouble because (a) it violates invariants (which caused a crash in bug 1901233) and (b) it influences how packing space is distributed, e.g. if the flex container uses `justify-content:space-around` or `gap` to distribute packing space around flex items.
Bug 1902156 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Spinning this off from bug 1901233, for the unusual situation that we ran into there. Adding and then removing a text node in a flex container will cause us to add and then remove an anonymous flex item wrapper-box -- that's what's supposed to happen, at least. BUT: if the text is linewrapped, we fail to remove the anonymous flex item, for some reason. The straggling anon box can cause trouble because (a) it violates invariants (which caused a crash in bug 1901233) and (b) it influences how packing space is distributed, e.g. if the flex container uses `justify-content:space-around` or `gap` to distribute packing space around flex items.