DescriptionDon't let a column spanner affect the self-margin-collapsing state of the parent.
When a spanner is removed from the tree, we mark the container chain for
layout, just like we do when removing any other kind of object. The container
of a spanner is the multicol container, though, so the direct parent of the
spanner may not be marked for layout. And that should not be necessary either,
since the spanner is essentially taken out of normal flow.
We get some marking for layout for free in layoutBlockFlow(), if
pageLogicalHeightChanged, but that only goes one level deep. Eliminate the need
for layout in situations like this.
Prior to this change, we'd fail on an assert that required that the cached
state of self-collapsing be in sync with reality.
Committed: https://crrev.com/b8a54c69086b8c5210ca896e3b6a7e924c84ae5a
Cr-Commit-Position: refs/heads/master@{#429638}
Patch Set 1 #
Messages
Total messages: 12 (7 generated)
|