This one was VarCached to two different variables in two different modules.
Differential Revision: https://phabricator.services.mozilla.com/D41920
--HG--
extra : moz-landing-system : lando
ComputedStyle* aComputedStyle doesn't provide any extra value over just aStyle.
Lots of these should be const and what not, oh well.
Differential Revision: https://phabricator.services.mozilla.com/D41933
--HG--
extra : moz-landing-system : lando
(This basically addresses the review comments that I missed in
bug 1105868 part 4. My bad.)
Differential Revision: https://phabricator.services.mozilla.com/D42134
--HG--
extra : moz-landing-system : lando
Some worker debugger runnables (the ones that want to evaluate script against a
debugger sandbox) depend on the JSContext being in a particular Realm before
they run, but don't really store which Realm that should be. Instead of
propagating that state via the current Realm of the JSContext across nested
event loops, we want to propagate it explicitly.
Differential Revision: https://phabricator.services.mozilla.com/D41790
--HG--
extra : moz-landing-system : lando
WasmInstance::funcRef has 'FailureMode::FailOnInvalidRef' so it looks like we
just need to report the OOM and return InvalidRef.
Differential Revision: https://phabricator.services.mozilla.com/D42050
--HG--
extra : moz-landing-system : lando
Intent email: https://groups.google.com/d/msg/mozilla.dev.platform/1NP6oJzK6zg/ftAz_TajAAAJ
For now do the obvious check rather than bigger refactorings, since we keep them
matching :link or not depending on whether they have an href.
I'll file an HTML spec issue about not making them traversable, and a MathML
issue about the craziness that it is that almost all MathML elements can be
links.
Differential Revision: https://phabricator.services.mozilla.com/D41269
--HG--
extra : moz-landing-system : lando
This part removes the use_toolchains transform, and adjusts all task
definitions accordingly.
Differential Revision: https://phabricator.services.mozilla.com/D41891
MANUAL PUSH: avoid closing autoland while docker images and toolchains
are rebuilt.
The remaining uses all need adjustements to in-tree mozconfigs, so they
all need to be done at once.
However, to make things slightly more intelligible, we do this in two
steps. This is step 1: we modify the use_toolchain transform to take care of
the transformation, while keeping the task definitions intact, so that
we only deal with mozconfig and build script adjustements here.
Differential Revision: https://phabricator.services.mozilla.com/D41890
Automatic update from web-platform-tests
Move computed transition-timing-function test (#18412)
The test for transition-timing-function computed
value should be under CSS Transitions, not
CSS Animations.
--
wpt-commits: 3db7e8efd19657f6b30fdb7ad7bf7d0f651214fc
wpt-pr: 18412
--HG--
rename : testing/web-platform/tests/css/css-animations/parsing/transition-timing-function-computed.html => testing/web-platform/tests/css/css-transitions/parsing/transition-timing-function-computed.html
Automatic update from web-platform-tests
[docs] Reorganize content on test organization
Consolidate content in the README and the comprehensive project
documentation.
--
[docs] Extend list of shared resource directories
--
[docs] Add hyperlinks
--
wpt-commits: 78fe39d8a9f88abbf26ff571fa6ce49ae0c56c25, 9d37ca75bc4b5fca60d267d422ccfa02bd3b93f4, d358ae4d7bd3f703d3adf09d5d6baa04f3367cce
wpt-pr: 18358
Automatic update from web-platform-tests
Remove reference to Reviewable in the test review policy
--
Don't recommend strongly.
--
wpt-commits: ca4839a06320f3452951a7579f16743cc561598b, 27caa8b336e166c8a4017cb4b619803725b1200d
wpt-pr: 18355
Automatic update from web-platform-tests
[css-logical] WPTs for inset parsing
inset is one to four values, each auto or a length-percentage.
https://drafts.csswg.org/css-logical/#propdef-inset
Change-Id: I3f1599e200fec16a709cc6404246a28c404805b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1747488
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686337}
--
wpt-commits: 3b5944691d24e19a3937671885abb749334e8d45
wpt-pr: 18376
Automatic update from web-platform-tests
[ElementTiming] Fix background image loadTime
This change adds a map |background_image_timestamps_| of load timestamps of
background images tracked by StyleFetchedImage, which are the background images
with url. The map only tracks the load time, as |images_notified_| must still be
used to track the background image paints. Otherwise we'd only report an entry
per background image even when applied to multiple elements.
This change also makes computations a bit more efficient by only calling
base::TimeTicks::Now() on the first time we load an entry. It also fixes a
problem of calling Set() in between usages of an iterator, which is not allowed.
Before this change, the added test would crash due to this problem.
Bug: 879270, 986891
Change-Id: I86640f5587f69f94e13c429f3e55b3d5d6978cc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745497
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686176}
--
wpt-commits: 1d8fa760f9999ef13baa4c267bf042b7b4122789
wpt-pr: 18345
Automatic update from web-platform-tests
Recreate XRInputSource when profiles change.
Based on discussion at https://github.com/immersive-web/webxr/issues/783 ,
we are confident this will become a requirement in the WebXR spec.
Also update the OpenVR render loop to re-send the input source description
when the profiles array is updated.
Bug: 989244
Change-Id: I77bb2b15d894fe41c532235b062163bdc87a4ea2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1744663
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686103}
--
wpt-commits: f6819af5e6f4fa46c3c325faf2cfb060b2ac7914
wpt-pr: 18338
Automatic update from web-platform-tests
Port WebSocket 3p-cookie-blocking web tests to wpt_internal
(For context, see https://crrev.com/c/1691522.)
The new requirement that SameSite=None cookies must be Secure made it
impossible to properly test third party cookies on WebSocket because
the web_test runner does not have a wss server. This CL ports those
tests, formerly in web_tests/http/tests/security/cookies/websocket/,
to web_tests/wpt_internal/websocket-cookies/.
Bug: none
Change-Id: Ifc6d2d78a84aa6c93e297dc71b3595108a18f179
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713670
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#686071}
--
wpt-commits: 990925e0c2bd9100806e7fee202911444a71a7c7
wpt-pr: 17989
Nicholas Nethercote
Markus Stange
Mike Hommey
Emilio Cobos Álvarez
Mats Palmgren
Boris Zbarsky
Ryan Hunt
Micah Tigley
Edgar Chen
moz-wptsync-bot
Eric Willigers
Simon Pieters
Mike Pennisi
autofoolip
Ms2ger
Eric Willigers
Nicolás Peña Moreno
Jacob DeWitt
Lily Chen