Automatic update from web-platform-tests
Split skip-not-fully-active.html into two tests
We'd like to prioritize loading and compositing tasks till FCP and this
appears to expose a problem with the test. The timing of the script on
line 6 with respect to the second promise test is a bit fragile.
If the iframe script runs before the promise then
document.querySelector('iframe') returns null and the test fails.
This timing issue seems unrelated to the test itself, so I propose
splitting the test into two as the simplest fix.
Bug: 971191
Change-Id: I65384093ac8f4616d64fc21ee692d145be1655a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807323
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#697512}
--
wpt-commits: f5a6e66efc40e166af62cb7d44786344f0735b93
wpt-pr: 19120
Automatic update from web-platform-tests
Maintain update-intermittent for tests with conditions during a full update
When `update_intermittent` is True and `remove_intermittent` is False,
ensure `full_update` does not remove any existing intermittent statuses
from tests with conditions.
Differential Revision: https://phabricator.services.mozilla.com/D39614
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1568497
gecko-commit: c267aa48b4dfebc648170f866168f4b699607a4a
gecko-integration-branch: autoland
gecko-reviewers: jgraham
--
Fixup lint errors
--
Fix use of intern in py3
--
Disable tests on py3
--
wpt-commits: 3b94f8748f9f03d9a4c63c2a8067f7f52535306f, 01ce984988b5decb335ac4c820e6d482777901d6, 77de8589cdd2f4cfaeeb54db9a40be118249b40e, 4534f63392ecac1a5593e7a5433568a4849d8ddf
wpt-pr: 18505
Automatic update from web-platform-tests
[sensor] Upstream sensor layout tests to wpt
Rewrote /external/wpt/resources/chromium/generic_sensor_mocks.js to align with
/http/tests/resources/sensor-helpers.js, but excluded those functions specific
for device orientation.
Merged tests from /sensor/resources/generic-sensor-tests.js to
/external/wpt/generic-sensor/generic-sensor-tests.js
Moved common utils into /external/wpt/generic-sensor/resources/generic-sensor-helpers.js
Merged tests from /sensor/*.html to corresponding test folders under /external/wpt/,
e.g. sensor/orientation-sensor.html -> external/wpt/orientation-sensor/OrientationSensor.https.html
Updated all sensor tests under external/wpt/ to adapt to sensor mojom mocks
Deleted folder web_tests/sensor/
Bug: 816462
Change-Id: I614ce82b7c90530b7a268d8f6a0f72cc96ea3d6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770158
Commit-Queue: Wanming Lin <wanming.lin@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#695905}
--
wpt-commits: db7bad01d261a21cb99405abb57f9dd7a421e147
wpt-pr: 18886
Automatic update from web-platform-tests
[LayoutNG] Correct overflow inside anonymous blocks inside %-insets.
NGPhysicalLineBoxFragment::ScrollableOverflow() compared the computed
style passed as container_style to the computed style of each child,
and it would calculate the child's relative offset only if they
differed. All element nodes have their own computed style, so this only
mattered for text nodes. However, if the container was an anonymous
block, they'd always differ, since the computed style of a text node
is the same as that of the parent DOM node. This is an implementation
detail; we save some memory by letting text nodes share computed style
objects with their containing DOM node. But that also means that extra
care is required when working with ComputedStyle objects associated
with text nodes: basically, treat all non-inherited-by-default
properties (such as 'position', 'top' and 'left') as if they were set
to their initial value.
Bug: 1002485
Change-Id: If77d79e45c2aa55ac30dc239c738e2a40f8326f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1807813
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#697324}
--
wpt-commits: 3472889e27404a9b3c893845156848a0c5fbda9b
wpt-pr: 19115
Automatic update from web-platform-tests
Port perspective and perspective-origin interpolation tests to wpt
The overflow regression tests was not moved because of this example:
https://chromium-review.googlesource.com/c/chromium/src/+/1804695
Firefox falls partially for some cases in perspective
interpolation, where the expectation is 'none' and Firefox produces
0px. The spec says the value must be either 'none' or positive values.
Bug: 900581
Change-Id: I8562cd51476178919ecf9a393f0d169eb7244461
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1808585
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#697323}
--
wpt-commits: c37a1605d2a5c4faf61b92e5735a7b0a29795c33
wpt-pr: 19107
Now that LCovRealm is allocated on demand, use a Vector directly instead
of allocating that vector on demand. To ensure pointer stability of
LCovSources, allocated them in the LifoAlloc and only store pointers in
the sources vector. They are still fully owned by the LCovRealm.
Differential Revision: https://phabricator.services.mozilla.com/D46170
--HG--
extra : moz-landing-system : lando
Save a little bit of memory when code coverage is not in use. Add a
collectCodeCoverage method to the realm so it can allocate LCovRealm on
demand. Also compute the realm name string from the constructor instead
of in the lookup code (this still happens at same time).
Depends on D46168
Differential Revision: https://phabricator.services.mozilla.com/D46169
--HG--
extra : moz-landing-system : lando
Avoid creating the ScriptNameMap in the off-thread parse zone. Instead
perform JSScript::initScriptName when merging the parse result to main
thread. This will avoid the need to migrate coverage initialization data
between Realms.
Differential Revision: https://phabricator.services.mozilla.com/D46168
--HG--
extra : moz-landing-system : lando
Note that to avoid introducing errors, I elected against renaming everything in
the code; internally to Firefox the code still refers to "UntrustedModules";
only the relevant fields have been renamed to reference the new ping schema.
A PR for backend schema changes is in the works.
Differential Revision: https://phabricator.services.mozilla.com/D43162
--HG--
rename : toolkit/components/telemetry/docs/data/untrusted-modules-ping.rst => toolkit/components/telemetry/docs/data/third-party-modules-ping.rst
rename : toolkit/components/telemetry/tests/unit/test_UntrustedModulesPing.js => toolkit/components/telemetry/tests/unit/test_ThirdPartyModulesPing.js
extra : moz-landing-system : lando
as documented in
https://web-platform-tests.org/writing-tests/testharness-api.html#setup
On errors without setup(), the harness would assume a single page test and
report as FAIL in an imaginary subtest name based on document.title.
Wrapping in setup() leads to failures reporting as a toplevel ERROR, which
perhaps better reports the nature of the failure.
This change happens to workaround an issue where the different subtest name
would confuse cleanup of stale data. The expectation data added here replaces
what was accidentally removed in
https://hg.mozilla.org/mozilla-central/rev/5be2e6400a48#l33.1
Differential Revision: https://phabricator.services.mozilla.com/D46685
--HG--
extra : moz-landing-system : lando
The previous approach of using space characters would sometimes end up causing spaces to get saved in storage and cause data loss.
Differential Revision: https://phabricator.services.mozilla.com/D46663
--HG--
extra : moz-landing-system : lando
We don't need this anymore now that we're always
using the visible rect.
This requires bug 1582528 to properly set the visible area.
Differential Revision: https://phabricator.services.mozilla.com/D46628
--HG--
extra : moz-landing-system : lando
