Before this patch:
- Consume time merely is the time it takes to push something into a vector (always displays zero).
- Total IPC time and the DisplayList IPC graph measure the time between api.set_display_list and the render backend picking the message up, plus the time it took to build the display list (but doesn't take into account the time it took for actual IPC in between).
- Send time is only the time between api.set_display_list and the render backend picking the message up but doesn't take into account the time it took between the content thread sending the DL and the compositor thread forwarding it.
After this patch:
- Content send time measures the time between the content thread sending the display list and the compositor forwarding it (actual IPC).
- Api send time measures the time between the compostor thread forwarding the DL and the render backend picking it up.
- Consume time is removed.
- Total send time is the sum of content and api times.
- Display list build times and display list IPC (total send time) are on separate graphs.
Depends on D69227
Differential Revision: https://phabricator.services.mozilla.com/D69228
--HG--
extra : moz-landing-system : lando
Depends on D69003
This backward compatibility message was only relevant for Firefox 67.
We can remove it.
Differential Revision: https://phabricator.services.mozilla.com/D69007
--HG--
extra : moz-landing-system : lando
Clearly WPT doesn't have enough preserve3d tests :(
This was being used by the overflow computation, which computed a too-tight
overflow, and thus clipped too much. Test fails without the patch as expected.
Differential Revision: https://phabricator.services.mozilla.com/D69356
--HG--
extra : moz-landing-system : lando
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