Version: ToT @ r608853

Say we have an inline formatting context, like:

<div id=target>foo</div>

There should be an NGInlineNodeData at the LayoutNGBlockFlow. Everything is fine so fat.

Now if we turn #target into a block formatting context by, for example
- target.innerHTML = ""
- or target.innerHTML = "<div>foo</div>"

Then after relayout, the original NGInlineNodeData at #target isn't cleared!

This currently doesn't cause any malfunctioning, since we don't access NGInlineNodeData from a block formatting context. Having a leftover data there is still bad...

This also causes failures in DocumentMarkerControllerTest, which asserts that text node is cleared by GC after detaching from DOM, which isn't due to the leftover NGInlineNodeData keeping reference to the node (through NGOffsetMapping).
 

Version: ToT @ r608853

Say we have an inline formatting context, like:

<div id=target>foo</div>

There should be an NGInlineNodeData at the LayoutNGBlockFlow. Everything is fine so far.

However, if we turn #target into a block formatting context by, for example
- target.innerHTML = ""
- or target.innerHTML = "<div>foo</div>"

Then after relayout, the original NGInlineNodeData at #target is still there. It should be cleared since we shouldn't have NGInlineNodeData if a block isn't inline formatting context.

This currently doesn't cause any malfunctioning, since we don't access NGInlineNodeData from a block formatting context. Having a leftover data there is still bad...

This also causes failures in DocumentMarkerControllerTest, which asserts that text node is cleared by GC after detaching from DOM, which isn't due to the leftover NGInlineNodeData keeping reference to the node (through NGOffsetMapping).