Closed Bug 1467656 Opened 7 years ago Closed 7 years ago

[wpt-sync] Sync PR 11392 - Correctly detect when a multicol descendant becomes or ceases to be a containing block.

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 11392 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/11392 Details from upstream follow. Morten Stenshorne <mstensho@chromium.org> wrote: > Correctly detect when a multicol descendant becomes or ceases to be a containing block. > > When a descendant of a multicol container becomes a containing block for > out-of-flow positioned objects, or ceases to be one, out-of-flow > positioned children may become or cease to be a part of the > fragmentation context. > > We didn't detect this correctly. We only checked for transforms (in > addition to position:relative). Make sure we check for filters too, now > that those also establish containing blocks. > > Bug: 847328 > Change-Id: I7ab47860bb8d9f8d9b0256b25e1123c34f73e8f4 > > Reviewed-on: https://chromium-review.googlesource.com/1089336 > WPT-Export-Revision: 4dca0c6f6ad74a71445922d230154f14f32a8a6c
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 1 tests and 1 subtests OK : 1 PASS : 1
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/fc06c6dd1dad [wpt PR 11392] - Correctly detect when a multicol descendant becomes or ceases to be a containing block., a=testonly
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/mozilla-inbound/rev/cc3bfa318ea9 [wpt PR 11392] - Correctly detect when a multicol descendant becomes or ceases to be a containing block., a=testonly
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.