This removes tracing for the values of the registration map and the active record set and sweeps them instead. This requires maintaining a map of FinalizationRegistryObjects on the zone.
Differential Revision: https://phabricator.services.mozilla.com/D67677
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Fix failing touch-event tests.
The idl tests were failing because the definition order was wrong.
Change-Id: Iac210d6c0b211c49a78749c8dfd2a94be76c9a45
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2110078
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751779}
--
wpt-commits: d154c9ec965214293d679640834e70ec2fd915dc
wpt-pr: 22337
Automatic update from web-platform-tests
Split external/wpt/largest-contentful-paint/invisible-images-composited.html
We still have cases that fail in pre-CompositeAfterPaint. Split the test
into 2 to ensure test coverage of the passing cases.
Bug: 957674
Change-Id: I951c28eb3f4d44f122c3d0314d24b454a2e56bc8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109144
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751734}
--
wpt-commits: c936cd7cea5642439e2471240a45a38beb426d4e
wpt-pr: 22326
Automatic update from web-platform-tests
Add tests for PointerCapture at Shadow DOM elements
PointerCapture should work for Shadow DOM elements based on Pointer Events specification. Add web platform tests to ensure PointerCapture works with shadow DOM elements.
Bug: 810882
Change-Id: I5f183afaab17689551f78903acba3e74f8cd49f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2096112
Commit-Queue: Liviu Tinta <liviutinta@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751687}
--
wpt-commits: 93411c99880dcb2905ae2e6fb995fef023bc9fcc
wpt-pr: 22158
Automatic update from web-platform-tests
[css-variables] Custom props with invalid var() should behave as 'unset'
We currently have a (WPT-enforced) bug where custom properties that
reference guaranteed-invalid values [1] behave themselves as guaranteed-
invalid. This is not correct per spec, which requires the custom
property to behave as 'unset' in this case. This was clarified in [2],
although the spec has described this behavior long before that.
Unfortunately Firefox has the same issue. Safari on the other hand, does
implement it correctly.
[1] https://drafts.csswg.org/css-variables/#guaranteed-invalid
[2] https://github.com/w3c/csswg-drafts/issues/4075
Bug: 980930
Change-Id: I84a0da3aad6b72b574009d560eb868632769098a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108026
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751636}
--
wpt-commits: fc793094912b67b45a94d101819bffb9b9307710
wpt-pr: 22318
Automatic update from web-platform-tests
[WPT/common/security-features] Sort subtests to reduce diffs
When `spec.src.json` is modified, the order of subtests were
changed and thus unncessesary diffs were generated, even if
the subtest contents are not modified.
This CL sorts subtests to avoid such diffs.
Generated files will be modified in
https://chromium-review.googlesource.com/c/chromium/src/+/2109511
Bug: 906850
Change-Id: Ic17d8122b0b5139e89ec2b4423511b933941ad65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2109570
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Eriko Kurimoto <elkurin@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751602}
--
wpt-commits: 6a665f63ae39b552f60b971f11c34b215861fcb3
wpt-pr: 22328
Automatic update from web-platform-tests
[wakelock] Fix all Web Platform Tests
This change fixes all of the wake lock tests in WPT by making two major
changes.
1) Grant wake lock permission at the beginning of the test using the new
set_permission method on test_runner.
2) Hook up the Mojo interface binder for the wake lock service in
dedicated worker contexts.
Bug: 257511
Change-Id: I136a2f90bc0c595a35ba707b5ab5200b4c42281a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2089966
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751473}
--
wpt-commits: 167c85fa084db1759d05bd6f3155728df516895c
wpt-pr: 22108
Automatic update from web-platform-tests
Remove WPTs for user activation transfer.
We are no longer pursuing the activation transfer idea.
Bug: 928838, 951453
Change-Id: I81844e1fdda740414c7252ef50619fcf1ab15450
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106966
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751460}
--
wpt-commits: 691307ff30ed1653b64508ac3736db3ffb13da72
wpt-pr: 22301
Automatic update from web-platform-tests
Add tests for true computed value of transform interpolations
Create a set of interpation tests for transforms which read the true
computed value (as opposed to the resolved value returned by
getComputedStyle() which differs drastically in the case of transforms,
see https://drafts.csswg.org/css-transforms/#transform-property).
As there is currently no universal way to get this value,
each test comes in 3 versions:
Two variants using computedStyleMap().get().toString() which is
supported by chrome. These also have duplicate versions where the zoom
property is set as it currently triggers some transform serialization
bugs in blink.
A version using commitStyles, which in implemented in both firefox and
chrome, but currently gives resolved values instead of computed ones
in chrome.
These assume that "computed value serialization", when referring to
a box-size dependent procedure, is used ion its historical context as
a deprecated term for what is now "resolved value" (as returned by
getComputedStyle()), and the serialization of the true computed value
follows the property infobox. This interperetation is currently used
by both Firefox and Chromium.
A spec issue to update the language around resolved value is at
https://github.com/w3c/csswg-drafts/issues/4869
Change-Id: I59afcc9f73906051212cc71570631509920ddc32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2103520
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751418}
--
wpt-commits: 201154711dd0e06c817880c7c9396a0d7188a8f5
wpt-pr: 22252
Automatic update from web-platform-tests
Implement main thread scroll offset snapshotting
Per https://wicg.github.io/scroll-animations/#avoiding-cycles, snapshot
scroll timeline state once per frame. Changes made:
- Snapshotting is done by saving scroll timeline current time and
phase.
- Snapshot scroll timeline state as part of the ScrollTimeline
constructor.
- Every time ScrollTimeline needs to query current time or phase, use
the snapshot.
- Any scroller layout change calls scroll timeline invalidation.
- When scroll timeline is invalidated outside of the document lifecycle
update, its state is re-snapshotted and attached animations are
marked as outdated. This is required to ensure correctness of user
scripts that query animation properties after scroller updates, like
the following:
scroller.scrollTop = 100;
console.log(anim.effect.getComputedTiming().localTime);
console.log(timeline.currentTime);
- If scroll timeline is invalidated during lifecycle update the same
procedure of snapshotting and marking the animations as outdated runs
right after the lifecycle update.
Bug: 944449
Change-Id: Id4330a15501b3a1312803d06e4ab9e3130ee3ee1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005629
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751412}
--
wpt-commits: 5c771eea33d162b4d4a828b8c408fc12c687b5b3
wpt-pr: 21615
Automatic update from web-platform-tests
[mathml] Test width and display=block on <math> (#22323)
--
wpt-commits: c903e42d305bea2c615fe11b4281af507706ce32
wpt-pr: 22323
Automatic update from web-platform-tests
Misc fixes to WPTs for user activation api.
This CL fixes/refactors existing tests to prepare for new WPTs for UAv2.
- Fix a test name suffix.
- Fix github issue number.
- Make postMessage format consistent.
- Clarify a child-frame name.
- Replace parent refs to "top" to allow deep iframes.
Change-Id: I9da97ee827d6556116eab9d592e44665dc71d4c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106538
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751348}
--
wpt-commits: bb4253d456fe0ad0ebe2200852a4d5c01dc71c0f
wpt-pr: 22319
Automatic update from web-platform-tests
Add WPT tests for paint-timing, when FCP only is available, covering … (#22262)
* Add WPT tests for paint-timing, when FCP only is available, covering different cases of 'contentful'
* Whitelist whitespace test
* More tests for complex-ish cases
* Fix test titles
* Simplify whitespace test
* Add more test-cases
* Make SVG contentful only when has paintable/contenful elements
* Fix based on review comments
* Update paint-timing/fcp-only/fcp-bg-image-two-steps.html
Co-Authored-By: npm1 <npm@chromium.org>
* Refactor and use assert{No}FirstContentfulPaint
* Refactor assert{No}Fcp to use getEntries instead of observer
* Readble error for FCP assertions
* Remove redundant rAF wait
Co-authored-by: Noam Rosenthal <noam@webkit.org>
Co-authored-by: npm1 <npm@chromium.org>
--
wpt-commits: c951468bfbac87c537eb605449691f4d465c756f
wpt-pr: 22262
Automatic update from web-platform-tests
Fix up incorrect size of <svg:image> with a SVG image without intrinsic size
This patch fixes up incorrect sizing of SVG Image with referred SVG
image without the intrinsic size.
So when referred image is SVG, it currently checks that referred image
has aspect-ratio.
If referred svg image doesn't have the aspect-ratio, set the concrete
object size from the 'default object size'.
Bug: 1045932
Change-Id: If979b3a9a7980bde9e2bee38ba2863cf223b4f0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094055
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Hyunjune Kim <hyunjune.kim@samsung.com>
Cr-Commit-Position: refs/heads/master@{#751325}
--
wpt-commits: 2b65c3f2f6bcb1cb0ec0191569d5317ad160399f
wpt-pr: 22258
Automatic update from web-platform-tests
Add timeouts for EventWatchers on CSS animation tests (#22282)
Previously the test harness could timeout while waiting on the event
watcher. In this patch, a timeout was added to the watchers in cases
where the events should fire on the next animation frame. With the
change, we still see timeouts on individual tests, but no longer see
the test harness timing out.
Next steps:
1. Add animationcancel. For some reason, this event got overlooked
previously and was never implemented. Adding this event resolves
the majority of timeouts (confirmed in an experimental patch).
2. Reconnect and event delegate after calls to animation.effect.
Currently, the lack of a delegate on the new effect halts the
dispatching of subsequent animation events.
Bug: 1059968
Change-Id: Ib5bf46762e316a5f3d5f33aa95bf74edaf42e773
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2105424
Reviewed-by: Yi Gu <yigu@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#750745}
Co-authored-by: Kevin Ellis <kevers@chromium.org>
--
wpt-commits: c1c943f3d9e3fe023e401a39db1a66e535a50561
wpt-pr: 22282
Automatic update from web-platform-tests
UpgradeInsecureRequest: Add subresource fetch from data: URL workers test (#22235)
This CL adds WPTs to test subresource fetch from data: URL dedicated and
shared workers with upgrade-insecure-request CSP.
The manual change is only in upgrade-insecure-requests/spec.src.json.
Others are automatically generated by generate.py.
Bug: 989399
Change-Id: Iefb7764be8ce68b5aefb1ac83f253302050fe55e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2102088
Commit-Queue: Eriko Kurimoto <elkurin@google.com>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751234}
Co-authored-by: Eriko Kurimoto <elkurin@google.com>
--
wpt-commits: bd040f26988de274b572e49a1139b138c448d899
wpt-pr: 22235
So that accesses that use mSkipRect.XMost() - 4 or - 16 are aligned to a 4-byte
boundary. Not doing so would crash on some architectures due to a SIGBUS.
Differential Revision: https://phabricator.services.mozilla.com/D66748
--HG--
extra : moz-landing-system : lando
Sylvestre Ledru
Jeff Walden
Jon Coppeard
Andreea Pavel
Eitan Isaacson
Nils Ohlmeier [:drno]
Zibi Braniecki
Mihai Alexandru Michis
Matthew Gaudet
emcminn
moz-wptsync-bot
Dave Tapuska
Xianzhu Wang
Brian Kardell
Liviu Tinta
Blink WPT Bot
Andreu Botella
Anders Hartvoll Ruud
Hiroshige Hayashizaki
Reilly Grant
Mustaq Ahmed
autofoolip
George Steel
Olga Gerchikov
Rob Buis
Noam Rosenthal
Hyunjune
Yoav Weiss
Emilio Cobos Álvarez
Michael Kaply
Tomislav Jovanovic