Bug 1514995 [wpt PR 14582] - Update wpt metadata, a=testonly wpt-pr: 14582 wpt-type: metadata

Bug 1514995 [wpt PR 14582] - [LayoutNG] Remove NGLayoutResult::PositionedFloats., a=testonly Automatic update from web-platform-tests [LayoutNG] Remove NGLayoutResult::PositionedFloats. This patch does a few (related) things: 1) Makes floats children of their appropriate inline-level container. Previously we weren't doing this, which was making OOF positioned children skip their correct containing block. Now they'll correctly get captured, during NGContainerFragmentBuilder::AddChild. 2) Now that float children are in the "correct" position within the fragment tree, we can now paint them. This changes the ng_box_fragment_painter.cc to paint inline-level floats and makes sure we set the NGPaintFragment correctly. 3) Lots of subtle painting layer changes. As floats are now in the "correct" fragment tree position, self-painting layers of inline-level elements (spans, etc) need to know that they are able to paint floats, determine position correctly, etc. The major behaviour changes are: <div> text <span style="position: relative;">abc <div style="float: left;"> <div style="position: absolute;"></div> </div> def</span> </div> The OOF positioned child will be contained within the <span> <div> <span style="position: relative; top: 100px;"> <div style="float: left;"></div></span> </div> The float will also shift by 100px, which previously wasn't the case. Additionally filter: blur(2px); etc, will be applied to the float. Change-Id: I61a2638cb1472f1a22f5994688d69fb6fffb8b88 Reviewed-on: https://chromium-review.googlesource.com/c/1365984 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#619070} -- wpt-commits: a1cc8c0bda2dc784ab07a34473c8f27d4bad7518 wpt-pr: 14582

Bug 1516494 [wpt PR 14677] - Update wpt metadata, a=testonly wpt-pr: 14677 wpt-type: metadata

Bug 1516494 [wpt PR 14677] - [css-text] Tab size lengths inherit as lengths, a=testonly Automatic update from web-platform-tests [css-text] Tab size lengths inherit as lengths -- wpt-commits: 900ad7284cb30dc3620e348a7eb5ff0f69dfd519 wpt-pr: 14677

Bug 1516492 [wpt PR 14676] - Update wpt metadata, a=testonly wpt-pr: 14676 wpt-type: metadata

Bug 1516492 [wpt PR 14676] - [css-text] Check tab-size behavior under various white-space values, a=testonly Automatic update from web-platform-tests [css-text] Check tab-size behavior under various white-space values -- wpt-commits: d02832384b2de958c40dc7606d35c8fbdef7bbde wpt-pr: 14676

Bug 1515571 [wpt PR 14611] - Move visual overflow computation into the descendant-dependent tree walk., a=testonly Automatic update from web-platform-tests Move visual overflow computation into the descendant-dependent tree walk. Visual overflow is different than layout overflow, and is used in: * Pre-CAP (aka SPv1) compositing (to determine bounds of composited layers) * Paint/raster invalidation (to determine whether drawn areas on the screen change). Tested: There were multiple layout or unit tests which failed due to the absence of each of the parts of this CL. We appear to have quite good test coverage of this logic. Bug: 892347 Change-Id: I1fadc5d600bda50992d9aba203319ed2d5059aac Reviewed-on: https://chromium-review.googlesource.com/c/1366767 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/master@{#618986} -- wpt-commits: 1d4dcbf0a3c4a1ded76ca96f3450261fec1d2266 wpt-pr: 14611

Bug 1516476 [wpt PR 14675] - Async Clipboard: Refactor tests to use arrow functions, a=testonly Automatic update from web-platform-tests Async Clipboard: Refactor tests to use arrow functions Bug: 896479 Change-Id: I2a9cd18fa812ff9bd9f8b51923b4fe373f593582 Reviewed-on: https://chromium-review.googlesource.com/c/1391408 Commit-Queue: Darwin Huang <huangdarwin@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#618984} -- wpt-commits: f74e788a986b4630f12fdf5f1aeba913b6328cad wpt-pr: 14675

Bug 1516192 [wpt PR 14659] - Claim to support testdriver in servodriver, a=testonly Automatic update from web-platform-tests Claim to support testdriver in servodriver -- wpt-commits: 259d0612af038d14f2cd889a14a3adb6c9e96d96 wpt-pr: 14659

Bug 1516407 [wpt PR 14668] - Update wpt metadata, a=testonly wpt-pr: 14668 wpt-type: metadata

