Automatic update from web-platform-tests
Implement `Sec-Fetch-Mode`
This patch implements `Sec-Fetch-Mode`, which adds the current CORS
mode to outgoing, secure requests, as defined in
https://mikewest.github.io/sec-metadata/#sec-fetch-mode-header.
Bug: 843478
Change-Id: I811bfa86bdac1600b8abdd275d9526f6408e62e2
Reviewed-on: https://chromium-review.googlesource.com/c/1466362
Reviewed-by: Camille Lamy <clamy@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631651}
--
wpt-commits: 86bfe06b7260f552913b3274c30377ce7e9968b8
wpt-pr: 15348
Automatic update from web-platform-tests
Implement `navigator.getUserAgent()`
This patch is smaller than it looks. It basically does the following:
1. It introduces `blink::UserAgentMetadata`, and a corresponding mojo
type in order to hold the various shards of data we'd like to expose
about user agents (brand, version, platform, architecture, and
model).
2. It threads these new types down from //chrome and //content/shell's
implementations of `ContentBrowserClient` down into Blink via the
same route we're using for the existing user-agent string
(ChromeContentBrowserClient -> RenderProcessHost -> RenderThread
-> Platform -> LocalFrameClient -> FrameLoader).
3. It extends `Navigator` with a new `NavigatorUserAgent` mixin that
exposes `navigator.getUserAgent()`. This returns a promise that
resolves with a newly defined `UserAgent` IDL dictionary type.
So, the patch is huge, but not really that complex.
Bug: 928670
Change-Id: I4f267e373864162264ad4d721650942b147b378d
Reviewed-on: https://chromium-review.googlesource.com/c/1458098
Commit-Queue: Mike West <mkwst@chromium.org>
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631613}
--
wpt-commits: 290e4d77cd6418cf7b37351549c1ed2e5c62f557
wpt-pr: 15296
Automatic update from web-platform-tests
domparsing: Fix an issue that XMLSerializer generates new prefix for an attribute with an existing namespace
Add an implementation of "retrieving a preferred prefix string"
[1], and apply it to attribute serialization.
As the specification defines, this CL introduces another map [2] like:
namespace URI => [older prefix, ..., newer prefix]
in order to retrieve most-recently-declared prefix.
When we search the map for a prefix, we check availability of
the prefix by the existing prefix-namespace map.
There are two failing test cases in XMLSerializer-serializeToString.html.
They follow the specification.
* The first failing one: An non-well-formed XML is produced if we follow
the specification. Chrome's new behavior matches to Firefox. Safari also
produces a bad XML.
* The second failing one: Firefox, Safari, and Chrome without this CL
preserve prefix in such case. This CL keeps the interoperable behavior.
[1] https://w3c.github.io/DOM-Parsing/#dfn-retrieving-a-preferred-prefix-string
[2] https://w3c.github.io/DOM-Parsing/#dfn-namespace-prefix-map
Bug: 906807
Change-Id: Idaea590ba19c9c21acbaf456ea91ce550c74db5a
Reviewed-on: https://chromium-review.googlesource.com/c/1445033
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631573}
--
wpt-commits: 2647e1e8f6995d12f44edbf0b4fce752e5cb7ec5
wpt-pr: 15343
Automatic update from web-platform-tests
Picture-in-Picture: remove/rename some methods in player/video element.
Mostly follow-ups from https://chromium-review.googlesource.com/c/chromium/src/+/1379049
Some methods became pointless, some had their meaning significantly
changed.
This CL also changes the timing of requestPictureInPicture() and exitPictureInPicture()
in order to be sync until the call to the service.
Bug: 919860, 930338
Change-Id: I437a060c2dd92021d514c4d6e2ffeb9f4642525b
Reviewed-on: https://chromium-review.googlesource.com/c/1409544
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631517}
--
wpt-commits: 23aa71fddb589531b2883be10fcff85d535d374a
wpt-pr: 15345
Automatic update from web-platform-tests
[Animation Worklet] Upstream web tests (related to animator) to WPT
Test for animator-registration was purposefully left out of this group because it will be a more involved change
web_tests/animations/animationworklet/animator-animate.html -> web_tests/external/wpt/animation-worklet/animator-animate.https.html
web_tests/animations/animationworklet/animator-with-options.html -> web_tests/external/wpt/animation-worklet/animator-with-options.https.html
Bug: 915352
Change-Id: I3ccab26ec2134a2d02df9fc9ae4e42dd997264ea
Reviewed-on: https://chromium-review.googlesource.com/c/1468008
Commit-Queue: Jordan Taylor <jortaylo@microsoft.com>
Reviewed-by: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631489}
--
wpt-commits: 0e4b1315e61ec051dafad75c73f6258f718d56c6
wpt-pr: 15364
Automatic update from web-platform-tests
[svg] Test ry property parsing (#15315)
--
wpt-commits: 5852f617c1ad109939bdb6b70f362dcd84a5cb73
wpt-pr: 15315
Automatic update from web-platform-tests
Unclosed URL At EOF
Verifies that a url() (specifically, one that parses to a `<url-token>`) that's unclosed at EOF is still valid.
Also tests "empty" url(), because that was brought up as another source of divergence in the same issue. There's some disagreement on whether that's valid at all and how to represent it, so rather than take a stand, I just assert that it should parse the same as the closed version, whatever that is.
Tests <https://github.com/w3c/csswg-drafts/issues/3598>
--
Merge pull request #15369 from web-platform-tests/tabatkins-patch-1
Unclosed URL At EOF
--
wpt-commits: b4f35dc6027f5e8776ac9c20f85031e0f1437233, 8dbed22314172d637582b63fc96e946e2e0dfff4
wpt-pr: 15369
Automatic update from web-platform-tests
Added 2 calc() tests on angle and time units from google chromium project
--
Merge pull request #15342 from TalbotG/Values3-GT-PR18
Added 2 calc() tests on angle and time units from google chromium pro…
--
wpt-commits: 8a193070bd34b767ed59817cf463e7f6ffc3df59, 00d0131bfcd2f99e6f8e4a9696c797f7500c4c2d
wpt-pr: 15342
Automatic update from web-platform-tests
Relax required SNR a bit
The required SNR was a little too high for some Mac OS bots. Make it
a little smaller.
Bug: 929435
Change-Id: I5fbfe6573f4907f33999085e52bb22f4b4b9a126
Reviewed-on: https://chromium-review.googlesource.com/c/1457228
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631309}
--
wpt-commits: 91d81bb73d5e8424e45918c84e275a9d46c51d51
wpt-pr: 15270
Automatic update from web-platform-tests
[Animation Worklet] Clean up animator registration logic for wpt test
Similar to [1], we should register the animator only once in the setup
for test current-time.https.html.
Given that DocumentTimeline does not always move forward, this test
also replaces waitForNextFrame with waitForDocumentTimelineAdvance.
[1] https://cs.chromium.org/chromium/src/third_party/blink/web_tests/external/wpt/animation-worklet/scroll-timeline-writing-modes.https.html
Bug: 923881
Change-Id: Iabc6c7c1cea520e3dd81ed8a781cc072e2d8e20b
Reviewed-on: https://chromium-review.googlesource.com/c/1466145
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631287}
--
wpt-commits: 109654d2560bf74830e483fdf15cbbc67208a877
wpt-pr: 15344
Automatic update from web-platform-tests
Fix shebangs and executable bits for a bunch of files (#15334)
Mostly adding missing executable bits or removing unnecessary ones.
In a few cases, missing shebangs were added.
--
wpt-commits: bac4db35ea82fa0a6ee65e9291c722592e27fb7f
wpt-pr: 15334
Automatic update from web-platform-tests
[LayoutNG] Add percentage_resolution_block_size into the min/max pass.
This was surprising to me! But the min/max sizes depend on the
percentage resolution block-size, as replaced elements reflect this
size into their width.
This was working previously as the replaced element was manually
computing the heights, but this adds it into the pass explicitly.
This fixes it for absolute positioned objects which use the current
final height as the input to this function.
Eventually we'll want to cache based off this, and record if there is
a replaced element with percentage block-size in the calculation chain.
Bug: 635619
Change-Id: I6db9a90007b6c7d70f51d5ae1209ffba8a629e03
Reviewed-on: https://chromium-review.googlesource.com/c/1456203
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#631236}
--
wpt-commits: bf3094004127a5b32edf8b80c8e4cc9bcad500d0
wpt-pr: 15322
Automatic update from web-platform-tests
Don't use mozdownload to download firefox
Instead use the same URL that's used by mozilla.org. This hopefully reduces the
problem where mozdownload tries to download a file that doesn't exist yet.
Note that we are still using mozdownload for geckodriver
--
wpt-commits: 803f7f06d6ca49211709dc1c4daa72393e6cb673
wpt-pr: 15329
Depending on the load, this.jsterm might not be
set when switching to the console panel, and can
cause a crash (blank tab).
This patch checks that this.jsterm exists before
taking further actions.
Differential Revision: https://phabricator.services.mozilla.com/D23511
--HG--
extra : moz-landing-system : lando
Refactored the TabQueueService to be a foreground service from Android O
onwards. The service now uses a foreground notification that briefly informs
the user that a new tab is being added to the queue.
Depends on D23528
Differential Revision: https://phabricator.services.mozilla.com/D23529
--HG--
extra : moz-landing-system : lando
On Wayland, `gtk_im_multicontext_get_context_id()` returns
`"wayland"`. However, we need to know actual IM which works
behind Wayland. Fortunately, `XMODIFIERS` env includes IME
name like "xim" case. Therefore, we can refer it instead.
Differential Revision: https://phabricator.services.mozilla.com/D23469
--HG--
extra : moz-landing-system : lando
`PresShell.h` is exposed as `mozilla/PresShell.h` and `PresShell` is the only
concrete class of `nsIPresShell`. Therefore, we have no reason to access
`PresShell` via `nsIPresShell`.
Differential Revision: https://phabricator.services.mozilla.com/D23277
--HG--
extra : moz-landing-system : lando
try to extend the animation time. I tested this locally on repeat 50 times.
Differential Revision: https://phabricator.services.mozilla.com/D23498
--HG--
extra : moz-landing-system : lando
