For compatibility with Chrome, when removing inline style at block parent,
we should reset the style with creating `<span>` element whose `style`
attribute removes the style. We do this only in CSS mode, but we should do
it in HTML mode too.
This patch also makes `FontFaceStateCommand::SetState()` ignore `tt` value
if its root caller is `Document::ExecCommand()`. It was implemented for
composer to handle XUL command in bug 115922. Therefore, we should not do
this special handling on the web. If it were possible to separate this
change to another bug, it'd be nicer. But without this change, we'll have
a lot of regressions of `Document.execCommand("fontname")`. Therefore,
this is also fixed in this patch.
Note that this removes first `.ini` file selection because
the tests cannot be run without test number range parameter.
So, the sections are not used anymore.
Differential Revision: https://phabricator.services.mozilla.com/D47862
--HG--
extra : moz-landing-system : lando
For compatibility with Chrome, when removing inline style at block parent,
we should reset the style with creating `<span>` element whose `style`
attribute removes the style. We do this only in CSS mode, but we should do
it in HTML mode too.
This patch also makes `FontFaceStateCommand::SetState()` ignore `tt` value
if its root caller is `Document::ExecCommand()`. It was implemented for
composer to handle XUL command in bug 115922. Therefore, we should not do
this special handling on the web. If it were possible to separate this
change to another bug, it'd be nicer. But without this change, we'll have
a lot of regressions of `Document.execCommand("fontname")`. Therefore,
this is also fixed in this patch.
Note that this removes first `.ini` file selection because
the tests cannot be run without test number range parameter.
So, the sections are not used anymore.
Differential Revision: https://phabricator.services.mozilla.com/D47862
--HG--
extra : moz-landing-system : lando
Otherwise we may keep the scroll anchor around and we may try to anchor to it
later even though we should've really suppressed it completely.
Maybe we should just call InvalidateAnchor() unconditionally from that code
path, even if there are no suppressions pending...
Differential Revision: https://phabricator.services.mozilla.com/D48456
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Remove unused --channel=experimental for resources/ tests
The argument is documented as "Chrome browser channel" and isn't used
here because Chrome isn't involved.
--
wpt-commits: e2381a6676f1ae4a491cfbac5805d25d491798a2
wpt-pr: 19342
Automatic update from web-platform-tests
Test origin-offset for `viewer` space
Bug: 1009129
Change-Id: Iea0ee4259c894db49a76f8f4e1ca9b53f95f69ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829296
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701468}
--
wpt-commits: 187e0e0d82dd6c2440ae6673b5ed2e130dc61a70
wpt-pr: 19409
Automatic update from web-platform-tests
Revert "Update emulated position on each XRFrame"
This reverts commit 8be89ae08126913ff4447927ac5a087b8d6babcf.
Reason for revert: Build failure:
https://ci.chromium.org/p/chromium/builders/ci/Win%20x64%20Builder/79827
[4142/15096] CXX obj/device/vr/vr/openxr_controller.obj
FAILED: obj/device/vr/vr/openxr_controller.obj
C:\b\s\w\ir\cache\goma\client\gomacc.exe ..\..\third_party\llvm-build\Release+Asserts\bin\clang-cl.e...(too long)
../../device/vr/openxr/openxr_controller.cc(204,19): error: no member named 'emulated_position' in 'device::mojom::XRInputSourceDescription'
description_->emulated_position = false;
~~~~~~~~~~~~ ^
1 error generated.
Original change's description:
> Update emulated position on each XRFrame
>
> For both the head poses and input poses, send this value through mojo
> from the device process to the renderer process on every frame.
>
> Bug: 969131
> Change-Id: Ie895deb75bddb6dd883d09828cfcb30f335d3793
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825478
> Auto-Submit: Jacob DeWitt <jacde@chromium.org>
> Commit-Queue: Will Harris <wfh@chromium.org>
> Reviewed-by: Will Harris <wfh@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Reviewed-by: Alexander Cooper <alcooper@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#701389}
TBR=dcheng@chromium.org,wfh@chromium.org,klausw@chromium.org,jacde@chromium.org,alcooper@chromium.org
Change-Id: I91ec66842b8f0a14bcb85145843fb4d617847066
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 969131
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1833005
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701401}
--
wpt-commits: 1eb937d8403daa35e94bec451643228f85831222
wpt-pr: 19428
Automatic update from web-platform-tests
Update emulated position on each XRFrame
For both the head poses and input poses, send this value through mojo
from the device process to the renderer process on every frame.
Bug: 969131
Change-Id: Ie895deb75bddb6dd883d09828cfcb30f335d3793
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825478
Auto-Submit: Jacob DeWitt <jacde@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701389}
--
wpt-commits: 1f22f318239a95db8df5afd5dd586809fcf762b2
wpt-pr: 19336
Automatic update from web-platform-tests
[LayoutNG] testcase for codependent scrollbars
Just a testcase, because the bug cannot be fixed at this time.
Aborted attempt to fix this is at:
https://chromium-review.googlesource.com/c/chromium/src/+/1820177/4
Bug: 1007065
Change-Id: I44195ec77cc8b0924c81a567a9505e8a77f7d492
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829878
Auto-Submit: Aleks Totic <atotic@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701345}
--
wpt-commits: e2f322248d49cfb11a1bbfebc49f4661b913dd96
wpt-pr: 19374
Automatic update from web-platform-tests
Migrate shape_detection.mojom.* interfaces to BrowserInterfaceBroker
This CL migrates code to the new BrowserInterfaceBroker class for the
TextDetection, BarcodeDetectionProvider and FaceDetectionProvider mojo
interfaces. This allows retrieving the remote implementation from the
renderer process without relying on FrameClient's InterfaceProvider.
Bug: 955171, 978694, 936482
Change-Id: I8772caa7877bc9d5ee14043dba87c59a4e9fbd77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1826782
Commit-Queue: Mario Sanchez Prada <mario@igalia.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701312}
--
wpt-commits: e2d4b543491ce7bfb51afdfb11a8197e1e78c223
wpt-pr: 19372
Automatic update from web-platform-tests
[wptrunner] Explicitly ignore certificate errors for Chrome
ChromeDriver will no longer pass --ignore-certificate-error by default
and users need to explicitly request the acceptInsecureCerts capability.
https://crbug.com/chromedriver/3148
--
wpt-commits: 98fe3d29b673c33e468e5661709a4e3ca33189d1
wpt-pr: 19402
Automatic update from web-platform-tests
Reland "[Payments] Enable shipping and contact info delegation [4/5]"
This is a reland of 3dd95e215bbb616913239ed37e61d15e894cf561
The payment_method_change_response is not renamed in the reland since clank
repository is using PaymentMethodChangeResponse.
The rename will be landed in a separate cl.
Original change's description:
> [Payments] Enable shipping and contact info delegation [4/5]
>
> This cl implements shipping address/option change events for PH. With
> this change payment handlers can notify the merchant when the user
> changes the selected shipping address/option, and wait for updated
> details (e.g. new shipping cost, etc) from merchant.
>
> For overall flow please check
> https://chromium-review.googlesource.com/c/chromium/src/+/1779003
>
> Bug: 984694
> Change-Id: Id881ba22bf4c846a4570801bacc49e5d4e89a72b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1804557
> Reviewed-by: Mike West <mkwst@chromium.org>
> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
> Commit-Queue: Sahel Sharify <sahel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#700238}
Bug: 984694
Change-Id: I9a1a84e56701287eb3625b6a681a3f346c47a6e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1828101
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Sahel Sharify <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701255}
--
wpt-commits: 421b6a7ee66ed3e48d5e16ed6cfd86c1f7f378ac
wpt-pr: 19343
Automatic update from web-platform-tests
Handle special origins for site_for_cookies computation at top-level.
In particular, at top-level too, the computation should be about origins,
not URLs, to resolve about:blank and to stop fighting with sandbox.
Bug: 911299
Change-Id: I2d1b05b597ec7c5062f7beb320ccc3384e22cf82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816656
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701142}
--
wpt-commits: 563a1ecea1478f6ef34c50259c3ff66bb5ea4fc3
wpt-pr: 19228
Automatic update from web-platform-tests
Fix updating metadata for results that are expected but have known intermittents
We were assuming that in the case that the status matched expected we'd have
no expected entry in the log data. But actually it was being set to None, so
handle both those cases.
Differential Revision: https://phabricator.services.mozilla.com/D44874
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1579168
gecko-commit: 4fe3084ae3e4ce4f20ebf6c0cf333381ac93a0c8
gecko-integration-branch: central
gecko-reviewers: maja_zf
--
Fix formatting
--
wpt-commits: 44df76773a7aa7361f6ca077180b3479d257cb16, 7c7f09fecc6dd4bcb38f97c9de4080038b067dac
wpt-pr: 19318
Automatic update from web-platform-tests
Update "Take Element Screenshot" and "Take Screenshot" user prompt tests to respect unhandled prompt behavior (#17563)
--
wpt-commits: 4f22c5b19bae217799ce92c9df6dfdf2800c6d81
wpt-pr: 17563
Automatic update from web-platform-tests
[WPT/upgrade-insecure-requests] Migrate to common/security-features generator
This CL migrates most of the wpt/upgrade-insecure-requests tests
from upgrade-insecure-requests/support/generate.py
into the /common/security-features generator framework.
Actual file regeneration is done in
https://chromium-review.googlesource.com/c/chromium/src/+/1788553
and the coverage will become larger than the current generator.
Particularly, this (and the regeneration CL) adds the following cases:
- `upgrade-insecure-requests` is delivered by HTTP response headers.
Previously, only the delivery via <meta> was tested.
- `upgrade-insecure-requests` isn't delivered and thus requests
are blocked (as mixed-content or simply failing to connect the server).
Previously, only successfully upgraded cases were tested.
Bug: 1001422
Change-Id: I351f4dcc75c1008cf743b63dfb585ca82e199f39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1788551
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701027}
--
wpt-commits: 186ba21183496dcf9ad5f4125986622dfef54f44
wpt-pr: 18903
Automatic update from web-platform-tests
OOR-CORS: Cleanup preflight algorithm changes
Now that the adding "Accept: */*" is clearly defined in
the fetch spec, this patch make some cleanups to follow
the spec algorithm, and remove a link to the issue thread.
Bug: 995740
Change-Id: I5a8899f1a02254e95009c4202957e73e8e4ece31
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1828767
Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701023}
--
wpt-commits: dd28ef4ed6b7a16ad2a4444ec27da805a4e02564
wpt-pr: 19364
Automatic update from web-platform-tests
Adding resource timing test that checks for #hash in the URL (#19015)
* Adding resource timing test that checks for #hash in the URL
Mostly copypasta of the `resource-timing/resource_cached.htm` test
Currently the test fails in Safari. Safari seems to strip the hash when it comes to images. XHRs look ok.
* simpler hash test, no iframes
using relatively recent features (filter and const), not sure if it's ok
* removed EOL whitespace
./wpt lint resource-timing
--
wpt-commits: 68abc3a55e4dcca5a5fc18c778619af0dee25d77
wpt-pr: 19015