Bug 1516407 [wpt PR 14668] - [css-text] Add "anywhere" equivalents to "break-word" tests, a=testonly Automatic update from web-platform-tests [css-text] Add "anywhere" equivalents to "break-word" tests -- wpt-commits: cd31531b419737b67c3201f89eaa1406afe27948 wpt-pr: 14668

Bug 1516405 [wpt PR 14667] - [css-text] overflow-wrap:break-word does not change the min-content size, a=testonly Automatic update from web-platform-tests [css-text] overflow-wrap:break-word does not change the min-content size -- wpt-commits: 69c2a2b356e180785ce276fd842959193bcb5a3c wpt-pr: 14667

Bug 1498964 [wpt PR 13510] - Update wpt metadata, a=testonly wpt-pr: 13510 wpt-type: metadata

Bug 1498964 [wpt PR 13510] - [css-text] Rework some tests to avoid anti aliasing issues, a=testonly Automatic update from web-platform-tests [css-text-3] Rework text-indent tests These tests used to have anti aliasing artefacts. A previous commit (cf1491254cca) solved that, at the expense of making the tests impractical to review manually, and no longer self descriptive. This change fixes that, while keeping the tests robust to anti aliasing artefacts. -- wpt-commits: 01bcaf75435db95e0ba06df42ccbd35aeef33f2f wpt-pr: 13510

Bug 1456739 [wpt PR 10627] - [css-text] white-space and intrinsic sizing, a=testonly Automatic update from web-platform-tests [css-text] overflow-wrap and intrinsic sizing Goes together with the spec changes for https://github.com/w3c/csswg-drafts/issues/2465 -- [css-text] break-spaces has moved from overflow-wrap to white-space -- Merge pull request #10627 from frivoal/text-2465 [css-text] white-space and intrinsic sizing -- wpt-commits: b439b5793f217eeb5ec1dd941161f6206ab2938d, ae2ef2d8cf5cab2db0a477411ea7f9cc79f6f737, 67b751ef3b96755111d9f845efd3b21c014d68bc wpt-pr: 10627

Bug 1497754 [wpt PR 13385] - Update wpt metadata, a=testonly wpt-pr: 13385 wpt-type: metadata

Bug 1497754 [wpt PR 13385] - [css-text] text-transform must not disturb shaping in arabic, a=testonly Automatic update from web-platform-tests [css-text] text-transform must not disturb shaping in arabic Related to https://github.com/w3c/csswg-drafts/issues/2135 -- Merge pull request #13385 from frivoal/text-2135 [css-text] text-transform must not disturb shaping in arabic -- wpt-commits: a1e342c18c90f8386adf9e23495814ed6e7f2804, 9b22a2f64e0199794898ae88bf29ae558e2a2f5a wpt-pr: 13385

Bug 1498099 [wpt PR 13461] - Update wpt metadata, a=testonly wpt-pr: 13461 wpt-type: metadata

Bug 1498099 [wpt PR 13461] - [css-text] Test for text-tranform:full-size-kana, a=testonly Automatic update from web-platform-tests [css-text] Improve text-transform:full-size-kana tests Rework the tests from https://github.com/web-platform-tests/wpt/pull/13504, so that: * They fit within 600px × 600px (as generally required for reftests) * They are easier for a human reader to review: being asked whether two characters are the same when the only difference expected is size is much easier if you have a reference for the right and wrong size. Only doing this in tests 001 to 004, as for the rest there's not (always) a corresponding small character. * The test that check that nothing happens on already full-size kana only applies the (ineffective) transform to one character in each pair as otherwise, it isn't really testing anything -- Merge pull request #13461 from frivoal/text-3143 [css-text] Test for text-tranform:full-size-kana -- wpt-commits: cf5dba33625ba1c4491054fa4a0ad3a1243f7a43, a546e84c5c9aa5e1481cfbdeef0d70530c811508 wpt-pr: 13461

Bug 1497386 [wpt PR 13428] - [css-text] plain-text copy & paste does not preserve text-transform, a=testonly Automatic update from web-platform-tests [css-text] plain-text copy & paste does not preserve text-transform This is a test for https://github.com/w3c/csswg-drafts/issues/627 -- Merge pull request #13428 from frivoal/text-627 [css-text] plain-text copy & paste does not preserve text-transform -- wpt-commits: 176d04ddd933ec150424b7f2c923ad6c4519b618, e13446ad8a47fa1643f3afa987d0da950822023b wpt-pr: 13428