While I'm here, I sorted the manifest, in order to match the sorted PGO list, so that it's easier to see when there's a discrepancy.
Differential Revision: https://phabricator.services.mozilla.com/D58968
--HG--
extra : moz-landing-system : lando
Stop dumping device 'ps' output to the test log since the information is available elsewhere
(android-performance.log) and since this call is associated with intermittent hangs.
I do not have a good explanation for the hangs: The same shell_output('ps') call is used
for android-performance.log, without any known failures. Something about dumping many lines
of output in one info() call?
Differential Revision: https://phabricator.services.mozilla.com/D58168
--HG--
extra : moz-landing-system : lando
when a tarball is broken and in the cache, the condprof client will loop on
trying to extract its content and eventually fail. On any tar extraction error,
we delete the file from the cache to get a fresh on
Differential Revision: https://phabricator.services.mozilla.com/D58917
--HG--
extra : moz-landing-system : lando
Most Android mozharness scripts define self.xre_path, but some, like android_wrench.py may not
(wrench has no other need for host-utils); now we explicitly allow for that.
Differential Revision: https://phabricator.services.mozilla.com/D58560
--HG--
extra : moz-landing-system : lando
AVD names were updated in bug 1599534, but this case - auto-selecting an avd for an arm
build - was missed.
Differential Revision: https://phabricator.services.mozilla.com/D58694
--HG--
extra : moz-landing-system : lando
There are multiple places where bogus non-empty transition rules can be created
before this patch when EffectSet's cascade information isn't up-to-date. That
can happen as described in bug 1606176.
Anyhow, in this particular call site, this is only used to filter from
transition rules effects that are from running animations, to implement:
https://drafts.csswg.org/css-transitions/#application:
> Implementations must add this value to the cascade if and only if that
> property is not currently undergoing a CSS Animation ([CSS3-ANIMATIONS])
> on the same element.
In the test-case, the EffectSet cascade info is empty, so we hit the "skip
everything" for animations (wrong), and "skip nothing for transitions" (also
wrong). This creates a transition rule node which then we never remove
(understandably, as the element never had a transition!).
This fixes the observables of this test-case, by checking the cascade level
(so that we don't create transition rule nodes with declarations coming from
animations). This is strictly more correct than what we were doing.
If we hit the proposed assertion after this change, this code may still create
transition rules that incorrectly override animations, but will never mint one
out of the blue which we'd then fail to remove (which is the problem the
test-case is hitting).
Differential Revision: https://phabricator.services.mozilla.com/D58333
--HG--
extra : moz-landing-system : lando
This commit does two things:
- It exposes the error that caused the test to fail in our logs, so it would
appear like so:
```
TEST-UNEXPECTED-FAIL | org.mozilla.geckoview.test.ExtensionActionTest.setIconSvg[#pageAction] | java.lang.AssertionError: We shouldn't get here
```
- It catches exceptions that are raised before any test code is run and outputs
a different message (since those failures do not depend on the test at all),
like so:
```
ERROR runjunit.py | The previous test failed because of an error in the test harness | org.mozilla.geckoview.test.rule.TestHarnessException: java.lang.RuntimeException: We shouldn't get here
```
This will hopefully help with spurious intermittents and understand when a
failure changes.
Differential Revision: https://phabricator.services.mozilla.com/D58022
--HG--
extra : moz-landing-system : lando
Some adb logs produce badly encoded characters, producing errors.
Since the log is just informative, and getting pulled after the work
is done, we can ignore these errors and just warn that the adb logs
could not be retrieved.
Differential Revision: https://phabricator.services.mozilla.com/D58801
--HG--
extra : moz-landing-system : lando
If the condprof client retries getting a condprof, it will
display the traceback of the failure. If the task succeeds eventually,
this failure will pollute the logs and confuse Treeherder if there's
another problem later on in the job.
Differential Revision: https://phabricator.services.mozilla.com/D58802
--HG--
extra : moz-landing-system : lando
This is a backport of improvements made while working on Bug 1597336 we can
apply right away on condprof to speed up test execution and get more logs when
something goes wrong
Differential Revision: https://phabricator.services.mozilla.com/D58748
--HG--
extra : moz-landing-system : lando
Changes:
Handle the import of `urllib`/`urllib2` modules properly.
Make the exception handling python2/3 compatible.
Fix print statements.
Differential Revision: https://phabricator.services.mozilla.com/D58479
--HG--
extra : moz-landing-system : lando
Changes:
Fix syntax issues preventing gittools.py from being python3 compatible.
Differential Revision: https://phabricator.services.mozilla.com/D58475
--HG--
extra : moz-landing-system : lando
Given that `test_composition` which requires the pref is defined in
css/support/interpolation-testcommon.js and setting prefs in
testing/profiles/web-platform/user.js seems to have a problem (bug 1604085),
so this place is the best place to set the pref for now.
And setting the pref reverts bug 1605866.
Differential Revision: https://phabricator.services.mozilla.com/D58722
--HG--
extra : moz-landing-system : lando
This cleans up and also allows us to keep the distinction between content: none
and content: normal, which allows us to fix the computed style we return from
getComputedStyle().
Do this last bit from the resolved value instead of StyleAdjuster, because
otherwise we need to tweak every initial struct for ::before / ::after.
Differential Revision: https://phabricator.services.mozilla.com/D58276
--HG--
extra : moz-landing-system : lando
This patch suppresses VR device access permission prompts for users that do not have any VR runtimes installed.
We could not depend on the existing VR device enumeration functions to suppress the permission prompts, as the
act of enumerating VR devices will result in some hardware physically powering on and software starting up (and staying running)
in the background.
This patch includes logic to spawn the VR process with an additional flag indicating that it should attempt only to detect the
runtimes, without proceeding to enumerate and activate hardware and software.
VRManager now includes an enum to more clearly organize it's state machine model, which now must ensure that the runtime detection
happens on-demand when the VR session support capabilities are first determined.
There is a new pref to disable the suppression of permission prompts for use within permission UI tests on machines without VR runtimes.
Renamed some variables and added comments to make code in nsGlobalWindowInner and Navigator clearer and better represent the updated logic -- to allow the separate detection of VR runtimes and VR session activation. Both the runtime detection and VR
session activity uses VREventObserver to send events to nsGlobalWindowInner.
Differential Revision: https://phabricator.services.mozilla.com/D57568
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Replace call to dict.iteritems by six.iteritems
--
wpt-commits: 878422d33b13cf46ec0d4f4201536426137ecc62
wpt-pr: 20920
Automatic update from web-platform-tests
Add content-aspect-ratio and update the description in canvas-aspect-ratio (#20943)
* Update the description in canvas-aspect-ratio. And add a test for content style image, make sure the width and height attributes won't infer its aspect-ratio.
--
wpt-commits: 453b3f32d5ee5a855780f9c43adc4c77996ab128
wpt-pr: 20943
Automatic update from web-platform-tests
html: Fix <input type=time> stepUp()-stops-at-border test (#20961)
Currently, this test is the only one failed by all three major browsers
in the file. Discovered by Kevin Raynel <kevinr@theodo.fr>.
--
wpt-commits: 53266c3b093c765918b37c7bd76b166d3b86d1f4
wpt-pr: 20961
Automatic update from web-platform-tests
XPath: Do not accept whitespace characters other than #x20, #x9, #xD, and #xA
Specification: https://www.w3.org/TR/1999/REC-xpath-19991116/#NT-ExprWhitespace
Bug: 1036767
Change-Id: I337ec70fefe8259d50bcf89a67b6e73c68fa585f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1980251
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727844}
--
wpt-commits: e08790c4a97eb7d4ad8a13b1f917bfae3b08d334
wpt-pr: 20906
Automatic update from web-platform-tests
Disallow recursive custom element constructions
With this CL, recursive custom element constructions are no
longer allowed. I.e. this will now only run the constructor once:
class extends HTMLElement {
constructor() {
super();
customElements.upgrade(this);
}
}
Previously, the code and spec had a bug which caused the above
code snippet to infinitely recurse. In [1] the spec has changed,
to set the custom element state to "failed" before the constructor
is called. With this change in place, recursive calls will
early-out at step #2 (of [2]), and avoid the recursion.
[1] https://github.com/whatwg/html/pull/5126
[2] https://html.spec.whatwg.org/multipage/custom-elements.html#upgrades
Bug: 966472
Change-Id: I76e88c0b70132eee2482c304ef9e727ae1fe8fc7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1931644
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727841}
--
wpt-commits: 4f24cabbe1f503f3daf8cf0834f4fb1a032f31bc
wpt-pr: 20465
Automatic update from web-platform-tests
[web-animations] Fix test in setting-the-playbackrate-of-an-animation.html (#20905)
This test assumes that currentTime will not change after waiting for
ready but the spec does not require that so this patch inverts these two
lines.
--
wpt-commits: c328e2ae1924a40d07dc552c4587ecc649eef0fd
wpt-pr: 20905
Automatic update from web-platform-tests
[LayoutInstability] Fix flaky tests
In this CL, some 'await waitForAnimationFrames(2)' are added to wait for
the initial render of the test page before introducing the observer.
This removes flakiness of these tests in WPT.fyi. Other cleanups are
done in the test files.
Bug: 1036013
Change-Id: Ic2631faf03ad00c8e32013c100c3b4ab867be2b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982708
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727639}
--
wpt-commits: 11f1a592c17fb4a7bb5c3081493ebb6a04a0aa39
wpt-pr: 20924
Automatic update from web-platform-tests
[LayoutInstability] Cleanup test observe-layout-shift.html
Currently, the test contains two async_tests, which is not good because
they run in parallel so the tests can affect each other. The first test
is redundant with buffer-layout-shift.html. The second test uses a
helper function from EventTiming, so we import the script instead of
copy-paste and we rename the test.
Change-Id: Ibe6d200441a07c603bccf0858406cf2c4f1d37a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1982710
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727640}
--
wpt-commits: a3f46a8e90c9bf8e0c860525cce7ae5f10654234
wpt-pr: 20926
Automatic update from web-platform-tests
[webnfc] Correct error type
Per spec:
If languageLength cannot be stored in 6 bit (languageLength > 63),
throw a SyntaxError.
But current implementation throws a TypeError, this CL fixs the error type.
Bug: 520391
Change-Id: I6ff64d87b387a07fff926ada80e5ee5d73b716b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981199
Commit-Queue: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Leon Han <leon.han@intel.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#727414}
--
wpt-commits: 36507c8b6fe2d51971da07c913589ef1621f1651
wpt-pr: 20915
Automatic update from web-platform-tests
LazyLoad: Timeout when moving image elements between documents
This CL adds WPT test for moving image elements between documents
as well as removing image elements.
Bug: 1001968
Change-Id: I725b60bfaf2406d7fdeabe8d4422d0618dc29478
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967084
Reviewed-by: Dominic Farolino <dom@chromium.org>
Commit-Queue: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#727350}
--
wpt-commits: 7ed322c3132993bcb5734702b40621448670fc76
wpt-pr: 20774
Automatic update from web-platform-tests
Add support for running crashtest tests with webkitgtk (#20914)
* This adds support in the webkitgtk_minibrowser, webkit and epiphany
product runners for running crashtest tests.
--
wpt-commits: e936890351047304cdc98d31d555f6d6a068097e
wpt-pr: 20914
Automatic update from web-platform-tests
[Native File System] Writable File Stream
This implements a WritableStream-based API.
WritableStream methods are fully implemented.
Operations are queued and the WritableFileStream can be piped to.
tell() queuing tracked at https://crbug.com/1034210
Transferability tracked at https://crbug.com/1035673
More information in the design doc: https://bit.ly/36wfLFA
BUG=955189
Change-Id: Ibd2e0a29c230a2fa25b6133fdbaac4f4ad4f1eb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913586
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727179}
--
wpt-commits: da7be43c647270534d83c44d6af9a76ca1faf1d1
wpt-pr: 20261
Automatic update from web-platform-tests
Use HTTP_NOTSAMESITE_ORIGIN for split cache Web Platform Test
Currently HTTP_REMOTE_ORIGIN is used as the third-party origin, but
this does not work for split cache experiments using eTLD+1 as the
additional key (i.e. when UseRegistrableDomainInNetworkIsolationKey is
enabled). This is due to HTTP_REMOTE_ORIGIN simply prepending 'ww1.' to
the HTTP_ORIGIN, which results in the same registrable domain.
Bug: 1035508
Change-Id: Ib42bb30491bb451a47b80914a48e252a9c93d10f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978037
Reviewed-by: Shivani Sharma <shivanisha@chromium.org>
Commit-Queue: Alex Turner <alexmt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#727110}
--
wpt-commits: 44e3f8a64aacebd5123aac7456cb81f423c38860
wpt-pr: 20880
Automatic update from web-platform-tests
[IndexedDB] Adding web platform test for index tombstones
This web platform test ensures that indexes update correctly for
cursors. If an implementation creates tombstones for index updates, then
this should test that those tombstones are ignored.
R=jsbell@chomium.org, pwnall@chromium.org
Bug: 1033996
Change-Id: I07585d9ec065b1ad4f8b720efceaca0987984869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972579
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726918}
--
wpt-commits: 560d73983d08fd0e36244f743d8c54a3b18e558c
wpt-pr: 20821
Automatic update from web-platform-tests
Enable file uploads in web_tests via testdriver-vendor.js.
testdriver supports file uploads via send_keys to the input element,
on the other hand eventSender supports file uploads via drag&drop to
the input element. So this CL implements test_driver_internal.send_keys
by using the drag&drop functionality if the target element is an
<input type=file>.
Also fixes a bug in file_upload.sub.html where backslashes in the file
path weren't being escaped, resulting in the test not working on windows.
Change-Id: I9a446f8dac3ae7817bb03ba9592d2537223b0f33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974849
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726873}
--
wpt-commits: c8158bdeea965ceecd5a95d507e75e863fdc6d0e
wpt-pr: 20857
Automatic update from web-platform-tests
Change how wptrunner computes reftests (#20459)
This preserves the current data structures within wptrunner as it
passes them onwards to Marionette currently in the Firefox case, and
as such changing them involves changes within Firefox too.
Those changes within Firefox are ones we should make, and is tracked
by https://bugzilla.mozilla.org/show_bug.cgi?id=1598340, before
changing how reftests are represented within wptrunner.
--
wpt-commits: e9fe7bf0c8d0d48f4fc36d6631c1d05af071792c
wpt-pr: 20459
--HG--
rename : testing/web-platform/tests/infrastructure/metadata/infrastructure/reftest/reftest_fuzzy_chain_ini.html.ini => testing/web-platform/tests/infrastructure/metadata/infrastructure/reftest/legacy/reftest_fuzzy_chain_ini.html.ini
rename : testing/web-platform/tests/infrastructure/reftest/fuzzy-ref-2.html => testing/web-platform/tests/infrastructure/reftest/legacy/fuzzy-ref-2.html
rename : testing/web-platform/tests/infrastructure/reftest/fuzzy-ref-2a.html => testing/web-platform/tests/infrastructure/reftest/legacy/fuzzy-ref-2a.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_fail.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_fail.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch_0.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch_0.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_and_mismatch_1.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_and_mismatch_1.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_0-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_0-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_1-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_1-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_fail.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_fail.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_cycle_fail_0-ref.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_cycle_fail_0-ref.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_fuzzy_chain_ini.html => testing/web-platform/tests/infrastructure/reftest/legacy/reftest_fuzzy_chain_ini.html
rename : testing/web-platform/tests/infrastructure/reftest/reftest_or_0.html => testing/web-platform/tests/infrastructure/reftest/reftest_multiple_match-0.html
Automatic update from web-platform-tests
Add a way to signal AR support through FakeXRDeviceInit
Aligns our MockRuntime implementation to changes introduced by:
https://github.com/immersive-web/webxr-test-api/pull/45
Change-Id: Icd33b566118501457c338a1d7882d260bf3f48e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974310
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Piotr Bialecki <bialpio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726856}
--
wpt-commits: cfa8792159ff63e208d4133ce692d2980bb41f90
wpt-pr: 20847
Automatic update from web-platform-tests
[css-pseudo] Properly set 'display: inline-block' to outside ::marker
Before this patch, outside markers were assigned 'display: inline-block'
but this happened in two different places: in LayoutNGListItem for
markers with 'content: normal', and in StyleAdjuster for content ones.
However, this meant that 'getComputedStyle(el, "::marker").display'
would be 'inline' in the former case and 'inline-block' in the latter.
This patch fixes that issue by ensuring that StyleAdjuster runs for all
markers, assigning 'display: inline-block' to outside ones even when
'content: normal'.
This has a noticeable effect even if the CSSMarkerPseudoElement flag is
disabled: text decorations are no longer propagated to outside markers.
This is actually expected, since decorations shouldn't be propagated to
inline-block descendants. They were being propagated for markers with
'content: normal' because the code that stops the propagation either
wasn't running for unstyled markers, or for styled normal markers it was
running before 'display: inline-block' was assigned.
This change won't be a compat problem since none of Chromium legacy,
Firefox and Edge propagate text decorations to outside markers by
default. Doing it seemed a LayoutNG bug.
Spec: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo
Spec: https://drafts.csswg.org/css-lists/#list-style-position
Spec: https://drafts.csswg.org/css-text-decor-4/#line-decoration
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-016.html
TEST=external/wpt/css/css-pseudo/marker-display-computed.html
The marker-content-016 test fails in legacy since the 'content' property
is not supported yet in ::marker
Change-Id: Ia1396a4f6c5d9825dba5a6265c32096a7066fbed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975887
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#726783}
--
wpt-commits: 2cb652e543d379bafcb3d0d26e2de28836f22df4
wpt-pr: 20864
Automatic update from web-platform-tests
[EventTiming] Fix crossiframe test
This CL does the following fixes to crossiframe.html test:
* Remove slow-image and onload, which are obsolete assumptions.
Instead, rely solely on PerformanceObserver.
* Use awaits where needed to make the test logic more sequential.
* Use coordinates and test_driver.Actions() to target the iframe. Using
the test_driver.click directly won't work for elements in iframes.
* Updates the test to check reasonable values for the frame and iframe
entries and check that they don't receive each other's entries.
This CL also:
* Removes unneeded variables from the clickAndBlockMain().
* Removes manual test, which is no longer needed.
Bug: 831729
Change-Id: Iff50035a216b21f67cd71796023af4f934573086
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972249
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726422}
--
wpt-commits: 80e94e6d5113f3670e0b36c0a1fd905a43ce65d5
wpt-pr: 20819
Automatic update from web-platform-tests
Refactor data-feeding for ImageDocument/ImageDocumentParser
ImageDocumentParser keeps the ImageResource for ImageDocument and passes
the associated ImageResourceContent to the HTMLImageElement used for the
ImageDocument.
This eliminates ImageDocument::CachedImageResourceDeprecated and cleans
up ImageDocument<->ImageDocumentParser interaction a bit.
The creation of the ImageResource now takes place in the first call to
ImageDocumentParser::AppendBytes rather than indirectly via a call to
ImageDocument::CachedImage.
Set ImageLoader::image_complete_ in the same as for regular image-loads,
and start dispatching 'load' (and 'error') events for the <img> element
in the image document. This behavior matches Gecko.
Bug: 958339
Change-Id: Iacdab89f6894adf70163f0d5300aefc9b2fce4e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975921
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726803}
--
wpt-commits: 25ec2153abd47ea8b7a8cba23b3f153167c0805d
wpt-pr: 20889
Automatic update from web-platform-tests
[css-layout-api] IntrinsicSizes Implementation
This change adds support for the CSS Layout API intrinsicSizes()
callback function. The implementation closely matches that of the
layout() callback function.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#intrinsicsizes
- Algorithm:
https://drafts.css-houdini.org/css-layout-api/#invoke-an-intrinsic-sizes-callback
The implementation also involved exposure of the
IntrinsicSizesResultOptions type.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#dictdef-intrinsicsizesresultoptions
Support was also added for the Child intrinsicSizes() function.
- Spec:
https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes
- Algorithm:
https://drafts.css-houdini.org/css-layout-api/#dom-layoutchild-intrinsicsizes
Bug: 726125
Change-Id: Ifc6064e069b4c9c5218c9d783b7d9de6a480e7ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1949536
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725834}
--
Rename some colliding references
--
wpt-commits: f160db31bb6fdf94c6c914a779a1b47b9e0e4e30, 5f8d15ebdcf0495c271c81776971061be1366445
wpt-pr: 20682
--HG--
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/absolute-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-absolute-ref.html
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/floats-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-floats-ref.html
rename : testing/web-platform/tests/css/css-layout-api/auto-block-size/negative-ref.html => testing/web-platform/tests/css/css-layout-api/auto-block-size/auto-block-size-negative-ref.html
rename : testing/web-platform/tests/css/css-layout-api/fallback-layout/fallback-ref.html => testing/web-platform/tests/css/css-layout-api/fallback-layout/fallback-layout-fallback-ref.html
Automatic update from web-platform-tests
COEP: Enforce CORP in cache.match()
Document using:
"Cross-Origin-Embedder-Policy: require-corp"
must not access cross-origin response that do not have the header:
"Cross-Origin-Resource-Policy: cross-site"
This is about only no-cors requests. CORS requests are checked against the
CORS headers instead.
See:
- https://github.com/whatwg/fetch/issues/985
- https://github.com/w3c/ServiceWorker/issues/1490
Bug: 1031542
Change-Id: I94a2cb9435fcf3e76f57a8f3d3344c87fa23f9a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973913
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726782}
--
wpt-commits: 236e6dbc70e128ab5ff5bad6ab98888281df8ffd
wpt-pr: 20840
When we run a suite more than once we can get more than one result for
a test. Iterate over all results when writing the summary rather than
erroring out in this case.
Probably a better solution would be to only write the result from the
current run, but we don't necessarily know what that is, since it's
not tracked by the SummaryHandler.
Differential Revision: https://phabricator.services.mozilla.com/D58133
--HG--
extra : moz-landing-system : lando
Bug 1594748 enabled cross origin opener policies but only on desktio Nightly.
Differential Revision: https://phabricator.services.mozilla.com/D58565
--HG--
extra : moz-landing-system : lando
Stylebench is patterned after Speedometer and calculates overall score from subtests in the same way. Stylebench should be marked as subtest_lower_is_better just like Speedometer.
Differential Revision: https://phabricator.services.mozilla.com/D56557
--HG--
extra : moz-landing-system : lando
Join <topsrcdir> with MANIFEST_PATH in android_device.py. I was concerned about TOOLTOOL_PATH
also, but that is already consistently joined with <topsrcdir> before use. I think these
are the only cases that needed attention.
Differential Revision: https://phabricator.services.mozilla.com/D58548
--HG--
extra : moz-landing-system : lando
This is the right thing to do, and prevents a race where we try to log
after the stdout capture queue is closed
Differential Revision: https://phabricator.services.mozilla.com/D56567
--HG--
extra : moz-landing-system : lando
Changes:
As part of python3 compatibility work, remove files that are no longer being used as far as I can tell (looking in searchfox).
Differential Revision: https://phabricator.services.mozilla.com/D58472
--HG--
extra : moz-landing-system : lando
This commit changes IsBidiLeaf to mark ruby boxes not a bidi leaf, since
conceptually they are not. I auditted all uses of it, and I believe it
makes more sense this way.
Differential Revision: https://phabricator.services.mozilla.com/D58290
--HG--
extra : moz-landing-system : lando
Changes:
Bring this file up to python3 standards.
This file is used indirectly in the `iris(av)` tests.
Differential Revision: https://phabricator.services.mozilla.com/D58474
--HG--
extra : moz-landing-system : lando
Do the same we do for classes for now. We could be more precise and achieve a
bit more sharing with some more effort (left a comment there), but it seems
unlikely to matter in practice (and if we did that, we'd probably want to do the
same for classes).
Differential Revision: https://phabricator.services.mozilla.com/D58453
--HG--
extra : moz-landing-system : lando
Changes:
Change the python version used in mozharness testing to python3.6 as that's what the `linter` docker image has, not `python3.5`.
Promote the tier of mozharness-py3 test to tier 1 and run it on all repositories to ensure python3 compatibility for future changes.
Differential Revision: https://phabricator.services.mozilla.com/D58209
--HG--
extra : moz-landing-system : lando
All usage of `synthesizeDragStart()` is, starting drag, cancel `dragstart`,
and finally compares `dataTransfer` items and given expected data. So,
we can make the users use `synthesizePlainDragAndDrop()` instead. It's
better API because it computes position of mouse operations at runtime and
checks whether the drag start was succeeded with optional logging feature
(i.e., it's easier to debug of intermittent failures).
This patch creates `synthesizePlainDragAndCancel()` for convenience. It
handles `dragstart` instead of the callers.
Differential Revision: https://phabricator.services.mozilla.com/D58214
--HG--
extra : moz-landing-system : lando
Most tests which use these APIs don't want to distinguish difference of
linebreaks (i.e., CRLF vs. CR vs. LF). And also most tests don't want to
check prefix and postfix of HTML data in clipboard on Windows.
Therefore, this patch makes them compare clipboard data with expected string
smarter. Every linebreak in clipboard data are treated as LF. Expected
HTML data is wrapped with `<html>`, `<body>` and comment nodes only on
Windows at comparing with clipboard data.
Differential Revision: https://phabricator.services.mozilla.com/D57963
--HG--
extra : moz-landing-system : lando
Changes:
Change assert from `assertEquals` to `assertEqual` since the former has been technically deprecated as of 2.7.
Add python3 compatibility in `setup.py`.
This should be the last item to bring full python3 compatibility to manifestparser.
Differential Revision: https://phabricator.services.mozilla.com/D58208
--HG--
extra : moz-landing-system : lando
This matches other browsers.
Keep the restriction just to chrome nodes, and in that case, avoid getting into
the broken state, which is what causes the issue. I'm not sure if this even
matters anymore given e10s but...
Differential Revision: https://phabricator.services.mozilla.com/D57475
--HG--
extra : moz-landing-system : lando
This is a pretty straightforward patch; we add `WindowsIATPatcher` to
implement the actual IAT patching, and use a partial specialization of
`FuncHook` to account for the underlying differences in implementation vs our
existing interceptor code.
Differential Revision: https://phabricator.services.mozilla.com/D57831
--HG--
extra : moz-landing-system : lando
This is a pretty straightforward patch; we add `WindowsIATPatcher` to
implement the actual IAT patching, and use a partial specialization of
`FuncHook` to account for the underlying differences in implementation vs our
existing interceptor code.
Differential Revision: https://phabricator.services.mozilla.com/D57831
--HG--
extra : moz-landing-system : lando
Previously, raptor mozharness jobs always exited with the return code of the
raptor test harness. With this patch, the mozharness job will exit with the
return code of the log parser, if the parser detects an error. This enables,
for example, exiting with TBPL_RETRY and triggering a task retry when the
test harness reports an ADBTimeoutError or similar.
Differential Revision: https://phabricator.services.mozilla.com/D58011
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Service worker: updating ready tests (#20655)
* Modernising ready test
* Removing test that no longer applies
* Waiting for activate
--
wpt-commits: 8986297ff16650c6cad632fcacfba7c2f9054ea7
wpt-pr: 20655
Automatic update from web-platform-tests
[css-grid] Grid align content distribution tests (#20110)
* add content distribution test, including cases for vertical-lr and vertical-rl
--
wpt-commits: efb47196a63bdb8c0cfdcc9415ab58bbbf02e0c0
wpt-pr: 20110
Automatic update from web-platform-tests
[webnfc] Reject the push when a non-NDEF tag comes in proximity
Previously, when a non-NDEF tag comes in proximity, NDEFWriter#push()
does nothing and still keeps in pending state.
This CL switches to reject NDEFWriter#push() in such case so that WebDev
can get a sense of what's happening.
BUG=520391
Change-Id: I17569910466e75f12ff4e37c29180e2a9af9db13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967745
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#726643}
--
wpt-commits: 256b4685b8e702c14ed854347f23f4979edbfc8e
wpt-pr: 20859
Automatic update from web-platform-tests
CSP: Parse and report violations from Content-Security-Policy-Report-Only
headers in the browser process.
Bug: 759184
Change-Id: Iefb33fa8ec2264f3e224d5a3ab92417160848fdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958692
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726618}
--
wpt-commits: be373901c6e71b8a14e9e2235a4961ef2ab62bfb
wpt-pr: 20688
Automatic update from web-platform-tests
XPath: Fix normalize-space()
It should handle only XML white spaces; #x20, #x9, #xD, and #xA.
We incorrectly handled other white spaces such as U+3000.
Bug: 893929
Change-Id: I59708f978ba1c23141f748de7a8f4c58d58c7acf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974713
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726557}
--
wpt-commits: 3a9bcdca3cf0ce754528e5c2e5503bb07ea3af9d
wpt-pr: 20861
Automatic update from web-platform-tests
Never let a non-zero-size pixel snap to zero size
The logic for LayoutUnit::SnapSizeToPixel maps the size to
the closest pixel align edge given a location. When a size of
width less than 1 happens to straddle a pixel aligned edge this
forces the size to zero.
Force the size to always be non-zero if the input size is non-zero,
and change PhysicalRect to use the LayoutRect snapping to get
correct cull rects.
Bug: 793785
Change-Id: Ia4c30d10c389fb4677006441aac9ee380a7c2f41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1948057
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726516}
--
wpt-commits: 30896bb9378b84ffd5583a1088d4e2862f19dc66
wpt-pr: 20871
Automatic update from web-platform-tests
Implement new pseudoElement interface on KeyframeEffect
Make target() return the originating element if target_ is a
PseudoElement (EventTarget still returns the layout object).
Add pseudoElement() property which returns the target pseudo-selector
if the target is a pseudo-element (null otherwise).
Invalid and unsupported pseudo-elements will still return a selector
and the originating element (from target()) but will not animated
(EventTarget returns null).
Add pseudoElement option to KeyframeEffect constructor.
Change-Id: Id7d16ea6966c533e56d1170462ff60a79b277fd5
Bug: 981894
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1921343
Commit-Queue: George Steel <gtsteel@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726506}
--
wpt-commits: 084d8726a0cde51d0fdd1e4bc375fa8788b6835b
wpt-pr: 20373
Automatic update from web-platform-tests
Fix `text-overflow: ellipsis` when `text-indent` is also applied
This patch fixes `text-overflow: ellipsis` to take the space
occupied by `text-indent` into the account.
Bug: 1006395
Change-Id: I417176efbc8f10fa3c073efa7695458fb2d302a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975372
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726504}
--
wpt-commits: 50046d4a51fe25bb4afc4883579a4b067e3137e0
wpt-pr: 20858
Automatic update from web-platform-tests
Origin policy: update feature policy parsing to match the latest spec
This updates the parsing of the feature policy parts of the origin
policy manifest to mostly match the latest spec draft at
https://wicg.github.io/origin-policy/, in particular
https://wicg.github.io/origin-policy/#parsing. That is, it moves away
from "feature-policy": ["... FP string"] to
"features": { "policy": "... FP string" }. This changes the data model
from a list of FP strings to an optional FP string. Additionally, it
removes the failure on parsing errors, as those are no longer in the
spec.
This does not yet properly parse the FP string as a FP directive;
instead it still treats it as a header (so, commas are allowed inside).
A failing test is added for that case, which will be addressed in a
followup CL.
Bug: 751996
Change-Id: I51711ee9381ecfc705683ba0eb870e461fed434e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965905
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726494}
--
wpt-commits: db14bfd40ccbf3cd633d759c96329b36ff1b53b6
wpt-pr: 20772
Automatic update from web-platform-tests
[css-pseudo] Recalculate viewport units in ::marker (#20795)
If a marker uses viewport units (vw or vh), they should be recalculated
when the size of the viewport changes.
This patch updates node traversal methods to include ::marker, so that
it's taken into account when updating viewport units.
However, this is only fixed for markers with non-normal content, since
otherwise they aren't implemented as real pseudo-elements yet.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-014.html
The test still fails because it includes cases with 'content: normal'.
Change-Id: I7495dd5c4bbd84d6286635a63199bfcc663c62c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970015
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#725463}
--
wpt-commits: 6d7a762c4c65d06fc95752f17ce96426c7b2d441
wpt-pr: 20795
Automatic update from web-platform-tests
[scroll-to-text-fragment] Apply :target CSS pseudo-class to match.
Per the spec, the common ancestor element of the match range becomes the
target element[1] and should have the :target pseudo-class applied.
[1]
https://html.spec.whatwg.org/multipage/browsing-the-web.html#target-element
Bug: 959163
Change-Id: Idb462a17972f4758df9617653f03b88196fd565a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965273
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Nick Burris <nburris@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726031}
--
wpt-commits: 7139b3d0aaeebe6cd40e62c46c06df630a49c2dd
wpt-pr: 20753
Automatic update from web-platform-tests
[OT-PW] Make it work with OOP-R
This CL makes off-thread paint worklet work with OOP-R. OOP-R serialize
an PaintOp and stores the serialized buffer in a shared memory. GPU
then reads the memory and de-serialize it.
For off-thread paint worklet, we are producing a DrawImageRectOp. Note
that this DrawImageRectOp is different than a normal one. It is a
DrawImageRectOp that contains a DrawRecord that contains multiple
PaintOps in it. So this CL adds a special code path to serialize it,
for paint worklet DrawImageRectOp only. The way to serialize it is to
iterate over all the PaintOps inside the DrawRecord. In this way, we
do not need to change anything on the GPU de-serialize code.
We also changed the layout tests. We changed some tests, now using
fillRect instead of strokeRect.
The problem with strokeRect is that using GPU rasterization could
easily result in subpixel difference on different platforms. Using
fillRect will avoid that.
Bug: 1020238
Change-Id: Ie0aadfe217e462547cc16a273d09ec8a64f055a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1957012
Reviewed-by: Yi Gu <yigu@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725554}
--
wpt-commits: 15e4f2b5a97b2fcd14c592f2de16cc62a82c645d
wpt-pr: 20705
Automatic update from web-platform-tests
Use Image::SizeAsFloat() and unsnapped rectangle in ImagePainter
The pixel-snapping of the destination rectangle can end up distorting
the geometry use for painting an SVG image preserveAspectRatio is used -
the larger the aspect ratio, the larger the error.
By passing the unsnapped rectangle to LayoutImageResource::GetImage, and
using Image::SizeAsFloat() to compute the source rectangle of the image,
e can minimize the error and allow the Image in question (an SVGImage)
to perform compensation for the difference in aspect ratio between the
snapped and unsnapped rectangles. This means that the painted result
will better approximate the intended rendering.
Also clean up accesses to the LayoutImageResource and ImageResourceContent
by adding and using local variables for them.
Bug: 812239
Change-Id: I0778648e7dd6fcca778a95123509f15b3519564c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969831
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#726375}
--
wpt-commits: 8e4a2c71523b8b9c078a6500711ff7ec1aa69bf4
wpt-pr: 20831
Automatic update from web-platform-tests
Fix OffscreenCanvas.convertToBlob worker exception tests
Previously they would always pass, regardless of the result.
--
Add SecurityError tests to offscreen-canvas/convert-to-blob
--
wpt-commits: df1173b63aa2e982309b50b4863256dce0c6436e, ff028c837c33dd07e62f927ce37844963e132369
wpt-pr: 20695
Automatic update from web-platform-tests
Add a test for serializing Module for storage.
--
wpt-commits: 0ae74ec621f758cfe426ab7cb71b5dd6be0a241c
wpt-pr: 20554
Automatic update from web-platform-tests
[css-pseudo] Let 'content' ::markers be forced to be inside
Even if a list item has 'list-style-position: outside', Chromium may
force its marker to be inside when it's a <li> outside a list element.
This information was stored in layout, but this created an undesirable
dependency since the computed 'display' value of the marker depends on
whether it's inside or outside. And it wasn't possible to force a marker
with non-normal 'content' to be inside.
This patch fixes it by adding an internal 'IsInsideListElement' flag in
ComputedStyle. This design also avoids traversing all the ancestors of
every <li> element.
BUG=457718
TEST=external/wpt/css/css-pseudo/marker-content-015.html
The test fails in legacy since 'content' is not supported yet.
Change-Id: I2df70841e8e9d729fd4aa47ec9b9973c09a82dcb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973914
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Cr-Commit-Position: refs/heads/master@{#726310}
--
wpt-commits: f61f56f084c397f6d46ffd18723300a124d12ea5
wpt-pr: 20837
Automatic update from web-platform-tests
[webnfc] Dispatch error events when failed to read a nfc tag
Trigger NDEFReader#onerror on all active readers when we found that the
nfc tag coming nearby is not NDEF compatible or some IO errors happened
when trying to read the tag, etc.
BUG=520391
Change-Id: I1cb0de0474942c9912cba465cb9d14c035e948c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1960479
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: François Beaufort <beaufort.francois@gmail.com>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#726253}
--
wpt-commits: 1268bd5901289acc95b1a576f108bdf382d82e44
wpt-pr: 20739
Automatic update from web-platform-tests
Disallow serializing and transferring non-origin-clean ImageBitmap (#20526)
The tests update for https://github.com/whatwg/html/pull/5114.
Add one test case for serialization, add one test case for
transferring. The relationship between COOP/COEP is now clear
and we can remove no-coop-coep.https.window.js.
--
wpt-commits: 578b1c621b57c2ad51442cb273bd5b8ea1dfed63
wpt-pr: 20526
Automatic update from web-platform-tests
XPath: Fix context node of rhs of union operator
The new behavior matches to Edge and Firefox.
Bug: 908632
Change-Id: I0dbb861e93836284a0c474cc486650dab27dc7b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973333
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726224}
--
wpt-commits: 3b8c7cec5f46c01850da7614058dae83ef2246c3
wpt-pr: 20828
Automatic update from web-platform-tests
XPath: Fix context node after evaluating an expression in a predicate
The new behavior matches to Edge and Firefox.
Bug: 625710
Change-Id: I27de8b769712062f548eb9d2274544d1ec0ff073
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973435
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726221}
--
wpt-commits: 1f3cbfb43e511f4707d8ec832089cae804546860
wpt-pr: 20829
Automatic update from web-platform-tests
Use [RaisesException] for immediate promise rejections in bluetooth
This is a part of effort for using [RaisesException] when synchronously
rejecting a promise.
It uses [RaisesException] for
//third_party/blink/renderer/modules/bluetooth.
Bug: 1001114
Change-Id: Iddb31cbbf71637ae989ea634f78207dfd9289c43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971049
Commit-Queue: Julie Kim(OoO til Jan 01) <jkim@igalia.com>
Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726215}
--
wpt-commits: 8934608dc507921b3701463053282909c5a86984
wpt-pr: 20808
Automatic update from web-platform-tests
Use XRSessionMode where appropriate
Refactor XRSessionOptions and XRRuntimeOptions to use an enum,
XRSessionMode, where appropriate rather than a pair of bools.
As the WebXr spec evolved, the mojom definitions evolved with it. Now
that WebVr has been removed and the spec has been solidified, this
refactors portions of the mojom to fit better and simplify the code. As
a result, a blink-side enum was able to be replaced with this new mojom
enum. Unfortunately, a device-side enum was not able to be removed, but
it was able to be scoped to just the SessionMetricsHelper. Hopefully
future cleanup will enable removal of this enum as well.
A couple of changes are worth calling out specifically:
Some slight behavior changes were added, which fit with the expectations
of the code. Namely, some runtimes that only checked for "immersive",
and not "environment_integration", now assert that the request is for
"ImmersiveVr", which more closely reflects reality.
XrRuntimeManager::GetRuntimeForOptions was also cleaned up from a more
complicated set of if-blocks to a switch statement.
Fixed: 1035205
Change-Id: I09f39d4a80f1454d5a9aa58fb785169ba5338510
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973156
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726205}
--
wpt-commits: b2e541f880ab1d03f0ba58b80a05993c43e2a8fc
wpt-pr: 20848
Automatic update from web-platform-tests
webxr-test: reset input source's clicked state after use
Using 'simulateSelect()' should generate only one "select" event, but since the
state value wasn't being reset it was also creating additional ones for each
following frame. This wasn't causing problems for the single existing test
using it (events_session_select_subframe), but is a trap for other uses.
Change-Id: I87cd55b1c0654d0183aa39af9bd5ad178d7409da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1974682
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726171}
--
wpt-commits: 269e7c07aa335a2d36279b2229b351fefbf98a80
wpt-pr: 20856
Automatic update from web-platform-tests
Preserve visual rect during layout tree reattachment.
Without this, a shift could hide from LayoutShiftTracker if the layout
tree had to be rebuilt due to a change in an ancestor's 'display'
property.
Bug: 1003459
Change-Id: Ib00772ff7846251533080b29d16f6cbaafc8189b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1958191
Commit-Queue: Steve Kobes <skobes@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#726137}
--
wpt-commits: 907bbfc36ceed7ad320e5175f329b70be318a854
wpt-pr: 20815
Automatic update from web-platform-tests
[CSS4Pseudo] Added 2 tests and 1 reference on selection and text-shadow
--
wpt-commits: b5b7813e9ce247495b0df30b2f9c8a35de2eacba
wpt-pr: 20802
Automatic update from web-platform-tests
Corrected a typo in float-shrink-to-fit-vrl-vlr-016.xht test
--
wpt-commits: 1799625e205a4457d879b6b9a3f74365f3b9cfd3
wpt-pr: 18602
Automatic update from web-platform-tests
Make interpolation-testcommon.js support composition
Port font-variation-settings-composition
Add composition test ability to external/wpt.
The Chrome passes all tests.
Firefox has a bug which give the output in reverse order.
Bug: 1034538
Change-Id: Ib71fc2518008144f7002eee95bff57fe90e05cce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965910
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#725575}
--
wpt-commits: b4f67181463668e61186828d11abee6d079d98c3
wpt-pr: 20790
Bogdan Tara
Ricky Stewart
Jeff Gilbert
Ehsan Akhgari
David Major
Geoff Brown
Tarek Ziadé
Henrik Skupin
Emilio Cobos Álvarez
Jonathan Kew
Tom Schuster
James Graham
Oana Pop Rus
Narcis Beleuzu
Marian Raiciof
Agi Sferro
Boris Zbarsky
Andrew Halberstadt
Byron Campen [:bwc]
Edwin Takahashi
Cosmin Sabou
Hiroyuki Ikezoe
Steven Englehardt
Kearwood "Kip" Gilbert
Stephen Donner
Rob Wood
moz-wptsync-bot
marmeladema
cathiechen
Leon Han
Timothy Gu
Kent Tamura
Mason Freed
haozhe
Brian Birtles
autofoolip
Nicolás Peña Moreno
L. David Baron
Rob Buis
Wanming Lin
Carlos Alberto Lopez Perez
Olivier Yiptong
pyup.io bot
Ms2ger
Alex Turner
Gérard Talbot
Daniel Murphy
Marijn Kruisselbrink
Sam Sneddon
Piotr Bialecki
Oriol Brufau
Kai Ninomiya
Fredrik Söderquist
Alison Maher
arthursonzogni
Philip Jägenstedt
Tom Tung
Xidorn Quan
Ting-Yu Lin
Geoff Lankow
Masayuki Nakano
Andreea Pavel
Aaron Klotz
Gurzau Raul
Dave Townsend
Perry Jiang
Jake Archibald
_Ros_
Lucas Gadani
Stephen Chenney
George Steel
Koji Ishii
Domenic Denicola
Blink WPT Bot
Nick Burris
Xida Chen
Dominic Farolino
Chris Lord
Yutaka Hirano
Julie Jeongeun Kim
Alex Cooper
Klaus Weidner
Steve Kobes