Automatic update from web-platform-testsAdd report-only mode to Feature Policy
This change adds a "report-only" policy to each security context, which
is local to that context (not replicated across processes) and is used
to determine whether a report should be sent even if a feature is
enabled, when the feature is used.
Reports are now augmented with a "disposition" field, which is either
"enforce", if the feature usage was actually blocked, or "report", if
it was not.
Feature policy directives are placed in the report-only policy if the
feature name is suffixed with "-report-only", otherwise, they affect
the regular (enforcing) policy.
Explainer at
https://github.com/WICG/feature-policy/blob/master/reporting.md
Existing tests are updated, and new tests for report-only mode are
added to ensure that reports are sent even when the feature is used
successfully.
Bug: 904878
Change-Id: I27bc42729c5ab5560160f3d993431e606a8a3a47
Reviewed-on: https://chromium-review.googlesource.com/c/1178811
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608004}
--
wpt-commits: b39f5e0d0e0872cdd9b7592f0b9ff0b5c11bcef3
wpt-pr: 13984
Automatic update from web-platform-tests[LongTasks] Change TaskAttributionTiming name to 'unknown'
At TPAC, we agreed that 'script' is confusing because it implies that
longtasks only measure script work. Thus, we decided to change the name
to 'unknown'. Also see https://github.com/w3c/longtasks/issues/47.
Change-Id: I5a0666d0fa078bfeac8ab6e8397b9b51aca3e833
Reviewed-on: https://chromium-review.googlesource.com/c/1336367
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608479}
--
wpt-commits: 4309ceb7b165a42534514ca9933846cc0912bdae
wpt-pr: 14063
Automatic update from web-platform-testsImprove robustness of wpt animation interpolation tests.
This patch fixes the problem where subtle changes to numerical values in matrix interpolation cause mismatches in the expected results.
To address the issue:
* Styles are checked to see if they are of the form matrix(...) or matrix3d(...).
* If the style is a matrix, then arguments are rounded and the style is reconstructed.
Bug: 797472
Change-Id: I44d6e0ed13e24dc2ecfeeacbcd4809d6dcdb6465
Reviewed-on: https://chromium-review.googlesource.com/c/1337640
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608466}
--
wpt-commits: 794b7ee9292f09802cd41e41a04be420b1d7bec3
wpt-pr: 14080
Automatic update from web-platform-tests[css-flex] align-content should apply even when there's just a single line
In Jan 2015 the spec changed in
https://drafts.csswg.org/css-flexbox/#change-201409-align-content-wrapping
Change our code accordingly. This effectively reverts commit
crrev.com/290823003 and relands crrev.com/2191683003
align-content-wrap-004 is a test for bug 641789, which was a regression
from the previous attempt at landing this patch.
Bug: 599828
Change-Id: I8de127c19203854922eb23a626cee4de9a772f22
Reviewed-on: https://chromium-review.googlesource.com/c/1323906
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608449}
--
wpt-commits: 34ecd56f063821c113fd20bcb05b80aafd82d787
wpt-pr: 14062
Automatic update from web-platform-testsFloats in a next fragmentainer may push lines down.
We cannot assume that when we push a line to the next fragmentainer
(because it doesn't fit in the current one), the line is going to fit
there. If the next fragmentainer has a float that nothing fits beside
and the float is too tall to fit the line below it, we need to jump to
yet another fragmentainer in order to find room for the line.
Bug: 902762
Change-Id: Ied14694ed1ad4fc25d28527edd1ca7389f00664c
Reviewed-on: https://chromium-review.googlesource.com/c/1335580
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608414}
--
wpt-commits: a218e2f1678badf75722fd444524d98cd5996b3f
wpt-pr: 14058
Automatic update from web-platform-tests[css-properties-values-api] Validate var() fallbacks.
According to a recent spec edit, any fallback in a var()-reference must
match the syntax of the referenced property, otherwise the var()-reference
is invalid. This applies even if the fallback is not used.
To implement this, ResolveFallback now returns kNone/kFail/kSuccess instead
of a bool. This is necessary, because the kNone case may be both an error
state and a success state, depending on whether the fallback is being
used or not, hence a plain bool is not sufficient.
R=futhark@chromium.org
Bug: 641877
Change-Id: I951eef6335bf1cd4064d59959d73ec4fa39c9ee0
Reviewed-on: https://chromium-review.googlesource.com/c/1335576
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608365}
--
wpt-commits: 4bf9cbfa246859a47e46507154760526e48f8af0
wpt-pr: 14055
Automatic update from web-platform-testsRevert "Update infrastructure/metadata/ to match Chrome and Firefox results"
This reverts commit c2bf7c6ed9e3ab9d42000b712d3793f6b58c33cd.
--
Revert "Add action_sequence in testdriver"
This reverts commit 3287351b606c4588e397632e2ab04641dc91094d.
--
wpt-commits: 9e10da29c88d1268b65bac176df3c6ab2ee6a3d5, 02dccc6b5ad45352ae5c3bdf23fcbd9b0deea071
wpt-pr: 14076
Automatic update from web-platform-testsRemove timeout in async_test for IndexedDB tests
Remove all the timeout parameters in async_test for IndexedDB tests.
Affected tests: 44, Pass: 44, Failed: 0
Related: #11120
--
wpt-commits: c7c8c373d49baba4721e7800525b1699bf67ac7e
wpt-pr: 14068
Automatic update from web-platform-tests[testharness.js] Honor test config in workers (#14061)
Ensure that uncaught exceptions originating from workers do not
influence harness status when the `allow_uncaught_exception` setting has
been enabled.
--
wpt-commits: 0ddb31913184805fa3725e22e5b88046e961996b
wpt-pr: 14061
Automatic update from web-platform-testsReplace direct use of offerToReceiveAudio by generateAudioReceiveOnlyOffer.
This allows to use non legacy APIs by default if supported.
--
Merge pull request #14040 from youennf/remove-offerToReceiveAudio-use-outside-legacy
Replace direct use of offerToReceiveAudio by generateAudioReceiveOnlyOffer
--
wpt-commits: 27e0acb4312abf064d6491ff29db3852a958dff8, 42abd6cc7ebd7c0b0513639e1a8c1bd958638fed
wpt-pr: 14040
Automatic update from web-platform-testsFix wpt: service-worker/navigation-redirect.https.html
As preparation for adding FetchEvent#resultingClientId, this CL fixes
the test to make it pass once resultingClientId is impelmeneted.
Bug: 778497
Change-Id: I6309a13d4315e6a99149275a6d7889f14ce0d757
Reviewed-on: https://chromium-review.googlesource.com/c/1335055
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608167}
--
wpt-commits: 6856483bcc86322198f10e0c42385a7f9127eb66
wpt-pr: 14050
Automatic update from web-platform-tests[css-grid] Consider scrollbars in PopulateGridPositionsForDirection()
We never care about scrollbars
in LayoutGrid::PopulateGridPositionsForDirection(),
that's fine if the scrollbars are at the end
(e.g. on the right in horizontal writing mode and LTR direction)
but it causes problems when they're at the beginning
(e.g. on the left in horizontal writing mode and RTL direction).
The patch modifies the method so it takes into account scrollbar size
in order to compute the position of the columns/rows
depending on the direction and the writing mode.
BUG=904438
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-lr-001.html
TEST=external/wpt/css/css-grid/grid-model/grid-container-scrollbar-vertical-rl-001.html
Change-Id: I9c8307638647e449f6975cacf99f89e29d4fa655
Reviewed-on: https://chromium-review.googlesource.com/c/1334370
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#608154}
--
wpt-commits: ca8728e002fdfcdde1ee2efd39ebaccc823bf9b2
wpt-pr: 14052
Automatic update from web-platform-testsWorklet: Modernize service worker interception tests for worklets using async/await
This is just a cleanup CL, and there're no functional changes.
Bug: n/a
Change-Id: I60820045469eed4a0903b37af9e4f8927bcc884d
Reviewed-on: https://chromium-review.googlesource.com/c/1335047
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607892}
--
wpt-commits: d16eb1ce23500e7234f58df86a59d5c00d222118
wpt-pr: 14045
Automatic update from web-platform-tests[wptserve] Eliminate race condition (#14024)
This race condition was expressed during testing sessions where the
first test to use the Stash feature issued did so with multiple requests
made in parallel.
--
wpt-commits: cbb25e2c99696956ed2a36e7bcdbdee1dca71705
wpt-pr: 14024
Leaving the Fennec process running after a swipe-to-kill puts Fennec in an unrecoverable state; this ensures we kill the process anytime a user swipes-to-kill Fennec and therefore lets us recover as usual.
Move JSON dump loading and CanonicalJSON serialization to a worker to reduce impact on main thread
Differential Revision: https://phabricator.services.mozilla.com/D10064
--HG--
extra : moz-landing-system : lando
Rust signatures aren't properly demangled, and contain some trailing
data that seems to depend on the compiler version. This defeats the
attempt to allow LSAN errors when importing tests, and we end up
adding multiple variants of the same symbol to the allow list.
To avoid this, simply preprocess the symbols not to contain the
trailing junk when reading LSAN output, whilst we await better
demangling.
Differential Revision: https://phabricator.services.mozilla.com/D12303
Bug 1483553 was fixed by the developers of medium.com so that we can remove
medium.com from the blacklist which prevents strict keypress dispatching on
specific websites.
Differential Revision: https://phabricator.services.mozilla.com/D12398
--HG--
extra : moz-landing-system : lando
When calling nsGlobalWindowOuter::SetOpenerWindow with null we should
make sure to also clear BrowsingContext::mOpener.
Differential Revision: https://phabricator.services.mozilla.com/D11769
--HG--
extra : moz-landing-system : lando
