Automatic update from web-platform-tests
Remove __future__ imports in tools/
The imports being removed are:
- absolute_import, mandatory since 3.0
- division, mandatory since 3.0
- print_function, mandatory since 3.0
- unicode_literals, mandatory since 3.0
- with_statement, mandatory since 2.6
See https://docs.python.org/3/library/__future__.html for details.
--
wpt-commits: b494ad81e9de67691707d24b74116d868f410813
wpt-pr: 29211
Automatic update from web-platform-tests
Implement MediaCapabilities API encodingInfo for WebRTC (#29186)
"webrtc" was recently added as an MediaEncodingType to the
MediaCapabilities API, see
https://w3c.github.io/media-capabilities/
"webrtc" replaces the deprecated encoding type "transmission".
This CL implements support for responding to supported and powerEfficient.
smooth is currently hardcoded to be true given that the configuration
is supported.
The feature is implemented behind the blink runtime enabled flag
MediaCapabilitiesWebRtc
Bug: chromium:1187565
Change-Id: I98d8d971304194d93aa436b8821ea665dfdab9f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2932438
Reviewed-by: Justin Novosad <junov@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Johannes Kron <kron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#890184}
Co-authored-by: Johannes Kron <kron@chromium.org>
--
wpt-commits: 47e838220e6e97af5d09df9931879f5b3cc4f8aa
wpt-pr: 29186
Automatic update from web-platform-tests
Do not propagate body styles when html root or body is contained
Per resolution in [1]. Added behind a flag since this is a web facing
change which needs an intent to ship.
[1] https://github.com/w3c/csswg-drafts/issues/5913
Bug: 1215265
Change-Id: I50f142245cdb55b422f8a6f3d9690444bf3648aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2897247
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#890175}
--
wpt-commits: cf84beafec2055bc7a7ba01fcaecd4f528f2f1dc
wpt-pr: 29165
Automatic update from web-platform-tests
webcodecs: Limit the number of video frames encoded at once
Bug: 1215807, 1123856
Change-Id: Ic672a76733c99fcdbba81d0a699d293dd29a123e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2945732
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#890152}
--
wpt-commits: f333d095eab8408d15593c240240125ffe9dabbf
wpt-pr: 29280
Automatic update from web-platform-tests
Make PostLayout no-op while side effects are disabled
|PostLayout| is to get the latest fragment for the node.
However, while side effects are disabled (added in r889851
crrev.com/c/2940587), new fragments are not associated with
the owner |LayoutBox|.
This patch makes |PostLayout| no-op in that case.
Bug: 1216596
Change-Id: I82fcb9055b26be27cfde383d599a0b36ac0f17bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2944448
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#890124}
--
wpt-commits: 6085f658ace31a3c962a69d5128cc7e66d79cbb9
wpt-pr: 29263
Automatic update from web-platform-tests
Treat urn:uuid resources as http resources for ResourceTiming purposes.
Change the resource filtering behaviour so urn:uuid resources served
from the WebBundle are treated as http resources for ResourceTiming
purposes. Also adding a WPT for this behaviour.
Bug: 1182555
Change-Id: If46fe837f463df59ae47762b373f9db91f9db3e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2931538
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Miras Myrzakerey <myrzakereyms@google.com>
Cr-Commit-Position: refs/heads/master@{#890110}
--
wpt-commits: c0fff013dd92a99fb8fde60bfd9a9c699cc16e03
wpt-pr: 29181
Automatic update from web-platform-tests
When detaching an AXObject, remove it from all ancestor child lists
When adding children, we recurse through unincluded children and
add their children. Therefore, an ancestor can cache AX children
that are actually not direct children.
For example, for this structure,
A (included)->B (unincluded)->C (unincluded)->D (included):
- A, B and C will all have D in their list of children
- No unincluded object is in an ancestor's list of children
- D's parent is C, C's parent is B, and B's parent is A.
There is a rule when adding children that detached children cannot
be reached. Children are no longer cleared while adding children,
because of crashes, e.g. while force loading inline text boxes.
Therefore, when detaching an AXObject, we must clear cached
children for every ancestor up to the first included ancestor.
Bug: 1211394
Change-Id: Id723b610928308dfbbe2f373d53a4c2be701e30f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2941402
Reviewed-by: Daniel Libby <dlibby@microsoft.com>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889930}
--
wpt-commits: b595fca32589a43797579ba9fc6b879fe697a602
wpt-pr: 29243
Automatic update from web-platform-tests
[SVG] Don't pass negative attribute values to ComputedStyle
width/height attributes on topmost SVG elements are presentation
attributes so their values are expected to show up in
ComputedStyle.Width()/Height(). But attributes can be negative while CSS
lengths cannot. This patch prevents negative SVG attribute values from
being passed to CSS.
Bug: 1207590
Change-Id: I11af6c9079ace385cd5b19ade34211eb1aa6cb5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2936183
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889915}
--
wpt-commits: 2db17ab1be2ccd97df6171e296ad8a636bb113e9
wpt-pr: 29208
Automatic update from web-platform-tests
Fix a corner case crash when removing iframe document
See the included test. It is possible that event listeners get called
on a node whose document has been detached. In that case, don't try
to call event listeners.
Fixed: 1210480
Change-Id: I63ce7706243abd133aa6ed6219484995140e2c9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2939730
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889901}
--
wpt-commits: 7cdb63520ff08a92b5bbc49aca80dd8522421351
wpt-pr: 29268
Automatic update from web-platform-tests
[TablesNG] Fix paint phase of collapsed borders.
As above currently they are painting in the foreground phase when they
should be in the background phase.
Bug: 1217146
Change-Id: I135d61caa5e6822226d7f87c32b3474da15d17b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2941972
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889870}
--
wpt-commits: bace9b040173f0cfd12ddd1604997df3ba99b497
wpt-pr: 29267
Automatic update from web-platform-tests
Add test for out of head <meta name="referrer"> elements
--
wpt-commits: cd9e10befb1edcbb7d04e06ef7255e56c72c07e8
wpt-pr: 29275
Automatic update from web-platform-tests
Move capturing-snap-positions.html into css/css-scroll-snap/ (#29013)
This is from https://github.com/web-platform-tests/wpt/pull/27247.
--
wpt-commits: 23aa68617363d0524e4c0a721be3101b4500e4ff
wpt-pr: 29013
Automatic update from web-platform-tests
Keep 3D points in a quad coplanar when clamping them to reasonable values.
This is necessary because sending quads that aren't coplanar (or,
really, within rounding error of being coplanar) to the plane splitting
code (DrawPolygon::SplitPolygon) confuses the plane splitting code (for
good reason) and leads to incorrect splits that can leave some pieces
undrawn.
There are two major pieces to this change:
* First, it changes the code that finds the appropriate transition
point on an edge that passes between positive and negative w (as part
of eliminating the parts of the quad with negative w) to choose a
point that is appropriately-clamped rather than nearly-infinite.
* Second, it adds new clamping code to clamp any remaining out-of-range
values (or the results of the first part if rounding puts them
slightly out of range) to clamp by moving them inwards within the
plane. Before doing this, if needed, it may also (if none of the
plane is close enough to the origin at x=0 and y=0) to move z
coordinates on all of the points in the plane a bit closer to z=0.
Fixed: 1202695
Change-Id: I82b9510710439a81135559ee7d686480cd1f30ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2877604
Reviewed-by: Robert Flack <flackr@chromium.org>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889969}
--
wpt-commits: 633c38f3db65fa129120448d48918cad383c4e54
wpt-pr: 29110
Automatic update from web-platform-tests
Modify WPTs to check for standards mode documents
The [1] PR will change the standard so that media and
text documents are in standard (no quirks) mode. This
CL updates the tests accordingly.
Chromium already made this change in code in Sept 2020
(see CLs on crbug.com/1131185) and found no compat
issues.
[1] https://github.com/whatwg/html/pull/6745
Bug: 1131185
Change-Id: Ie5f5ae5eb802008bf27794c152620bdcc9948ba2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2945338
Auto-Submit: Mason Freed <masonf@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889933}
--
wpt-commits: ce674ef72677377bc04c08c314a753c9274e3982
wpt-pr: 29269
Automatic update from web-platform-tests
[COOP] Add regression test for bug 1216244
See https://crbug.com/1216244.
When a window navigate elsewhere using a combinaison of document.write
and a meta refresh header, the openee/opener relationship must hold when
the opener has COOP:same-origin-allow-popups.
This has been broken in M90 by:
https://chromium-review.googlesource.com/c/chromium/src/+/2659421
and fixed by reverting it.
This patch adds a regression test to avoid future regressions.
R: titouan@chromium.org
CC: japhet@chromium.org
CC: clamy@chromium.org
Fixed: 1216244
Change-Id: I3362947be08f0b5b02743afa49f20a335a437d3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2940001
Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#889705}
--
wpt-commits: 0f963db061411bc9e578aab01355cc69573a2a52
wpt-pr: 29214
Automatic update from web-platform-tests
chore: make exposed_in matcher work in Deno (#29239)
Previously exposed_in checked if `"document" in self` to determine if
we are on the main thread. Deno does not have a `document` so this doe
not work there. Instead we now check for `'Window' in self`.
--
wpt-commits: 2d105dc373a4457c1bb555161832460ae1107d59
wpt-pr: 29239
Automatic update from web-platform-tests
chore: update webidl2.js to v24.1.1 (#29238)
Pulls in https://github.com/w3c/webidl2.js/pull/579 for Deno.
--
wpt-commits: 0c0ec487597b6e83f94089ddcef6df854239b10d
wpt-pr: 29238
This is slightly complicated by the fact that the editor code wants to be able
to set this from the content process, so we really need separate
BrowsingContext and WindowContext flags, the latter of which can be set by the
owning process.
Differential Revision: https://phabricator.services.mozilla.com/D114899
Extension.jsm, ContextualIdentityService.jsm and GeckoViewConsole.jsm still reference browser.properties.
Depends on D117622
Differential Revision: https://phabricator.services.mozilla.com/D117623
This commit updates the memory runtime code to generally
use pages instead of byte lengths. In terms of runtime
structures: limits are in pages, memory object max
size is in pages, memory object current size is in bytes,
and the TlsData bounds check limit is in bytes.
This code is tricky, so I've added a 'wasm::Pages' typed unit
to catch cases of type confusion and make intent clearer. I've
also tried to add asserts, comments, and rename unclear variables.
The array buffers (shared and non-shared) still track their
length in bytes (this is best as the byte length is needed for
warm code in memory.copy/fill), but now the 'maximum' field is
stored in pages. This allows maximum values that would overflow
byte lengths with memory64 to be represented.
The array buffer interface for wasm now generally only uses
pages, and most code internal operates on pages. There are
still a few cases where byte lengths are required and we add
code or assert that converting from pages to byte lengths is
valid.
Differential Revision: https://phabricator.services.mozilla.com/D116652
Add accessor methods and tweak code to reduce users
that depend on MemoryDesc exposing raw byte lengths for
the initial and maximum fields.
Additionally, MemoryKind is added to MemoryDesc so we can start
asserting in code that assumes Memory32.
Differential Revision: https://phabricator.services.mozilla.com/D116651
This is a clean-up to add a first-class MemoryDesc object,
replacing the ad-hoc methods of describing a module's memory.
Temporarily, this is just a Limits (in pages) and the byte length converted
versions of Limits. The byte length fields will be dropped later.
asm.js used to rely heavily on mutating the ad-hoc representation on
ModuleEnvironment. This commit adds a ModuleEnvironmentShared::Memory
struct for simulating the old way of mutating ModuleEnvironment.
Differential Revision: https://phabricator.services.mozilla.com/D116650
We are going to use the mEffectsInfo's mVisibleRect as a displayport base for
OOP iframe's root scroller and we don't want the displayport base if it hasn't
been arrived from the parent content, to do that, we need to tell the difference
whether the iframe was painted as empty or hasn't been painted.
Differential Revision: https://phabricator.services.mozilla.com/D116575
vqmovn_u16 is very different semantically then _mm_packus_epi16. _mm_packus_epi16 treats the input as signed 16-bit integers and narrows to unsigned 8-bit.
vqmovn_u16, however, is an unsigned to unsigned narrow. vqmovun_s16 does what we actually need here, which is to treated the input as signed 16-bit and narrow to unsigned 8-bit.
Differential Revision: https://phabricator.services.mozilla.com/D117705
This test formerly had a win7-specific fuzzy annotation. I'm generalizing that
annotation to include all Windows versions, since Windows 10 has had similar
fuzzy failures; and I'm also merging with the adjacent "gtkWidget" fuzzy
annotation, since it's got exactly the same fuzzy thresholds.
Differential Revision: https://phabricator.services.mozilla.com/D117719