168883 - detection of {ib} situations needs to happen in ContentInserted, ContentAppended, and elsewhere

Status: RESOLVED WORKSFORME

(Core :: Layout, defect, P5)

Description

[Boris Zbarsky [:bzbarsky]]

Right now we only detect {ib} situations in ConstructInline... so dynamic
changes to the tree can easily not lead to things that _should_ be special being
marked as such.  We should fix that (or handle {ib} in reflow as dbaron once
suggested, I guess).

Comment 1

[Boris Zbarsky [:bzbarsky]]

marking some dependencies.... thare are probably a few more I missed. I really
would prefer to see us move towards doing this in reflow, though.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Handling {ib} during reflow is bug 142585, and I'd certainly prefer that.  It
would probably be less work than fixing all of these messy issues with the
current handling.

Comment 3

[Boris Zbarsky [:bzbarsky]]

So at this point, I think WipeContainingBlock() pretty much covers what this bug is about.  I haven't been able to come up with a scenario in which ContentAppended or ContentInserted fails, and the various dependent bugs are OK.