These two platforms are the easiest to get started with - as well as accounting for the great majority
of desktop Firefox users.
This patch is based on the OS vendors' lists of fonts shipped with the current version of each OS.
Differential Revision: https://phabricator.services.mozilla.com/D66125
--HG--
extra : moz-landing-system : lando
This replaces and extends the "hidden" flag we currently use on macOS to mark internal system fonts
like .LastResort and .Keyboard that should not be exposed; rather than just a boolean "hidden" flag
we'll have several levels of visibility, some of which the user may opt in to exposing (at the cost
of potentially becoming more fingerprintable).
The current patch assumes three levels besides always-hidden:
Base - fonts that are part of the base OS install and always available
LangPack - fonts that are provided by the OS subject to user's chosen language options
User - user-installed fonts that were not provided by the OS
(This categorization may be subject to revision as we learn more about real-world needs and
configurations.)
Differential Revision: https://phabricator.services.mozilla.com/D66124
--HG--
extra : moz-landing-system : lando
Add interpreter entry support for JS-to-wasm calls that return multiple
values. The returned values will be collected into an array.
Differential Revision: https://phabricator.services.mozilla.com/D68769
--HG--
extra : rebase_source : 176fdf616132e64f23939ac558b77a0972c3e378
extra : source : 1e25841508c8a6b818e0f6b756c4d427a72394e7
With WarpBuilder enabled we failed the Frame-onStep-resumption-05.js jit-test. This
failed because when we are propagating a forced-return and turn off the debugger,
we ignored this forced-return for Ion frames. This patch fixes that test failure.
It also tidies up the code with a ShouldBailoutForDebugger helper function.
Differential Revision: https://phabricator.services.mozilla.com/D69219
--HG--
extra : moz-landing-system : lando
This covers the function.arguments issue discussed in bug 1626294 and the expression
decompiler being disabled for Ion frames (bug 831120). It gets us from 29 to 18 failures
with --ion-eager --no-threads --warp.
I considered looking into the expression decompiler issue more, but it's not easy and
disabling the expression decompiler might be the sanest thing to do anyway to avoid
confusing error messages.
Differential Revision: https://phabricator.services.mozilla.com/D69197
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Make stability.py work with py3 (#22538)
Running wpt run --verify was failing in py3 for 2 reasons:
* Importing modules from the same dir was not working
* iteritems() is not defined for collections
--
wpt-commits: 3637298f9c5198cdf6a91f0a4920f6c1836eb614
wpt-pr: 22538
Automatic update from web-platform-tests
Add two more FCP tests, based on new spec changes (#22515)
Co-authored-by: Noam Rosenthal <noam@webkit.org>
--
wpt-commits: 5721f7843f406054b8e02b0e33ff8e733830cc3d
wpt-pr: 22515
Automatic update from web-platform-tests
[css-flexbox] Move flexitem-stretch-range.html test to WPT
This CL moves flexitem-stretch-range[-expected].html test from
css3/css-flexbox to external/wpt/css/css-flexbox with WPT
styles, adding links to the relevant specs, and test description.
Additionally, this CL removes <p></p> paragraph because it's the
same to the assert.
Bug: 1063749
Change-Id: If2811c22ddb2d38e9bb233d8fca416c8c5f0452d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124280
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754799}
--
wpt-commits: fae595a73489890622c9351f40b8b57dc904d235
wpt-pr: 22520
Automatic update from web-platform-tests
fixup! [css-flexbox] Move flex-flow-auto-margins-no-available-space-assert.html test to WPT
Change 'auto' with 'percentage the test title and file name.
And, the attribute of the bug link rel is changed to 'issue'
with a full bug link.
Bug: 1063749
Change-Id: I0a25c6caa3d3afd6c928bb8bc2b692037c0f57c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2126329
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Cr-Commit-Position: refs/heads/master@{#754778}
--
wpt-commits: 5eb4894a68051e04b14fe471da38dd8817e417ed
wpt-pr: 22517
Automatic update from web-platform-tests
[css-flexbox] Move flexitem-stretch-image.html test to WPT
This CL moves flexitem-stretch-image.html
test from css3/css-flexbox to external/wpt/css/css-flexbox with WPT
styles, adding links to the relevant specs, and test description.
Additionally, this CL adds 100x100-blue.png to
external/wpt/css/css-flexbox/support directory.
Bug: 1063749
Change-Id: I1424f3fb9ca5a79046e3e451393a4eaa0f080347
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2126428
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754775}
--
wpt-commits: 4645d03374fc26707b7cf80ba0649694631fb3ec
wpt-pr: 22519
Automatic update from web-platform-tests
[css-flexbox] Move flexitem-percent-height-change.html test to WPT
This CL moves flexitem-percent-height-change.html test from
css3/css-flexbox to external/wpt/css/css-flexbox with WPT
styles, adding links to the relevant specs, and test description.
Bug: 1063749
Change-Id: I265c8cc40707ffa6cffbacb544aea66add617658
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124278
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754774}
--
wpt-commits: 66b81958d0fb22f77a8b19cd7ed4fc9f8c235809
wpt-pr: 22518
Automatic update from web-platform-tests
[LayoutNG] Fixes OOF min/max sizes for nodes w/ %-dependent children.
Previously we just passed in the containing block size, however this was
incorrect for the following case:
<div style="position: relative; height: 200px;">
<div style="position: absolute; top: 0; bottom: 100px;">
<canvas width=1 height=1 style="height: 100%;"></canvas>
</div>
</div>
This pre-calculates the block-size of the OOF-positioned element, and
pass it into the NGBlockNode::MinMaxSizes pass.
Change-Id: I897dc6f9c157bfa1ae63f9821cdb6ed03a218322
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122854
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754763}
--
wpt-commits: f4afb725eca2a7765da4038b6e6f66745b642006
wpt-pr: 22546
Automatic update from web-platform-tests
CSS parser and layout support for the 'page' property.
There were already some stubs for the 'page' property, but it couldn't
be used for anything. Move it behind a runtime flag and implement it.
Also add legacy layout engine support. Will add to LayoutNG once it
supports printing.
Bug: 1053768
Change-Id: I2b7eff133c925a67ef36db4b6fa259cf934abf75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2126708
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754753}
--
wpt-commits: d0418fc79cf3142bd69d9e488611ef5574bd27c8
wpt-pr: 22540
Automatic update from web-platform-tests
Added Badging API Web Platform Tests.
The [Badging API](https://wicg.github.io/badging/) is a new API
allowing the setting of application/document badges. This change
converts the Badging API web tests into Web Platform Tests.
This change adds a no-op MockBadgeService to the content_shell.
This is necessary because the RenderProcessHostImpl will terminate
the render process if unknown Mojo messages are received.
Bug: 1051684
Change-Id: I61e29b8f197a754fea489ebb2d0dcd41484f6cf4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2088297
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Matt Giuca <mgiuca@chromium.org>
Commit-Queue: Chris Mumford <cmumford@google.com>
Cr-Commit-Position: refs/heads/master@{#754676}
--
wpt-commits: 051ca830ad86d533cb17ad35fe654a7d04d86fb3
wpt-pr: 22105
Automatic update from web-platform-tests
[css-flexbox]: Migrate flexbox-with-multi-column-property.html to WPT
This CL moves flexbox-with-multi-column-property.html from
css3/flexbox/ to external/wpt/css/css-flexbox/. It also adds
links and references to the related spec, and expected behavior.
Last, it replaces uses of -webkit-column-* by their respective
column-* counterparts.
Relevant spec change: https://github.com/w3c/csswg-drafts/issues/1364
([css-multicol-1][css-flexbox-1][css-grid-1] Clarify that column-*
properties only apply to block containers).
BUG=1063749
R=dgrogan@chromium.org
Change-Id: Icd31c1974af431bd8cd6de94970e4e29137a669e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127294
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754649}
--
wpt-commits: 79a262ea111267cc1cc5c436f872ae5e8daaeec1
wpt-pr: 22534
Automatic update from web-platform-tests
[css-flexbox]: Migrate negative-overflow.html to WPT
This CL moves negative-overflow.html from css3/flexbox to
external/wpt/css/css-flexbox.
<link ref=help|match> tags were added, as well as <title>.
CSS and JS referenced paths were also updated.
BUG=1063749
R=dgrogan@chromium.org
Change-Id: I4091fc870f51a31ac9fbac51b42eaa6cd33a16de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2127607
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754637}
--
wpt-commits: ea0cab74182aaef81fc73242f60c23be39b8007b
wpt-pr: 22547
Automatic update from web-platform-tests
cancelScheduledValues removes setValueCurveAtTime
If the time requested in cancelScheduledValues overlaps the time of a
setValueCurveAtTime, then the setValueCurveAtTime is also removed.
Bug: 1063502
Change-Id: I6e8bd4bf802cd76f26b46f60905f977ab76d5b5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2121353
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754612}
--
wpt-commits: 23ddfb672d1e986be516b78d4e154e47b1ef0452
wpt-pr: 22508
Automatic update from web-platform-tests
Add test for FCP based on directionality (#22516)
Co-authored-by: Noam Rosenthal <noam@webkit.org>
--
wpt-commits: 713a89e5dd5a4df25803ad60294e0c408d8a4ae2
wpt-pr: 22516
Automatic update from web-platform-tests
Fix rounding in DelayNode buffer size calculation
DelayNode needs to buffer maxDelayTime worth of sample frames,
plus one for interpolation. If maxDelayTime isn't an integer
number of frames, we have to round it up -- otherwise the buffer
ends up one frame too short, causing the interpolation to wrap
around and access the newest input instead of the oldest.
Bug: 1065110
Change-Id: Ia47dbd07c3b3b48734c03442a020d76a680eaaa0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2122852
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754595}
--
wpt-commits: ca667500feb6f684f412630a9814cc17e4fde670
wpt-pr: 22506
Automatic update from web-platform-tests
[COEP] Make WPT testing reporting to have a long timeout.
The reporting API queue reports and send in a batch after a few seconds.
This might be after the WPT test timeout (10s).
This patch switch the timeout to be 'long' for those tests.
TBR=ahemery@chromium.org
Bug: None.
Change-Id: I1cb4ec0f62d43178204e2d1218887ec68000915e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124835
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754514}
--
wpt-commits: 14988fd1cadc467adf9d87e237729e90c9e49868
wpt-pr: 22523
Automatic update from web-platform-tests
Isolate activation-gated APIs from user-activation WPTs.
This CL isolates activation-gated APIs from the tests because those API
behavior may depend on other browser-defined things.
Four specific changes done here are:
- Isolate a basic activation test as non-tentative.
- Replace an existing wpt with a chained setTimeout test.
- Isolate tests for same/cross-origin consumption behavior.
- Clarify tests for same/cross-origin navigation behavior.
Change-Id: I0a7e6d87fc8ed088cd162bbaa8584e8ea7710239
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2110685
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754529}
--
wpt-commits: bb678e5e0eab0abc4ab46f42c2f8ef91e0cbf904
wpt-pr: 22423
Automatic update from web-platform-tests
[css-flexbox] Rename flex-minimum-size-002.html
This CL is a follow-up of https://crrev.com/c/2123500. It renames
flex-minimum-size-002.html to flex-minimum-size-001.html.
From the previous CL[1], min-size-auto.html was renamed to
flex-minimum-size-002.html and landed given that minimum-size-image.html
was supposed to be renamed to flex-minimum-size-001.html on the CL[2].
But, minimum-size-image.html was eventually renamed to
flex-aspect-ratio-img-column-011.html and there is no longer
flex-minimum-size-001.html.
So, rename flex-minimum-size-002.html to flex-minimum-size-001.html.
[1]https://crrev.com/c/2123500
[2]https://crrev.com/c/2123499
Bug: 1063749
Change-Id: Ic04772fdd0eb2b8cde09d43a735e6f34e017bf83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2123956
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754503}
--
wpt-commits: 4e3194253a33d974879757c6afef79c76b05aa9d
wpt-pr: 22522
--HG--
rename : testing/web-platform/tests/css/css-flexbox/flex-minimum-size-002.html => testing/web-platform/tests/css/css-flexbox/flex-minimum-size-001.html
Automatic update from web-platform-tests
[ScrollTimeline] Do not show scrollbar to bypass flakiness on early Mac
The flaky tests are not related to worklet animations because it's the
reference file that is not painted correctly.
Mac scrollbars have their own painting path and they paint greedily.
There might be a race condition on the order of painting that caused the
scrollbar being completely black.
Bug: 946534
Change-Id: I5e2fab05e7a5ee5ec09dcab2a03606ca5ce1fd0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124296
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754480}
--
wpt-commits: fba97eee58d4bf45b5c2cadc2eac780b78a8fe95
wpt-pr: 22496
Automatic update from web-platform-tests
Let StyleCascade own MatchResult and interpolations
There is currently a bug where font-relative units in the base style
are not responsive to font-affecting animations (even with issue 437689
fixed) _if_ the element hits the MatchedPropertiesCache. This can
easily happen if two identical elements (with the same MatchResult)
undergo the same CSS animation.
The reason this bug exists is in StyleResolver::
CascadeAndApplyMatchedProperties. Notice that, when
cache_success.IsFullCacheHit() is true in that function, we return
immediately, and never Analyze the MatchResult. In other words, the
MatchResult is _there_, fully populated (we're using it as the cache
key after all), but we never let the StyleCascade actually Analyze it,
which is the source of the bug. When we later apply animations
(see StyleResolver::ApplyAnimatedStandardProperties), we Analyze the
animations/transitions _only_. This was done on purpose, as too much
Analyzing is expensive. Hence, during ApplyAnimatedStandardProperties,
I assumed that either:
- We would hit the base computed style optimization, and hence the
MatchResult would be empty, and there is no need to analyze it, or
- We would not hit the base computed style optimization, and the
MatchResult object would be populated and Analyzed already.
But of course, I forgot about the third option: based computed style
optimization miss, but a hit on the matched properties cache. In that
case the we have a non-empty MatchResult that haven't been Analyzed.
To fix this, we could have simply Analyzed the MatchResult in
ApplyAnimatedStandardProperties (potentially a second time). But this
is inefficient. I don't want to do that.
Instead, this CL moves the MatchResult ownership (and
CascadeInterpolation ownership) to StyleCascade itself. It also adds
flags which tells us what needs to be analyzed. Using this, we can
now analyze-on-demand during Apply, which means we analyze exactly the
amount we need to analyze, also in the case where an animation frame
hits the MatchedProperties cache.
It also makes for a far more sensible (but still not perfect)
StyleCascade API, compared to "manually" analyzing.
Note that this CL also removes filtering Analyze-time. This means
that e.g. for ::marker, we add declarations to the CascadeMap that
we know aren't going to be applied (as they are filtered in the Apply
step). This is because analyze-on-demand is not easily compatible with
this kind of filtering. For example, when dealing with inherited-only
cache hits, we first try to apply the inherited properties only.
If the font or zoom was modified, we need to apply the non-inherited
properties after all. And for that second apply pass, we obviously need
all properties to have been analyzed before, not just the inherited
properties.
Bug: 1065387, 437689
Change-Id: I7e9b7f33fc12f055603e789d3ae700d5a7a3dbbf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124649
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754457}
--
wpt-commits: 724eb3d3feb35cb1d762b9196842917aafaf0399
wpt-pr: 22527
