Automatic update from web-platform-tests
Port offset-*-interpolation-*.html to wpt
Most of these has corresponding tests in wpt/ already, this CL adds
some additional test cases that is not covered in wpt/.
Bug: 900581
Change-Id: I534b55582814b31cc0e3368afcf69eeefb45e661
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1763250
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689917}
--
wpt-commits: 00832c4cfcd3d93b9ea5ef35cb47ce9d0c2316f2
wpt-pr: 18592
Automatic update from web-platform-tests
Port offset-path-interpolation-*.html to wpt/
There are already 5 corresponding tests under css/motion/animation/ for
offset-path. 001--004 are almost identical with some numbers different
at from or to value. This CL adds some test cases to 005.html which
don't currently exist.
Bug: 900581
Change-Id: I9f6995313bdaa29baec19f26b781c95449be0a4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762371
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689912}
--
wpt-commits: 863ab8eb05f6fda8de334c81d91f566b816eaa18
wpt-pr: 18565
Automatic update from web-platform-tests
Add WPT test for responder iceConnectionState
This is based on the repro script in #968960.
At the moment, it gives consistent "new", "checking", "connected"
transitions.
Bug: chromium:968960
Change-Id: I88eb2d7d06410d6ea79196bc6cec10552e34d400
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660429
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689888}
--
wpt-commits: 6265e5cecf8fef67c6ed8783763a3a61abb2644f
wpt-pr: 18611
Automatic update from web-platform-tests
Add missing comma in earlyoom argument list (#18630)
Without the comma, the string literals are concatenated.
Spotted via `sudo earlyoom -p -r 60--prefer=(chrome|firefox) --avoid=python`
with a missing space in Taskcluster logs.
This was introduced in https://github.com/web-platform-tests/wpt/pull/15724.
--
wpt-commits: b3b48132272f9a92414ce879bd8a5ab468879b8f
wpt-pr: 18630
Automatic update from web-platform-tests
bluetooth: disconnect evt to standalone tests
This change updates the gattserverdisconnected-event tests in wpt/ to be
standalone window tests. This change allows the tests to be formatted
with clang-format.
Bug: 994756
Change-Id: Id08fd9bdef1fc8b37d8ad192b23e11a77a99f4c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761071
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Auto-Submit: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689743}
--
wpt-commits: d8cebfcaa00c03fdf60fc5b548b631a636e99754
wpt-pr: 18551
Automatic update from web-platform-tests
[WebXR] Resolve required/optional features per the spec
This adds support to resolve required/optional features against device
capabilities as well as sets up the plumbing for appropriately tailored
consent.
A WPT test for lack of device support was also added, which required
updating the tests.
Bug: 991605
Change-Id: Ibce6924492311544fd75ca36ed79aa855c943aad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757183
Auto-Submit: Alexander Cooper <alcooper@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Jacob DeWitt <jacde@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689605}
--
wpt-commits: 04c1d5adf9ab1e0b3b29a55599cf59727fcf9e93
wpt-pr: 18512
Automatic update from web-platform-tests
Add ability for service worker to filter out frozen windows.
Add code to support handling of frozen clients. Frozen clients do not
run their event loop, so postMessage to them just causes problems. To
allow service workers to continue working with frozen windows we expose
includeFrozen in the matchAll and the frozen attribute on the Client. If
a service worker calls focus on a client it will unfreeze the window when
it is moved to have focus. This feature is currently marked as
experimental and an intent to ship will be sent.
This is specified in https://wicg.github.io/page-lifecycle/ and
https://github.com/w3c/ServiceWorker/pull/1442
BUG=957597
Change-Id: I6abe1882e88c65dac99250db5bb7fa8d3a4b2b1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1677065
Commit-Queue: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689558}
--
wpt-commits: 3d052c54485970c1673500c1ba7d52182adf6f4f
wpt-pr: 17554
Automatic update from web-platform-tests
Create Web Platform Tests for Scroll to text
Add a web platform test that performs navigations to a test page with
various targetText parameters and checks if the target page
successfully scrolled as expected. Using a BroadcastChannel is the only
way to communicate whether the target page scrolled, since scroll to
text is specifically restricted from iframes or pages with an opener,
so there's no other way for the test page to track the status of the
child target page.
Bug: 994299
Change-Id: I69243e739c3a7469ac48647508e379f204ccfbf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756707
Commit-Queue: Nick Burris <nburris@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689453}
--
wpt-commits: 3c56e312080b972189b3dcfe57107b60527bb436
wpt-pr: 18469
Automatic update from web-platform-tests
MathML: Wait for Ahem fonts to be ready for displaystyle dynamic tests. (#18614)
--
wpt-commits: 3ccf6da39967fe9e9c296c4b9342e3de8dcf4c98
wpt-pr: 18614
Automatic update from web-platform-tests
[css-flexbox] Only clear the override size if we're doing layout
And make ChildUnstretchedLogical{Width,Height} handle the case where
an override size is set (by clearing and re-setting).
The problem with clearing the override size, but not doing layout,
is that we may later do a simplified layout which will then
lay out as shrink-to-fit, which is undesired.
Bug: 992010
Change-Id: I18d3ae66f62cbdc9cdcf76810dc0eff6be915af6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758940
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689485}
--
wpt-commits: 768d6294ed324158d4269a833fda94ea7927efe3
wpt-pr: 18573
Automatic update from web-platform-tests
Revert "[CSS] Treat viewport-relative units as computationally independent"
This is a speculative revert in order to either confirm or eliminate it
as a source for a hard to track down persistent performance regression.
This reverts r679183 (commit 6b846d3689b9038c73d87ecbab61670e91c7e051).
Bug: 993476
Tbr: pdr@chromium.org
Change-Id: I37566d32fb0853590e72299fdc0f281c712bf027
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1764195
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689475}
--
wpt-commits: 7c8e32ead1a5cc9b402558fd43d0c555bd31965f
wpt-pr: 18612
Automatic update from web-platform-tests
Skip problematic tests in Safari using --exclude (#18585)
Workaround for https://github.com/web-platform-tests/wpt/issues/16229.
--
wpt-commits: 2c25b504c582b31efdd33ae429de78efe9558331
wpt-pr: 18585
Automatic update from web-platform-tests
[LayoutNG] Give flex items their stretched size earlier.
Force the cross size on stretchy items when they are laid out for
flex base sizing or cross size determination.
Bug: 845235
Change-Id: I49c6b9a9ef1d2e86aa02c47841075ed2726d5619
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762816
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689303}
--
wpt-commits: 0702f3fe6d81479cb42dcc59c930599cd28ca5cc
wpt-pr: 18572
Automatic update from web-platform-tests
Corrected text assert of abs-pos-non-replaced-vlr-213.xht test (#18605)
--
wpt-commits: 738a91a4ef94f5163c0addc53e2f65d42a0e3cda
wpt-pr: 18605
Automatic update from web-platform-tests
bluetooth: descriptor tests to standalone window
This change updates the descriptor tests in wpt/ to be standalone window
tests. This change allows tests to be formatted with clang-format.
Bug: 994756
Change-Id: Ifcedeadd35d0775793269572fec478eaa5dbe06d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757889
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Auto-Submit: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689260}
--
wpt-commits: e6dc25e5af4343c1220996a54ba24a735d3ce81c
wpt-pr: 18504
Automatic update from web-platform-tests
[LayoutNG] Lay out flex items with ShrinkToFit in more cases
A row flex box's cross size of {fit,min,max}-content isn't definite,
which affects the inline size of orthogonal children.
Bug: 845235
Change-Id: Id08a1cf6d23e9e295e87c52d426079bc7e886b74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758992
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689232}
--
wpt-commits: a1cec169e027d234248e36e74c29b1efae1b528c
wpt-pr: 18514
Automatic update from web-platform-tests
Support percentage comparison resolution against negative reference values
It's a very edge case that a percentage may be resolved against a
negative value, which is allowed only in 'background-position' property.
To support this without massively changing existing code, this patch
adds an indicator flag to |CSSMathFunctionValue|, so that when the flag
is set, the resolution of calculated percentage values is delayed to when
a reference value is available. When the flag is not set, we still use
the existing code path where a calculated percentage value can be
resolved immediately.
Together with this patch is a test suite on parsing and evaluation of
comparisons on percentages.
Bug: 825895, 978682
Change-Id: I2a6aabd48313ccda82b50f6dc00fd62c4548bc84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762970
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689198}
--
wpt-commits: 8f929221b0664b735209dd1b44594dd21d643520
wpt-pr: 18574
Automatic update from web-platform-tests
[css-layout-api] Re-add LayoutEdges.
This patch was created by reverting:
https://chromium-review.googlesource.com/c/chromium/src/+/1282724
And converting the tests to use promises, and switching the API to NG.
I run the patch against the mac-bots a few times to determine if I
could reproduced the flakiness which occurred initially to no avail.
Bug: 726125
Change-Id: I5f6197699977c03d3efbd4ca0926815faabee19d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761372
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689023}
--
wpt-commits: 443459a640bf144ec0ea6c7ab4b5e8bc6432f362
wpt-pr: 18570
Automatic update from web-platform-tests
Code health refactoring of animation.cc.
This patch aligns the implementation of web-animations with the spec.
Previously updates were performed via a PlayStateUpdateScope. This
class depended on an extra state (kPending) that is not to spec.
Support for microtasks is also introduced in this patch, which
addresses most of the remaining timing issues with the finished state
of an animation.
Bug: 960944
Change-Id: I62aff2254d2b5265f869415e0f763e140b460c37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1739386
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#689018}
--
wpt-commits: 521a012922a378241b46eff13e96bb3c154cb01e
wpt-pr: 18399
Automatic update from web-platform-tests
bluetooth: Implement getAvailability()
This change implements the getAvailability() method for
navigator.bluetooth as defined in the specification.
Bug: 707640
Change-Id: I9e9b3e7f8ea7f259e975f71cb6d9570e5f04b479
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1651516
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Auto-Submit: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688987}
--
wpt-commits: 4bea59463f988fe991f485b05c4fbb0fc2f00d7d
wpt-pr: 17301
Automatic update from web-platform-tests
HTML: Test default styles for 'appearance'
Part of https://github.com/whatwg/html/pull/4322
--
wpt-commits: c73e28f65eb65da982a7542d5ab71620992707ec
wpt-pr: 18591
Automatic update from web-platform-tests
HTML: COEP and ImageBitmap
Helps with https://github.com/whatwg/html/pull/4734 and #18354.
--
wpt-commits: 53c7a93cc4ba3a5fa1fe3f3358eeb9ad2ad2f0e9
wpt-pr: 18543
Automatic update from web-platform-tests
[Azure Pipelines] drop old workaround for `safaridriver --version` (#18454)
The `--version` argument is supported starting in Safari 12.1:
https://github.com/web-platform-tests/results-collection/issues/617
--
wpt-commits: a2d1acf3d4e8fe76eba70ee9b5f69dba2189819f
wpt-pr: 18454
Automatic update from web-platform-tests
[SyntheticModules] Allows for Fetching and Loading of JSON/Synthetic Modules
This is the final change required for JSON Modules to be utilized by developers.
Following the acceptance of this change, if you run chromium with the JSONModules runtime flag, the following is now valid syntax:
<script type="module">
import data from "./example.json";
</script>
This change introduces several things:
-It introduces the ability for ModuleScriptLoader to load JSON Modules
-It introduces the ability for ModuleScriptFetcher to retrieve JSON resources
-It introduces a new field to ModuleScriptCreationParams: response_mime_type_
-It introduces the JSONModules runtime flag to chromium
This change corresponds with the following V8 change:
https://chromium-review.googlesource.com/c/v8/v8/+/1761583
Bug: 967018
Change-Id: Ibcdb61659fb07047ffeead2ff4a55c450c183e43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731108
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Sam Sebree <sasebree@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#688905}
--
wpt-commits: a8a1303f3dadc7392a426ca6525e23b6114bb066
wpt-pr: 18477
Automatic update from web-platform-tests
[webnfc] Make the retval of NDEFRecord#{toText,toArrayBuffer,toJSON}() nullable
Previously, for invalid cases, toText() returns an empty string,
toJSON() returns undefined, which does not match the spec.
The spec was changed at:
https://github.com/w3c/web-nfc/pull/298
BUG=520391
Change-Id: Ia63e675c5b0032cee13802d1e5d706c35089a056
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761586
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Leon Han <leon.han@intel.com>
Cr-Commit-Position: refs/heads/master@{#688840}
--
wpt-commits: 92f88af2986da56259c26c16ec473e6961c80ad3
wpt-pr: 18556
Automatic update from web-platform-tests
bluetooth: Gen tests to standalone window tests
This change updates the Bluetooth test generator to generate the tests
as standalone window tests. This update allows the tests to be formatted
with clang-format.
The new generated tests now have the extension .https.window.js and
have been processed with `git cl format --js`
Bug: 994756
Change-Id: Ide5f1308905e3a35eccc7800391ea6e15f06741f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757881
Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688791}
--
wpt-commits: 8405bbd389242937ffc8e0c4b9c2100546d8be40
wpt-pr: 18502
Automatic update from web-platform-tests
[mojo] Add testing support to BrowserInterfaceBrokerProxy
This change adds a SetBinderForTesting() method to
BrowserInterfaceBrokerProxy and modifies MojoInterfaceInterceptor to
call this new method if a script passes a new "useBrowserInterfaceBroker"
parameter.
Also converts IdleManager to use BrowserInterfaceBrokerProxy as a use
case for overriding interface handlers in web tests.
Bug: 985118
Change-Id: I8dc3fc1c4beb2ae375a2534b03cd890ce1e3b52c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756480
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688743}
--
wpt-commits: 7b7272abd27a2c8175af33813c8bfa37450432a5
wpt-pr: 18475
Automatic update from web-platform-tests
[Azure Pipelines] reduce Edge parallel jobs from 20 to 10 (#18448)
20 was chosen to make each job of a full EdgeHTML run fast enough, but
with Chromium-based Edge each job now finishes in <1h. Each job has some
overhead, so decrease the number of jobs to 10.
--
wpt-commits: 4b0d632f645332cb02d547853a77bcaddf85ca2e
wpt-pr: 18448
Automatic update from web-platform-tests
Port backdrop-filter-interpolation.html to external/wpt
There are already some backdrop-filter-*.html, this CL picks the ones
that don't exist in wpt, and put them there.
Bug: 900581
Change-Id: Ie6cf7454fed6d3e89f31e69cbad93fdaa7bf3f55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760889
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688652}
--
wpt-commits: f6e0a7443efe2cd1254968b6d664f784fd7dc145
wpt-pr: 18546
Automatic update from web-platform-tests
WPT test to verify XRRigidTransform.matrix is SameObject
Bug: 995845
Change-Id: I830f5c9b1eac21b37f4ac534b0c862b8265265e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761437
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Auto-Submit: Jacob DeWitt <jacde@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688632}
--
wpt-commits: 5c7f3fe81b3f9a89cb17c0d237119e6bcd954858
wpt-pr: 18568
Automatic update from web-platform-tests
[fetch] Remove unnecessary use of "sub" feature
The referenced files do not use the templating syntax recognized by
WPT's "sub" feature, so they do not need to be included with the query
string parameter which enables the feature.
--
[csp] Remove unnecessary use of "sub" feature
The referenced files do not use the templating syntax recognized by
WPT's "sub" feature, so they do not need to be included with the query
string parameter which enables the feature.
--
wpt-commits: 9051fd92227f033a4941c26b1652079bac47f031, 02f4ccec3d7ed3df58207106819a8ae2a9d51b9a
wpt-pr: 18516
Automatic update from web-platform-tests
[ci] Check out master when managing tags & labels (#18393)
* [ci] Check out master when managing tags & labels
Previously, we identified a problem when attempting to run a GitHub
Action for the "pull_request" event when the underlying branch had been
deleted [1]. By migrating to the latest GitHub Action beta release [2],
we've since gained more insight into the process and more control over
its behavior.
Alter the configuration for the new "checkout" Step to consistently
check out the `master` branch. Update the Action specifier to reference
a stable release of the Action.
[1] https://github.com/web-platform-tests/wpt/issues/18286
[2] https://github.com/web-platform-tests/wpt/pull/18359
* fixup! [ci] Check out master when managing tags & labels
--
wpt-commits: 6e9bf9411482aa2d931c005ad66750414b6a5fee
wpt-pr: 18393
Automatic update from web-platform-tests
[tools] Disallow refs to some non-existent files
The Chromium infrastructure generates files which it stores in a
top-level directory named "gen". In the absence of stable documentation
for how these files must be implemented, the tests which reference them
cannot be used by other implementations.
--
wpt-commits: 4bcd7a626463b5def43c61a5940926aa2d141ff6
wpt-pr: 18509
Automatic update from web-platform-tests
Fix float-cast overflow in CompositorTransformOperations
Some functions in this class calls APIs in cc::TransformOperations,
which all take floats. But those functions provide doubles, and that
causes float-cast overflow.
This CL solves the problem by using SkDoubleToMScalar, and layout tests
are added.
Bug: 995038
Change-Id: Ic1b73c31d6090f38c7c6f342d9e953c58567604c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1761733
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688518}
--
wpt-commits: 4bf2a76e410c23a7d3d5352bf156ae08caaa6206
wpt-pr: 18555
Automatic update from web-platform-tests
Fix flakes in external/wpt/css/css-tables/html5-table-formatting-3.html
Split off from https://crrev.com/c/1751324
There is a race condition between loading all parts of the document and
running the test. This patch fixes it.
Bug: 971191
Change-Id: Ie1090416758553d8e5fa36a8ac4592cd3ce5ceb2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760912
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688439}
--
wpt-commits: 632521c58828b9ccee39c803d292b60718df1da9
wpt-pr: 18548
Automatic update from web-platform-tests
Remove invalid test cases using unitless zero length in math functions
Spec (*) explicitly disallows unitless zero length in math functions:
> Note: Because <number-token>s are always interpreted as <number>s or
> <integer>s, "unitless 0" <length>s aren’t supported in math functions.
> That is, 'width: calc(0 + 5px);' is invalid, because it’s trying to
> add a <number> to a <length>, even though both 'width: 0;' and
> 'width: 5px;' are valid.
There are some existing WPT test cases violating this, which are
removed in this patch.
(*) https://drafts.csswg.org/css-values-4/#calc-type-checking
Bug: 994359
Change-Id: Iba66c4e425ec24133c7f70bbbeca7a60d59e1883
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758734
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688401}
--
wpt-commits: 9741b2578272e28cf832c33b1a69732c1b889ba9
wpt-pr: 18515
Automatic update from web-platform-tests
[Native File System] Improve error reporting.
Don't try to force every error into a base::File::Error, instead have our own
enum and a custom error message. This should make it easier for web developers
to debug what is going on.
Also switches some DOMException constructor usage to using V8ThrowDOMException
which results in the exception messages actually being shown in dev-tools.
Bug: 971268, 991544
Change-Id: Id5128363bf5410ed08c1f4e65ebbe4b4bee93d7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1738654
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688278}
--
wpt-commits: 071a2e47b7f56ef3baf8a663bdcd30d3ace8706d
wpt-pr: 18322
Automatic update from web-platform-tests
Fix :enabled so that it does not match links
The spec [1] is clear that :enabled and :disabled should *not* match
link elements. Prior to this CL, links would match :enabled in Chrome,
but would never match :disabled. This is obviously contrary to the
spec, and it also does not match other browsers' behavior:
Firefox (68), Safari (12.1), Edge (18) and IE (11) all work according
to the spec.
Now, neither :enabled nor :disabled match links in Chrome.
[1] https://html.spec.whatwg.org/multipage/semantics-other.html#selector-enabled
Bug: 993387
Change-Id: I745a314fdac720243ebf37eed4fdcf57228cc3cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754509
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688241}
--
wpt-commits: 6bd88d385b3865a88e4d5632c26b753504e5005b
wpt-pr: 18460
Automatic update from web-platform-tests
Port filter interpolation tests to WPT
This CL moves filter-interpolation-*.html from animations/interpolation
to external/wpt/css/filter-effects/animation.
Some of the test cases in animations/interpolation/ already exist in
css/filter-effects/animation/, and hence they are not added again. We
only add the ones that aren't there yet.
Bug: 900581
Change-Id: I34b93a035885c9de12b86c22e508039bd47d0d30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760726
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688183}
--
wpt-commits: 2395a2ad79a46e3da68437d65253e2f38c59dacd
wpt-pr: 18544
Automatic update from web-platform-tests
Enable testdriver to return results to tests. (#18431)
Enable testdriver to return results to tests.
--
wpt-commits: 5fc1b5c33aa54e12d63a52f0190ab5db54feb334
wpt-pr: 18431
Automatic update from web-platform-tests
[LargestContentfulPaint] Add larger content tests
This CL adds tests where there is a bunch of content and LCP must observe the
largest (one for when image is largest, one for text).
Bug: 994414
Change-Id: I9330f238e1f8a2a8227dce7a04fd741d2dc666d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757165
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688087}
--
wpt-commits: 93e7ae091f09497c548ce60ca5026ef07c03b3bc
wpt-pr: 18472
Automatic update from web-platform-tests
Replace emoji with mathematical symbol in CSS selector ref test
Replace the snowman emoji (U+2603) with the sum sign (U+2211) in order
to avoid situations in which a color fallback font is chosen for the
emoji, which cannot be colored white and the reftest thus failing, since
the test case shows and emoji, while the reference content does not
contain any characters.
Bug: 976737
Change-Id: I342d81870418e56575700d3c0941a16544121a57
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1760304
Auto-Submit: Dominik Röttsches <drott@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688076}
--
wpt-commits: e697a7a9cbae673f3df19b603fe6c98e45057e7d
wpt-pr: 18545
Automatic update from web-platform-tests
Use get-host-info.sub.js in no-cross-origin-autofocus.sub.html (#18388)
* Use get-host-info.sub.js in no-cross-origin-autofocus.sub.html
WebKit test infrastructure doesn't support domains like www1.localhost.
This change uses get_host_info().HTTP_REMOTE_ORIGIN to choose an
appropriate cross-origin domain that works with both WPT infrastructure
as well as with WebKit's test infrastructure.
This also removes 'sub' from this file name as it's no longer needed.
--
wpt-commits: ee90e096375788bae5f83b4e7973632c9e3d48ef
wpt-pr: 18388
Automatic update from web-platform-tests
[css-writing-modes] form controls **should** match the writing-mode (#18539)
--
wpt-commits: 397d195c458423cd5ea44c62dabfe10b480fe017
wpt-pr: 18539
Automatic update from web-platform-tests
[Trusted Types] Deprecate expose param in createPolicy, add defaultPolicy.
Remove getExposedPolicy and replace it with a defaultPolicy property, which is needed internally and fixes#992031 in one go.
Bug: 992006, 992031
Change-Id: Ic5f1ae6a9001a18cb72828fd8b854453605d3c84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751723
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Commit-Queue: Stefano Sanfilippo <ssanfilippo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688056}
--
wpt-commits: a6c4ea135fdbae5a57a7282b7fc24f042890da55
wpt-pr: 18400
Automatic update from web-platform-tests
Load Ahem as web font in ex-unit-001.html (#18478)
--
wpt-commits: 82b73b315ce7ed1554e7a9b7bced66a5831e4ee5
wpt-pr: 18478
Automatic update from web-platform-tests
[performance-timeline] make sure performance entries are not clonable (#18043)
* Add a performance-timeline test making sure performance entries are not clonable
* Review comment
--
wpt-commits: a1edc496a1392559ce3a85ab811fa86b36020b28
wpt-pr: 18043
Automatic update from web-platform-tests
[webnfc] Replace NDEFRecordData#data() with multiple getters
The spec change was introduced at
https://github.com/w3c/web-nfc/pull/243.
BUG=520391
TBR=dcheng
for just adding a TODO into
third_party/blink/renderer/modules/nfc/nfc_type_converters.h
Change-Id: Iee1841352417065cdf13b08a82ac79cfd6cdb7a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755642
Commit-Queue: Leon Han <leon.han@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Cr-Commit-Position: refs/heads/master@{#688007}
--
wpt-commits: 790b9903a1d4491041c6764a59062ad11b4926a4
wpt-pr: 18449
Automatic update from web-platform-tests
SVG Text: text-anchor computed value (#18372)
The computed value of text-anchor is the specified keyword.
https://svgwg.org/svg2-draft/text.html#TextAnchorProperty
--
wpt-commits: 8561d630fb3c4ede85b33df61f91847a21c1989e
wpt-pr: 18372
Automatic update from web-platform-tests
[css-inline] Parsing line-height (#18371)
line-height is 'normal' or a number or a length-percentage.
The computed value for line-height is normal or a length.
--
wpt-commits: 11b9a030314227fa8e98ea76af85367357e86321
wpt-pr: 18371
Automatic update from web-platform-tests
Fixed nested list item crash when list-style-type:none
In quirks mode, if it's nested li, markers will occupy a whole line.
If list-style-type:none, it reasonable that no child in marker.
So remove the DCHECK and make marker_inline_size zero.
Bug: 985298
Change-Id: I54281b70064a7a568ae8a3190c0244c1140462c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749266
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687971}
--
wpt-commits: a7b9b0c0721a7ee59c58358fa0961ae7e38725fd
wpt-pr: 18528
Automatic update from web-platform-tests
[css-writing-mode] Fix reftests (#18527)
The reftests were correct with regards to size calculations,
but different writing modes align the viewport's scrollbar differently,
and unless we compensate for that, thigns won't line up and ref-tests
will fail.
--
wpt-commits: 5f31d2e63a382fcd3d703123b1c76c4e25544fec
wpt-pr: 18527
Automatic update from web-platform-tests
[css-writing-modes] Hide scrollbars that mess up with the ref-test (#18529)
Closes#14933
--
wpt-commits: 148df271ea86a8399a1952ae881665af757cc38f
wpt-pr: 18529
Automatic update from web-platform-tests
[css-writing-modes] Fix a bunch of writing mode tests (#18530)
They had incorrect paths to the font file, and refered to non existing
support file.
Plus a few other tweaks along the way.
Has anybody ever run these??? It should have been imediately obvious
they were totally broken...
--
wpt-commits: 28ec9c945002256366342c61c2d87228ae9cc872
wpt-pr: 18530
Automatic update from web-platform-tests
[css-writing-modes] Fix writing mode test (#18525)
Don't depend on the height of the content area of a inline, it's not
defined. Turn it into an inline block instead.
--
wpt-commits: 9668d6d1f46afba821258ae0951f49edf2f5747c
wpt-pr: 18525
Automatic update from web-platform-tests
[css-writing-mode] Mark replaced element writing mode effect as should, per spec (#18523)
--
wpt-commits: 82c89b43b1e5753ef970e34ed53d191d0d02f88e
wpt-pr: 18523
Automatic update from web-platform-tests
[css-writing-modes] tag feature to the right level (#18522)
--
wpt-commits: 9d60ac1665ba65a5bff686b7898428181179a36c
wpt-pr: 18522
Automatic update from web-platform-tests
Attempt to make test more stable
The animation test "correct-events-for-short-animations-with-syncbases.html"
used to be flaky. This is an attempt to fix it and also convert it to a
web platform tests.
Verified to run in FF and Chromium.
Colors were also changed reflect their usage.
Bug: 981522
Change-Id: Ieead9ca1c5ccf050ac2e886ecf630d9a9f61b6e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1732097
Auto-Submit: Edvard Thörnros <edvardt@opera.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#683542}
--
wpt-commits: 80e84e1b75ea48bef3ce4fac5fe77e4e1beb2fe7
wpt-pr: 18250
Automatic update from web-platform-tests
Clean up WPT TestExpectations for CSS animations and transitions
external/wpt/css/css-animations/Element-getAnimations.tentative.html
external/wpt/css/css-transitions/AnimationEffect-getComputedTiming.tentative.html
(turned on and baselined, code appears to have been fixed earlier)
external/wpt/css/css-transitions/CSSTransition-startTime.tentative.html
(now has same behavior reargless of when in frame the test is started)
external/wpt/css/css-transitions/properties-value-*
(fix duration to allow for CPU stress and add RAF before checking event
handlers are called, using guideline in
https://web-platform-tests.org/writing-tests/testharness-api.html#timeouts-in-tests
"Note that timeouts generally need to be a few seconds long
in order to produce stable results in all test environments.")
external/wpt/css/css-transitions/no-transition-from-ua-to-blocking-stylesheet.html
(marked flaky instead of always-fail, test sometimes passes)
REMOVE external/wpt/css/css-transitions/transitions-animatable-properties-01.html
(old and flaky duplicate of properties-value-001.html)
(serial timeouts add to close to 60s, causing harness timeout in CI)
Bug: 849975, 849927, 922970, 825262, 332189, 626703,
Change-Id: Id03994b3017ac72858dca00ee71d9b89dacbd3c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1748116
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Auto-Submit: George Steel <gtsteel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687422}
--
wpt-commits: b0545c7a1c25c1ae01b78fdd40a1d6eee1d2f0bf
wpt-pr: 18458
Automatic update from web-platform-tests
Add and run the WebGPU CTS under WPT
This adds a build of the WebGPU CTS (https://github.com/gpuweb/cts) to WPT.
(The version hash is saved in wpt/webgpu/framework/version.js.)
This also deletes the existing WebGPU web_tests, as they have been ported into the CTS.
Bug: 984818
Change-Id: I5b514a2a893b530bcc522ff131f6c653bb996210
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1707578
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Austin Eng <enga@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687932}
--
wpt-commits: 7a9cb992767821c707c922d1cae1dffe3c8613b0
wpt-pr: 18414
Automatic update from web-platform-tests
Check requested reference space against enabled XR session features
Currently we only check if the requested reference space is supported
by the device before resolving the request. With more detailed consent
this is no longer sufficient, we need to also check the underlying
feature of the reference space against which features have been enabled.
This CL also does some minor refactoring of code related to
XRSessionFeature.
Bug: 985095
Change-Id: Ibe6ecadbc6ce25c523eb4ee9d8a73560d8580df5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754275
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Commit-Queue: Will Cassella <cassew@google.com>
Cr-Commit-Position: refs/heads/master@{#687912}
--
wpt-commits: ffc0fba7d4063f0fb063b9a215dd9ef7fedefebd
wpt-pr: 18471
Automatic update from web-platform-tests
Report image url for oversized/unoptimized images
Add image url to FeaturePolicyViolationReportBody when there is a
oversized/unoptimized image feature policy violated. Previously the
fileSource field in report is set to null when policy is violated.
The effect is achieved by letting LocationReportBody represents both
a location in JavaScript source code and a location of a general
resource, e.g. a image. Because image does not have line number and
column number, these attrs are represented in optional value, and
LocationReportBody now saves pieces of actual information it needs
to generate the report, instead of a reference to SourceLocation.
Bug: 989701
Change-Id: Ibe88f07e7fa93c3d54b17380f8627221c119e106
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1741958
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Charlie Hu <chenleihu@google.com>
Cr-Commit-Position: refs/heads/master@{#687829}
--
wpt-commits: a5424fdbac9e46bee33f081b5975878c6b17496e
wpt-pr: 18337
Automatic update from web-platform-tests
Fix interpolation-testcommon.js on Firefox
The new test generation logic had some problems:
i. It produced different sets of tests on different browsers depending
on the support status. This caused difficulties comparing test results
across browsers.
ii. It produced duplicate subtest names when a 'from', 'to', or
'underlying' was not supported. Duplicate subtests are a fatal error
in WPT.
This CL fixes these problems by always generating the tests, and
asserting support in them.
It also removes the composition code, which was unused.
Bug: 900581
Change-Id: Id5617881bbf3b5f0a0b8eade5b630aa8fd65af8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758486
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687797}
--
wpt-commits: 6a439fd0334d0c7f57eb4cb58f29dbec1d026926
wpt-pr: 18508
Automatic update from web-platform-tests
Reword test names generated by interpolation-testcommon.js
Previously the generated test names were of the form:
property foo from <value> to <value> at <progress> is <actual-value>
This read weirdly when the test failed:
property foo from 0 to 1 at 0.5 is 'bananas': expected 0.5 but got 'bananas'
This CL re-words the test names to read like:
property foo from 0 to 1 at 0.5 should be 0.5: expected 0.5 but got 'bananas'
Bug: 900581
Change-Id: I77a02a24648171b3945d41cbf81d982879f4500d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758283
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687653}
--
wpt-commits: 81f8d11a1844e0881e7ad0ade1da3ac367b8d607
wpt-pr: 18507
Automatic update from web-platform-tests
Rewrite interpolation-testcommon.js
Right now the wpt/css/support/interpolation-testcommon.js is very
specific to interpolations using CSS animations. As a result, it is
used by a few tests only.
This CL rewrites the file. To be more specific, most of the code comes
from web_tests/animations/interpolation/resources/interpolation-test.js,
which runs the tests with several interpolation methods:
1. cssAnimationsInterpolation
2. cssTransitionsInterpolation
3. cssTransitionAllInterpolation
4. webAnimationsInterpolation
With this general test file, a lot of existing interpolation test can
use this. Furthermore, the intention is to move non-wpt interpolation
and composition tests to wpt using this file.
Bug: 900581
Change-Id: I1058c556932d28709bacdb08a4591c958aead937
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752103
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687264}
--
wpt-commits: 92d4abd3c9f5ba2970467b540da200739af27a1f
wpt-pr: 18402
Automatic update from web-platform-tests
WPT tests for WebXR SameObject attributes
Adding [SaveSameObject] and a reference to the attribute in
v8_private_property.h is required for the [SameObject] FrozenArray
attributes to have the expected behavior.
Attributes now covered by tests:
Navigator.xr
XRSession.{renderState,inputSources}
XRView.{projectionMatrix,transform}
XRRigidTransform.{position,orientation,inverse}
XRPose.transform
XRViewerPose.views
XRInputSource.{targetRaySpace,gripSpace,profiles}
XRWebGLLayer.framebuffer
XRSessionEvent.session
XRInputSourceEvent.{frame,inputSource}
XRInputSourcesChangeEvent.{session,added,removed}
XRReferenceSpaceEvent.{referenceSpace,transform}
Bug: 960958
Change-Id: I8582909c3e87ec0bfe05e443416708a54f606bd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752934
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Jacob DeWitt <jacde@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687756}
--
wpt-commits: b5a32d255d399ca91c55d37a0cd204a65c5c8866
wpt-pr: 18410
Automatic update from web-platform-tests
Composite color values on the worklet thread
Follow up to:
https://chromium-review.googlesource.com/c/chromium/src/+/1614120
(Allows number values to be composited on the worklet thread)
--and--
https://chromium-review.googlesource.com/c/chromium/src/+/1698667
(Allows creation of keyframe model for color values on compositor)
This CL adds similar functionality as that used for number types to update
color values on the compositor. New classes CrossThreadColorValue and
CSSUnsupportedColorValue were created for CSSPaintValue::GetImage to identify
color valued custom properties as compositable.
Bug: 883721
Change-Id: Ib8c26e5c6c6077b21288de3156fa35cc6e02435d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713747
Commit-Queue: Adam Raine <asraine@google.com>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687702}
--
wpt-commits: 7c42039e0623abaae97105214e9968c92272f15d
wpt-pr: 18013
Automatic update from web-platform-tests
[ci] Correct file management in tests
The `mkstemp` function creates a file and opens that file [1], so these
tests erroneously attempted to delete an open file. This mistake was not
identified during development or automated testing because it only leads
to a runtime exception in Windows environments [2].
Refactor the helper function to close the file immediately after writing
to it.
[1] > `mkstemp()` returns a tuple containing an OS-level handle to an
> open file (as would be returned by `os.open()`) and the absolute
> pathname of that file, in that order.
https://docs.python.org/2/library/tempfile.html#tempfile.mkstemp
[2] > On Windows, attempting to remove a file that is in use causes an
> exception to be raised; on Unix, the directory entry is removed
> but the storage allocated to the file is not made available until
> the original file is no longer in use.
https://docs.python.org/2/library/os.html#os.remove
--
wpt-commits: 7f35d6cf8b99b613d14786ce990a815c805a1d74
wpt-pr: 18341
Automatic update from web-platform-tests
[IntersectionObserver] Use inclusive intersect with remote frame parent
The rest of the MapToVisualRectInAncestorSpace code will do inclusive
intersections when the kEdgeInclusive flag is set, as required by
IntersectionObserver to correctly handle zero-area targets.
This patch adds coverage for this situation to the existing WPT for
cross-origin IntersectionObserver. Since the bug only affects
IntersectionObserver running inside an OOPIF, this also updates the
test to force the iframe into a different domain, rather than just
using the sandbox attribute (which is not sufficient to trigger OOPIF).
BUG=978759
Change-Id: I7dbe52d2f3e39e029fed3dda5be31190c593a1e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754595
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Stefan Zager <szager@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687361}
--
wpt-commits: 504feb2f721bab75aa597a8082e06700874b84d6
wpt-pr: 18443
Re-enabling the disabled manifest `testing/web-platform/meta/media-source/__dir__.ini` for windows10-aarch64 since the tests now pass.
Differential Revision: https://phabricator.services.mozilla.com/D43714
--HG--
extra : moz-landing-system : lando
See https://github.com/mathml-refresh/mathml/issues/5#issuecomment-475506856
and https://groups.google.com/forum/#!topic/mozilla.dev.platform/kl5c87mBlO0
This patch introduces a new preference
mathml.deprecated_style_attributes.disabled in order to disable legacy support
for attributes background, color, fontfamily, fontsize, fontstyle and
fontweight. Note that xlink:href will be handled separately in bug 1575870.
* A new counter and deprecation message is introduced for these attributes.
In nsMathMLElement, the old WarnDeprecated calls are replaced with a single
call to WarnOnceAbout for the deprecate attributes. Notice that for some
reason, the color attribute used to send warning in both ParseAttribute and
MapMathMLAttributesInto.
* sMtableStyles is removed and replaced with a simple comparison.
* sMathML3Attributes is split into two tables: one for script attributes which
will be handled in bug 1548471 and one for style attributes, handled here.
The attributes in this second table is now ignored when the feature flag is
disabled.
* test_bug553917.html is updated so that it no longer checks the old warning
messages for these attributes. New warning messages have been verified
manually.
* Reftests checking support for these attributes are run with the support
enabled.
* Finally, WPT tests are run with the support disabled and a new test
is added to verify that these attributes are no longer mapped to CSS.
Differential Revision: https://phabricator.services.mozilla.com/D43111
--HG--
extra : moz-landing-system : lando
We can't parse files where the key-value pairs are after the subtest
data, so ensure that we add it before. Also fix a bug when metadata is
added on one side of the merge but unchanged on the other; we were
accidentially inserting the entire test rather than just the expected
value.
Differential Revision: https://phabricator.services.mozilla.com/D43658
--HG--
extra : moz-landing-system : lando
The main motivation here is to get these subsections out of the main index.
While changing the heading to an 'h2' or lower would suffice, I opted to remove
them entirely. I did this because the links in this section is for the overall
global documentation. E.g, the "Indices and tables" section under /tools/lint,
has nothing to do with linting.
It is still possible to access the index and search page from the root:
https://firefox-source-docs.mozilla.org/#indices-and-tables
Differential Revision: https://phabricator.services.mozilla.com/D43653
--HG--
extra : moz-landing-system : lando
For tests with ids like foo/bar?baz/foobar we were incorrectly setting the manifest test_id
to foobar rather than bar?baz/foobar. Fix this by determining the length of the path up to
the last / and trimming that off the front of the test id. This approach avoids
reserializing the url.
Differential Revision: https://phabricator.services.mozilla.com/D43579
--HG--
extra : moz-landing-system : lando
Before this patch, it was unclear who was responsible for checking deviceId and
groupId constraints for devices. MediaManager was doing it through one path for
getUserMedia, with the help of the devices, as part of selecting the
best-fitting device. However, Reconfigure() took another path where the regular
backends for camera and microphone were implemented correctly, but fake devices
were left out so automated tests for applyConstraints were failing.
This patch lifts the responsibility for checking deviceId and groupId
constraints out of the MediaEngineSources into MediaDevice, which already is the
owner of the anonymized ids that MediaEngineSources are unaware of.
This makes constraints checking a two-staged approached where deviceId and
groupid goes first. If they satisfy the constraints, the underlying device is
queried for whether the constraints fit.
As a bonus, this unclutters a lot of the MediaEngineSource interface.
Differential Revision: https://phabricator.services.mozilla.com/D40834
--HG--
extra : moz-landing-system : lando
This by default creates an empty js file, but does support the
--long-timeout flag.
Differential Revision: https://phabricator.services.mozilla.com/D39888
--HG--
extra : moz-landing-system : lando
Ensure that if we try to create a mochitest of unsupported file type we return a
useful error
Differential Revision: https://phabricator.services.mozilla.com/D38224
--HG--
extra : moz-landing-system : lando
This patch fixes an existing bug with this clean up.
Except `HTMLEditRules::MoveBlock()`, `GetListActionNodes()` is called after
calling `SplitInlinesAndCollectEditTargetNodesInExtendedSelectionRanges()`
or `CollectEditTargetNodesInExtendedSelectionRanges()` **with**
`EditSubAction::eCreateOrChangeList`. I think that `HTMLEditRules::MoveBlock()`
using the edit sub-action is a simple mistake. Perhaps, it should be
`EditSubAction::eCreateOrRemvoeBlock`. However, I'm not 100% sure because
`HTMLEditor::CollectEditTargetNodes()` does special handling for
`EditSubAction::eCreateOrRemvoeBlock` but not so for
`EditSubAction::eCreateOrChangeList`. The behavior of difference between
those edit sub-actions are only here. Therefore, this patch creates new
`EditSubAction` `eMergeBlockContents` for `MoveBlock()`.
Then, this patch makes `HTMLEditor::CollectEditTargetNodes()` handle
`EditSubAction::eCreateOrChangeList` insead of `GetListActionNodes()`.
This causes one logic change in `SplitInlinesAndCollectEditTargetNodes()`.
It calls `MaybeSplitElementsAtEveryBRElement()` after `CollectEditTargetNodes()`
so that this change makes calling `MaybeSplitElementsAtEveryBRElement()` at
last. According to my tests, new behavior must be expected since `<br>`
elements outside and in `<table>` should be handled consistently. Therefore,
this patch adds some simple testcases into WPT.
Differential Revision: https://phabricator.services.mozilla.com/D43190
--HG--
extra : moz-landing-system : lando
See https://github.com/w3c/csswg-drafts/issues/4239
This fixes what is in my opinion one of the biggest issues of scroll anchoring
as specified / currently implemented.
It's trivial to flush layout on a scroll handler and create scroll adjustments,
which in turn would trigger other scroll events to be fired. This situation,
which is what has happened in most of the scroll anchoring regressions I've
fixed, at best gets pages to get stuck in an infinite CPU loop. At worst, it
causes scrolling to be unusable because the page keeps reacting to scroll
events.
An alternative, slightly more elegant but not clear to me if 100% implementable
approach would be bug 1529702.
This should enormously reduce the need for scroll anchoring suppression
triggers[1], I'd think, which in turn would allow me to investigate removing
some of that complexity.
https://drafts.csswg.org/css-scroll-anchoring/#suppression-triggers
The setup to set / unset the boolean is a bit awkward but I couldn't come up
with anything better.
Differential Revision: https://phabricator.services.mozilla.com/D43233
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
[Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445)
As it is, it's only possible to run both of them:
https://github.com/web-platform-tests/wpt/issues/17342#issuecomment-521534275
This also renames the Edge Dev job and artifacts so that Edge stable can
later be added without further renaming.
--
wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4
wpt-pr: 18445
Automatic update from web-platform-tests
Create new list for paced animation values
SVGAnimationElement::calculateKeyTimesForCalcModePaced() used to
overwrite the data passed in by the user. This commit fixes the
issue and there are now two lists stored, one with the user data
and one with the key times for paced.
This is a bug fix and should only affect SVGAnimationElements,
there will be an increase in memory usage, especially for animation
intensive scenes. Can be avoided by changing to a CPU heavy approach,
but this will probably be more energy efficient for mobile devices.
Bug: 231525
Change-Id: Ief9bbb8c6d1133d0041ad2c8f5a3d63f9ddcde90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1757825
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Edvard Thörnros <edvardt@opera.com>
Cr-Commit-Position: refs/heads/master@{#687651}
--
wpt-commits: 6ee27431c3352f158b198de70c0816bf1b485a05
wpt-pr: 18491