In CreateColumnSpanSiblings(), aInitialBlock can be a DetailsFrame.
Therefore, when creating a non-column-span wrapper, we cannot assume
it's always a block frame. We need to use CreateContinuingFrame to
ensure the correct type of continuation is created.
Differential Revision: https://phabricator.services.mozilla.com/D15134
--HG--
extra : moz-landing-system : lando
The width doesn't matter for the tests. It's to fit the 600x600 window
to prevent scrollbar from appearing.
Differential Revision: https://phabricator.services.mozilla.com/D15219
--HG--
extra : moz-landing-system : lando
I should have added this test back in bug 590039 and bug 600428, but I didn't.
Differential Revision: https://phabricator.services.mozilla.com/D14827
--HG--
extra : moz-landing-system : lando
If a ColumnSetWrapperFrame already has column-span children,
ColumnSetWrapperFrame::GetContentInsertionFrame() will return itself to
let WipeContainingBlock() aware this is the case to reframe.
To make this work, we need to move the reframe condition prior to check
NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR bit because the top level
ColumnSetWrapperFrame never has NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR bit
set.
Differential Revision: https://phabricator.services.mozilla.com/D14819
--HG--
extra : moz-landing-system : lando
Add some tests to make sure we clamp the interpolated result with
negative easing function on circle(), ellipse(), and inset().
Depends on D14654
Differential Revision: https://phabricator.services.mozilla.com/D14655
--HG--
extra : moz-landing-system : lando
This also updates some existing annotations to collapse lines with
webrender and not-webrender clauses.
Differential Revision: https://phabricator.services.mozilla.com/D14933
--HG--
extra : moz-landing-system : lando
We should let block-size/min-block-size/max-block-size accept keywords as the
initial value, just like width in vertical writing mode or height in horizontal
writing mode.
Depends on D7536
Differential Revision: https://phabricator.services.mozilla.com/D14320
--HG--
extra : moz-landing-system : lando
Support unprefixed min-content and max-content and treat the prefixed
version as aliases for
1. width, min-width, max-width if inline-axis is horizontal, and
2. height, min-height, max-height if inline-axis is vertical, and
3. inline-size, min-inline-size, max-inline-size, and
4. flex-basis.
Besides, update the test cases to use unprefixed max-content and
min-content.
Depends on D7535
Differential Revision: https://phabricator.services.mozilla.com/D7536
--HG--
extra : moz-landing-system : lando
Bug 1506163 fixed only part of the issue. There are more types of frames
such as table, grid, flex, etc. that create their own block formatting
context.
Instead of propagating NS_FRAME_HAS_MULTI_COLUMN_ANCESTOR to the
children, we explicit carry the bit over to block and inline frames by
checking that their parent doesn't suppress column-span descendants.
Also, remove the unused "onload" from <body> in the tests.
Differential Revision: https://phabricator.services.mozilla.com/D13597
--HG--
extra : moz-landing-system : lando
Coroiu Cristina
Jonathan Kew
Bogdan Tara
Jan-Ivar Bruaroey
Margareta Eliza Balazs
Ting-Yu Lin
quasicomputational
Ting-Yu Lin
Kartikaya Gupta
Andreea Pavel
Wes Kocher
Henri Sivonen
L. David Baron
Cosmin Sabou
Hiroyuki Ikezoe
Razvan Maries
Boris Chiou
Mats Palmgren
arthur.iakab
Dorel Luca
longsonr
Jonathan Kingston
Ciure Andrei
WR Updater Bot
James Graham
Andreas Pehrson
Emilio Cobos Álvarez