e29528c47bfbd8f3a000eebe445d6a5fde4a9c61: Bug 1732646 [wpt PR 30871] - [credentialless] Update redirect behavior., a=testonly
Arthur Sonzogni <arthursonzogni@chromium.org> - Sat, 02 Oct 2021 13:00:16 +0000 - rev 594145
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732646 [wpt PR 30871] - [credentialless] Update redirect behavior., a=testonly Automatic update from web-platform-tests [credentialless] Update redirect behavior. In the Fetch specification PR, we changed our mind and decided to omit credentials as soon as there at least one cross-origin request. Previously, only the current URL was taken into account. See: https://github.com/whatwg/fetch/pull/1229#discussion_r712175485 Bug: 1175099 Change-Id: I308281bdab95be264ca7a2ef990341bddd0e9bc2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3168346 Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/main@{#923884} -- wpt-commits: 2d6d77b3054e9b7f35bdd2b3e7de9b53ecfed7d5 wpt-pr: 30871
f6bdf3be5fcdbf6f0dcd959d3a11d91a0a61986f: Bug 1732073 [wpt PR 30904] - [layout] Fix metrics DCHECK., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Sat, 02 Oct 2021 13:00:12 +0000 - rev 594144
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732073 [wpt PR 30904] - [layout] Fix metrics DCHECK., a=testonly Automatic update from web-platform-tests [layout] Fix metrics DCHECK. Previously we'd hit this check quite often in clusterfuzz: Crash Type: CHECK failure Crash Address: Crash State: !metrics_.IsEmpty() || IsEmptyLineBox() in ng_physical_line_box_fragment.cc blink::NGPhysicalLineBoxFragment::NGPhysicalLineBoxFragment scoped_refptr<blink::NGPhysicalLineBoxFragment> base::MakeRefCounted<blink::NGPh This particular testcase is an atomic-inline with a saturated -ve margin at the bottom. As a result the call to BaselineMetrics within the inline layout algorithm: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/layout/ng/inline/ng_inline_layout_algorithm.cc;l=589-593?q=baselinemetrics&ss=chromium would result in a FontHeight of [LayoutUnit::Min(), LayoutUnit()]. This would return true for FontHeight::IsEmpty() as it only checked the ascent. This fixes the issue by checking the descent as will within IsEmpty(). Bug: 1243485 Change-Id: I63d9dd57a6e08dd361f21c68b60fabe025e7befc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3173984 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#923759} -- wpt-commits: 30619eb589be9a693c0a4535c296826ef5fcd617 wpt-pr: 30904
57d92dad02998c5490ede3a70e86f07791f097c8: Bug 1732070 [wpt PR 30840] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 23 Sep 2021 15:07:35 +0000 - rev 594143
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732070 [wpt PR 30840] - Update wpt metadata, a=testonly wpt-pr: 30840 wpt-type: metadata
38f34b6424af2518d0006b2b78266a0693842714: Bug 1732070 [wpt PR 30840] - [css-fonts] Add parsing tests for font-palette-values, a=testonly
Myles C. Maxfield <mmaxfield@apple.com> - Sat, 02 Oct 2021 12:59:49 +0000 - rev 594142
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732070 [wpt PR 30840] - [css-fonts] Add parsing tests for font-palette-values, a=testonly Automatic update from web-platform-tests [css-fonts] Add parsing tests for font-palette-values (#30840) -- wpt-commits: af14bcce007b6a27904084e7ea05ef022144137a wpt-pr: 30840
e8408abd45440bb1bc8abe3ca39bcf6f01cd728a: Bug 1732068 [wpt PR 30907] - Fix wpt resize observer test, a=testonly
Aleks Totic <atotic@chromium.org> - Sat, 02 Oct 2021 12:59:45 +0000 - rev 594141
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732068 [wpt PR 30907] - Fix wpt resize observer test, a=testonly Automatic update from web-platform-tests Fix wpt resize observer test See https://github.com/w3c/csswg-drafts/issues/6610#issuecomment-918778072 smfr complained that our tests are spewing RO errors, and they were. This fixes it Change-Id: I8074082a2a02e5b1a80971fcc31993ae434386a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3174434 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Aleks Totic <atotic@chromium.org> Cr-Commit-Position: refs/heads/main@{#923664} -- wpt-commits: 8dffdd0c1a6c69234deb519cbe9399d95614bf4f wpt-pr: 30907
e6d16b1e136b3e99593c064bced28cd90f186677: Bug 1732067 [wpt PR 30813] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 23 Sep 2021 15:03:44 +0000 - rev 594140
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732067 [wpt PR 30813] - Update wpt metadata, a=testonly wpt-pr: 30813 wpt-type: metadata
8bcfd340fe2395cc7cc6d8eee7bd29928a372df6: Bug 1732067 [wpt PR 30813] - CSS highlight processing model, a=testonly
Delan Azabani <dazabani@igalia.com> - Sat, 02 Oct 2021 12:59:38 +0000 - rev 594139
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732067 [wpt PR 30813] - CSS highlight processing model, a=testonly Automatic update from web-platform-tests CSS highlight processing model This patch implements the inheritance-based propagation for highlight pseudo-elements, as described in css-pseudo’s #highlight-cascade and introduced in w3c/csswg-drafts#2474. Highlight pseudos like ::selection were historically implemented such that only the ::selection selector (*::selection) worked intuitively. The spec’s processing model essentially makes it possible to define both general ::selection styles and more specific ::selection styles. We add a feature (HighlightInheritance) and a new computed style extra field of type scoped_refptr<StyleHighlightData>, which in turn points to four refcounted ComputedStyle instances, one for each highlight. Only a handful of properties are applicable, but reusing ComputedStyle like this simplifies the applying code, and allows us to share many of the field groups between instances anyway. We update the initial style singleton to point to a set of four empty highlight styles, which we only use when the feature is enabled. When the feature is disabled (or resolving custom ::highlight styles), there is no functional change. Highlight styles are lazily computed on paint’s demand, inherit only from the originating element styles, and we store the result in the Element’s pseudo cache (StyleCachedData). When the feature is enabled, we compute highlight styles during the originating element’s recalc (RecalcOwnStyle), skipping any highlight pseudos that the element had no matching rules for (a question that can already be answered thanks to pseudo bits). Style resolution is largely unchanged: we start with default styles, then use output of the cascade to change those styles. But defaulting is much easier for highlight styles: all properties are inherited, so we can simply clone the whole ComputedStyle. Relevant test page and screenshots: • https://bucket.daz.cat/work/igalia/0/8.html • https://bucket.daz.cat/4f37833aa15299a5.png (before) • https://bucket.daz.cat/67d2abdd9bcda17c.png (after) WPT already has some tests (css/css-pseudo/cascade-highlight-*), but more thorough test coverage will land in these patches: • https://github.com/web-platform-tests/wpt/pull/30688 • https://github.com/web-platform-tests/wpt/pull/30692 Bug: 1024156 Change-Id: I1f54f36ef2ac80165261a3f80d3a21cdf359c199 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2850068 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by: Mason Freed <masonf@chromium.org> Commit-Queue: Delan Azabani <dazabani@igalia.com> Cr-Commit-Position: refs/heads/main@{#923485} -- wpt-commits: 4eb26e6225ed30a6cfc73eb743eaf9f59086521c wpt-pr: 30813
7f4a9de37e6ef7f2cbeb5302aa3f9898cdeee108: Bug 1732066 [wpt PR 30905] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Sep 2021 13:11:05 +0000 - rev 594138
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732066 [wpt PR 30905] - Update wpt metadata, a=testonly wpt-pr: 30905 wpt-type: metadata
8c4b766799fe208b874d3ace15d1370fd081decc: Bug 1732066 [wpt PR 30905] - Rename some css highlight test cases, a=testonly
WeizhongX <77710146+WeizhongX@users.noreply.github.com> - Sat, 02 Oct 2021 12:59:24 +0000 - rev 594137
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732066 [wpt PR 30905] - Rename some css highlight test cases, a=testonly Automatic update from web-platform-tests Rename some css highlight test cases (#30905) We now have tests with the same file name in chromium and wpt upstream, which cause a merge conflict when exporting and importing the changes. Rename the file names at upstream to resolve such conflict. -- wpt-commits: 4f50940a6a8864ef73232048f7d41892216cb080 wpt-pr: 30905
566c6d18c0dc4f331f7198745d2f53e597e77576: Bug 1732065 [wpt PR 30906] - Revert "[@layer] Fix cascade ordering of inline style and layered style", a=testonly
Xiaocheng Hu <xiaochengh@chromium.org> - Sat, 02 Oct 2021 12:59:18 +0000 - rev 594136
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732065 [wpt PR 30906] - Revert "[@layer] Fix cascade ordering of inline style and layered style", a=testonly Automatic update from web-platform-tests Revert "[@layer] Fix cascade ordering of inline style and layered style" This reverts commit 65f6b482860b4dda8933a19f1f4b4115c3812b41. Reason for revert: Caused b/200698937 Original change's description: > [@layer] Fix cascade ordering of inline style and layered style > > This patch adds a new flag to MatchResult and CascadePriority to > indicate if a declaration is from inline style or other style sheets, so > that we can compare inline style and other layered style correctly. > > Without this flag, currently we are treating inline style as regular > declarations in the implicit outer layer, and therefore mistakenly > override it with layered style rules in other style sheets. > > Bug: 1095765 > Change-Id: I10dbafcf9721fc5b8a5b11edeaeab48c82df86d4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3167095 > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> > Reviewed-by: Rune Lillesveen <futhark@chromium.org> > Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> > Cr-Commit-Position: refs/heads/main@{#923216} Bug: 1095765 Change-Id: I93b6caffbaa777338f1b05769f85ae2becbdabab No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3174089 Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#923601} -- wpt-commits: 7f0082f448285e9adcae0373042618dbb704baee wpt-pr: 30906
baf896beca3769ee588583ec96c950cb619246ee: Bug 1732063 [wpt PR 30874] - Handle BR clear=all correctly in block fragmentation., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Sat, 02 Oct 2021 12:59:13 +0000 - rev 594135
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732063 [wpt PR 30874] - Handle BR clear=all correctly in block fragmentation., a=testonly Automatic update from web-platform-tests Handle BR clear=all correctly in block fragmentation. BR clearance is special in that it's applied *after* the content (the line), while regular CSS clearance is about adding spacing *before* something. If clearance from a BR element crosses fragmentainer boundaries, do two things: 1. If the line has content before the BR clear element, add an additional line break before it, so that we can fit everything on the line before the BR in the correct fragmentainer. In addition to looking good, the line may contain floats, and we cannot push those ahead of us, as we'd get no progress that way! 2. Abort layout of a line with an isolated BR clear element, if it needs to be pushed to a subsequent fragmentainer, and ignore any orphans and widows requests in this case (we're creating a line that doesn't really exist, spec-wise). Layout is aborted with NGLayoutResult::kOutOfFragmentainerSpace. We were already handling kOutOfFragmentainerSpace layout abortions for new-FC children, as this was already supported for nested multicol containers. Now that we also support it for same-FC children (such as lines), we need to update the code to not assume that layout was successful. Handle block fragmentation a bit earlier (so that we'll return before attempting to access the resulting fragment), and add checks for successful layout where needed. It might be possible to add real support for trailing clearance to the block fragmentation engine, but it just seemed like an unreasonably large effort (especially maintenance-wise) for such a corner-case. This fixes the following tests in external/wpt/css/CSS2/floats-clear/ (not part of the virtual/layout_ng_block_frag/ testsuite) when LayoutNGBlockFragmentation is enabled: floats-clear-multicol-000.html floats-clear-multicol-001.html floats-clear-multicol-balancing-000.html floats-clear-multicol-balancing-001.html Bug: 829028 Change-Id: If3ebb307cac4afd388e5edfc2ac576510afe283e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3168884 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#923551} -- wpt-commits: 98d42726729f9b673ea057d48de64b7273b82518 wpt-pr: 30874
2b771166aff453412e0a55d6cd5e986521648d1b: Bug 1732062 [wpt PR 30887] - c-v: Distinguish the type of forced updates., a=testonly
Vladimir Levin <vmpstr@chromium.org> - Sat, 02 Oct 2021 12:59:09 +0000 - rev 594134
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732062 [wpt PR 30887] - c-v: Distinguish the type of forced updates., a=testonly Automatic update from web-platform-tests c-v: Distinguish the type of forced updates. This patch ensures that we can force an update for style without forcing layout, etc. This is useful since we need to determine whether we have a lock that blocks, for e.g. layout, and if we force a lock it's unclear whether layout would be updated without this patch. With the patch, functions like UpdateStyleAndLayoutTree only force style updates. R=chrishtr@chromium.org, jarhar@chromium.org Fixed: 1250742 Change-Id: I9856acbcabedfb0b232518b438ca43a16a0cfd09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3168328 Commit-Queue: vmpstr <vmpstr@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#923524} -- wpt-commits: bc1925dd5349f8beec43c0f94a2c3e1cdd2e8466 wpt-pr: 30887
698d10acdee38a33cd4bcfe67c73ab2758e5e988: Bug 1732060 [wpt PR 30876] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 23 Sep 2021 14:56:22 +0000 - rev 594133
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732060 [wpt PR 30876] - Update wpt metadata, a=testonly wpt-pr: 30876 wpt-type: metadata
ce5f03f5d53e11327a0b6c3ef8364a8bb3a62c6f: Bug 1732060 [wpt PR 30876] - Don't include BR clearance in the line's height., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Sat, 02 Oct 2021 12:59:01 +0000 - rev 594132
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732060 [wpt PR 30876] - Don't include BR clearance in the line's height., a=testonly Automatic update from web-platform-tests Don't include BR clearance in the line's height. Including clearance in the line height may result in tall monolithic content, which is problematic for block fragmentation, especially for column balancing. Instead, store trailing clearance in the layout result, so that the block layout algorithm can add it to the layout position for subsequent content. We already use a similar trick for ruby annotations, and some care is required so that we don't move back above the clearance offset when canceling ruby annotations overflow (which happens in some cases). There was no test coverage for this, so added three tests for that (they pass both and without this CL). Also added a multicol test that demonstrates what this fixes in column balancing. Bug: 829028 Change-Id: I84e58326e9ada78e3f29ad01d8043a173626aea3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3168645 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#923502} -- wpt-commits: faa9a85d068538c986ba01119789194f92f8d344 wpt-pr: 30876
214c5b0c273eba7803aaa105eae0e33460e8ab65: Bug 1732059 [wpt PR 30891] - Remove stashed request headers for speculative parser tests, a=testonly
Mason Freed <masonf@chromium.org> - Sat, 02 Oct 2021 12:58:51 +0000 - rev 594131
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732059 [wpt PR 30891] - Remove stashed request headers for speculative parser tests, a=testonly Automatic update from web-platform-tests Remove stashed request headers for speculative parser tests The old code would append all of the request headers for the request to the stashed value. That causes the failure string for all dependent tests to change when, e.g. the User-Agent string changes due to the test being run on a different bot. This CL removes the headers, as those seem only useful for debugging, and are causing lots of flaky behavior on at least Chromium bots. Prior failure message: FAIL Speculative parsing, document.write(): link-rel-stylesheet-disabled Unhandled rejection: assert_equals: speculative case incorrectly fetched expected "" but got "param-encodingcheck: %C4%9E\r\nHost: web-platform.test:8001\nConnection: keep-alive\nUser-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/999.77.34.5 Safari/537.36\nAccept: text/css,*/*;q=0.1\nReferer: http://web-platform.test:8001/html/syntax/speculative-parsing/generated/document-write/link-rel-stylesheet-disabled.tentative.sub.html\nAccept-Encoding: gzip, deflate\nAccept-Language: en-us,en\n\n" New failure message: FAIL Speculative parsing, document.write(): link-rel-stylesheet-disabled Unhandled rejection: assert_equals: speculative case incorrectly fetched expected "" but got "param-encodingcheck: %C4%9E\r\n" Fixed: 1250457,1249920,1249921,1249954,1250003,1250004 Bug: 1144176 Change-Id: I45dbbb8794c6bf2d5e962cecf531e06a7af09160 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3170927 Commit-Queue: Mason Freed <masonf@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#923491} -- wpt-commits: 2dc665185ccac1b30667190b05e5e0cd9885d7c5 wpt-pr: 30891
cc93ca5e9e469394e9b1406d44ff031d35f9a970: Bug 1732058 [wpt PR 30807] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 23 Sep 2021 14:48:38 +0000 - rev 594130
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732058 [wpt PR 30807] - Update wpt metadata, a=testonly wpt-pr: 30807 wpt-type: metadata
ca0fc4ff17636bd561c8e84ee210c60b9cc5b284: Bug 1732058 [wpt PR 30807] - Use interpolation at the endpoints of animations., a=testonly
L. David Baron <dbaron@chromium.org> - Sat, 02 Oct 2021 12:58:43 +0000 - rev 594129
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732058 [wpt PR 30807] - Use interpolation at the endpoints of animations., a=testonly Automatic update from web-platform-tests Use interpolation at the endpoints of animations. Use interpolation at the endpoints of animations (by removing various optimizations to return the endpoint values at the endpoints), since it's needed to get the correct axis for animation of the 'rotate' property, the correct conversion away from a 'none' value at one endpoint for the 'rotate', 'scale', and 'translate' properties, and correct list lengths for list-valued properties that can interpolate between lists of mismatched lengths, whether by repeating to the least common multiple length (stroke-dasharray) or filling the shorter list with no-op or zero values (filter, backdrop-filter, box-shadow, text-shadow, some registered custom properties). The changes to translate-composition.html and scale-composition.html cause Firefox to pass the tests whose expectations are being modified, and thus, like Chrome, pass the entire file (whereas they cause Safari to fail additional tests). The test changes are discussed further in https://github.com/web-platform-tests/wpt/issues/30377 . The differences between the test expectations for background-image (where the test expects discrete animation, per the spec) and for -webkit-mask-image (where the test expects -webkit-cross-fade()) is rather suspicious, but I've left the difference as-is for now. Fixed: 1026169, 1180834 Change-Id: I6320b74b0aff29989a748fab1bff78b91426701e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3139948 Reviewed-by: Kevin Ellis <kevers@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: David Baron <dbaron@chromium.org> Cr-Commit-Position: refs/heads/main@{#923427} -- wpt-commits: 30e724ac90157333d34198f0c29131b2e2a6b1da wpt-pr: 30807
8a3239413605c994f933ed9ccf2e8d95d4fd1dd9: Bug 1732054 [wpt PR 30849] - Support 'small-caps' keyword for font-synthesis property, a=testonly
Munira Tursunova <moonira@google.com> - Sat, 02 Oct 2021 11:06:51 +0000 - rev 594128
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1732054 [wpt PR 30849] - Support 'small-caps' keyword for font-synthesis property, a=testonly Automatic update from web-platform-tests Support 'small-caps' keyword for font-synthesis property Implement support of 'small-caps' keyword for font-synthethis shorthand property. Enabled corresponding WPT tests by removing existing fail expectations. Bug: 509989 Change-Id: Ib089c2f6742f81eecf471b3c75b46018234939ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3168780 Reviewed-by: Dominik Röttsches <drott@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/main@{#923339} -- wpt-commits: 4cedd9779a3d4ed46589747150a940e04cbbddb2 wpt-pr: 30849
cf559311e933cb686bdb2ada490b47ad5138d235: Bug 1716030 [wpt PR 29346] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 22 Sep 2021 17:33:40 +0000 - rev 594127
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1716030 [wpt PR 29346] - Update wpt metadata, a=testonly wpt-pr: 29346 wpt-type: metadata
b741b9d58b45f95ecd7b8d7ae3f177fb60eba635: Bug 1716030 [wpt PR 29346] - Use assert_approx_equals in css/css-text/i18n, a=testonly
Lauryn Menard <lauryn.menard@gmail.com> - Sat, 02 Oct 2021 11:06:43 +0000 - rev 594126
Push 38841 by ncsoregi@mozilla.com at Sun, 03 Oct 2021 10:06:40 +0000
Bug 1716030 [wpt PR 29346] - Use assert_approx_equals in css/css-text/i18n, a=testonly Automatic update from web-platform-tests Use assert_approx_equals in css/css-text/i18n Fixes #25084. -- wpt-commits: 0f6907dc33c953257475f7bf9fe37b6c53a424f3 wpt-pr: 29346
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip