Automatic update from web-platform-tests
Bump urllib3[secure] from 1.26.5 to 1.26.6 in /tools (#29507)
--
wpt-commits: 9e11b662c7204cf561801314bec46ec36220ebc6
wpt-pr: 29507
`TextControlState` is alive during reframing, but `TextEditor` is not so.
Therefore, `TextControlState` should take the `PasswordMaskData` before
`TextEditor` is destroyed. And if `TextEditor` is recreated, and the value
hasn't been modified, unmasked range should be restored in the new editor.
Depends on D118757
Differential Revision: https://phabricator.services.mozilla.com/D118758
During a `TextControlState` alive, `PasswordMaskData` should be alive too.
Otherwise, we cannot keep unmasked range at reframing.
Depends on D118756
Differential Revision: https://phabricator.services.mozilla.com/D118757
The intermittent failure is caused by unexpected global reflow during the test.
If `<input type="password">` is reframed, `TextEditor` instance is recreated.
Then, the unmasked range of the editor stored by `TextEditor` is also lost.
Therefore, unmasked range is randomly lost by unexpected reflow.
If the global reflow is occurred by font list update etc which are not expected
by users, unmasked password field is unexpectedly masked. So, this is a real
bug of `TextEditor`.
So, unmasked range needs to be stored outside `TextEditor` for making its
lifetime longer than `TextEditor`. For doing it, first, `TextEditor` should
access password mask data via a pointer to a struct. Then, fortunately,
we need to allocate it only when the `TextEditor` is a password editor.
Depends on D118755
Differential Revision: https://phabricator.services.mozilla.com/D118756
Automatic update from web-platform-tests
Throw error if connections are made between different contexts
The WebAudio spec says that if a node is connected/disconnected to
another node or AudioParam that belongs to a different context, then
an InvalidStateError must be thrown.[1][2] Add a check for this and throw
the required error.
This also requires a fix to audit.js which wasn't properly catching
DOM exceptions of the wrong type.
Finally, ctor-channelsplitter.html needed to be updated to specify the
error type because of the change in audit.js.
Also adds new WPT test, different-contexts.html, to more thoroughly test
connect/disconnects to different contexts.
[1] https://webaudio.github.io/web-audio-api/#dom-audionode-connect-destinationnode-output-input-destinationnode
[2] https://webaudio.github.io/web-audio-api/#dom-audionode-disconnect-destinationnode-destinationnode
Bug: 1206927
Change-Id: I320425268d1fd243e347dd36c79172c69dcc9733
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2965479
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#895851}
--
wpt-commits: c632c827c408d77c09f63cba01f3ad526588c67f
wpt-pr: 29400
Automatic update from web-platform-tests
Update scrollbar-gutter to new version of the spec
Update the implementation of scrollbar-gutter to match the new spec:
https://drafts.csswg.org/css-overflow-4/#scrollbar-gutter-property
The syntax is is simplified to: auto | stable && mirror?
The "stable" value also applies when overflow is "hidden".
The "always" and "force" keywords have been removed.
The "both" keyword has been renamed to "mirror".
This CL updates all affected tests to match the new spec.
Bug: 710214
Change-Id: I4a22a1abc821fa8982759cee3b69089f75dce229
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2970809
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Felipe Erias <felipeerias@igalia.com>
Cr-Commit-Position: refs/heads/master@{#896301}
--
wpt-commits: 88543e2b64be5702179549bd94983613634c187a
wpt-pr: 29451
Automatic update from web-platform-tests
[css-grid] Fix grid-areas-overflowing-grid-container-{004,005} tests.
These two tests were incorrect, applied a fix where the non-scrollbar
axis has a grid-template of 100% instead of 100px.
Bug: 1108097
Change-Id: I8027714bea7bf81c6e968c97231c6f1252cbd787
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2988294
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#896219}
--
wpt-commits: ff358187185df64f9c9faf2fdc20b6fa16c74fb6
wpt-pr: 29502
Automatic update from web-platform-tests
[webcodecs] Use network byte order for format names.
This CL renames the WebCodecs RGB formats to be named in network byte
order. It also adds 'I420A' to distinguish 3 vs 4 plane YUV.
Bug: 1204349
Change-Id: Id60987cf2f115bd546fea2b84b54ff6f61fd1b5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2946350
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#896215}
--
wpt-commits: 772ff3cf390b507d171330caacefcbe4654df476
wpt-pr: 29291
Automatic update from web-platform-tests
Address clusterfuzz errors with image maps and a11y
Ignore <img usemap> inside of any <map>, in order to avoid potential
loops in the tree structure.
Fixed: 1221999
Change-Id: Ib5a112e1bc7f39d2a702fa39dedc4145d29d54b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2986380
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Auto-Submit: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#896160}
--
wpt-commits: 0d89db41ff09f470ca0a645c31455578a5100ab5
wpt-pr: 29492
Automatic update from web-platform-tests
Allow navigating parent and child during history traversal
This is a behavior we've wanted for years, but which could cause
serious breakage in the absence of FrameNavigationEntries being
shared across multiple NavigationEntries. That was implemented in
https://chromium-review.googlesource.com/c/chromium/src/+/2910529
Normally, when sharing FrameNavigationEntries, we "fork" the entry
when it is updated due to navigating cross-document (unless reloading
the same url). However, this does not work well when navigating away
from an initial empty document, because we want to hide any empty
documents at the start of an iframe's lifetime. In particular, in the
case where an iframe and the main frame racily navigate, we can end
up with an initial empty document's FNE shared across 2 different
NavigationEntries. It is important that when the first real navigation
takes place, we update the existing entry rather than fork,
so that the initial empty document is overwritten in both places.
Therefore, add a special case in
NavigationControllerImpl::RendererDidNavigateAutoSubrame, to ensure
an initial empty document is always updated rather than replaced.
Bug: 542299, 598043
Change-Id: I4113cbbcb8dd5d5065e88ad8f5761acc09847543
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2953549
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#896133}
--
wpt-commits: 3b1c1631085e7af5f48d0e38c6a84410c2a9e96c
wpt-pr: 29471
Automatic update from web-platform-tests
Re-add style containment to contain:strict and contain:content
This change was resolved upon by the CSSWG.
Intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/oMVBKemrTDQ
Fixed: 1220736
Change-Id: Ia73d9a3af4373f803cc9e257bd8565104ff5359a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2965549
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#896107}
--
wpt-commits: 90c83d9317172d8ccb5a03e852ad78669db37a19
wpt-pr: 29455
Automatic update from web-platform-tests
[Scroll Unif.] Chain to local parent frame in main-thread hit test.
If the scroll hits an iframe that isn't scrollable for some reason, we
need to look for a scrollable container in the parent frame.
Bug: 1223032
Change-Id: I4c1fd69712532802ec120821441d443087bed3c1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2983821
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#896035}
--
wpt-commits: 1dedf64cf9556cbc34ad771d1dc1f5371861be18
wpt-pr: 29478
Automatic update from web-platform-tests
URL: pathname setter should not erase path-only URL paths
For https://github.com/whatwg/url/pull/582.
Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
--
wpt-commits: 77d54aa9e0405f737987b59331f3584e3e1c26f9
wpt-pr: 27720
Automatic update from web-platform-tests
[GridNG] Fix computation of 'fr' size in ExpandFlexibleTracks
Fixing a bug where the algorithm for finding the size of an 'fr' unit
was not resolving correctly when the grid had '0fr' track definitions.
This happened because "base size / flex factor" ratio in such case
became indefinite and was not properly handled.
This change excludes sets with a flex factor of 0 from the algorithm
and assumes that those tracks would have a fixed base size.
Bug: 1222867
Change-Id: I492d3d5a5874b74d44b830b32dc6c51568f95b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2986908
Commit-Queue: Ethan Jimenez <ethavar@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Kurt Catti-Schmidt <kschmi@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#895969}
--
wpt-commits: 60a9644afaaadba34418bbbd115ad828146619c5
wpt-pr: 29493
Automatic update from web-platform-tests
Add test case for text-transform uppercase and selection
This is just a test to show the effects of https://crbug.com/750990
when selecting text that has changed the number of characters
due to text-transform.
BUG=750990
TEST=external/wpt/css/css-text/text-transform/text-transform-upperlower-105.html
Change-Id: If7cbde1f1e480c98d0ad4586f93729cbca1d0d1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2987819
Commit-Queue: Manuel Rego <rego@igalia.com>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/master@{#895958}
--
wpt-commits: c660b404f53e49f4ce2932b7ccf39188082dc2da
wpt-pr: 29497
Automatic update from web-platform-tests
Change documentation to point at Matrix rather than IRC. (#29484)
--
wpt-commits: 751ba879160535e949456da20e1a6221b7c0d55e
wpt-pr: 29484
Automatic update from web-platform-tests
Streams: read with fixed endianness
In some tests for readable byte streams, we pass a Uint16Array to
reader.read(view), then write into it as a Uint8Array and finally read
the results back as a Uint16Array. However, Uint16Array uses the
platform byte order, whereas these tests assume that it's always in
little-endian order.
Node.js has also started implementing the Streams API
(nodejs/node#39062), and they also run on big-endian platforms. To
support this, the tests must be independent of the platform byte
order. Use a DataView to achieve this.
--
wpt-commits: afcacf21caaf9d0efd6601833077e04af9b4dee1
wpt-pr: 29488
Automatic update from web-platform-tests
Fix under-invalidation of collapsed border on removal of a table cell
Collapsed borders need repaint when grid structure changes. We need to
invalidate the table which paints collapsed borders.
Bug: 1221182
Change-Id: I82d38f042602d134e9c148a997d3e06b76668074
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2983733
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#895774}
--
wpt-commits: 1ab2113bafa2171064dc20127fbc3fea984bc98d
wpt-pr: 29469
Automatic update from web-platform-tests
Revert "Auto-expand details elements for find-in-page"
This reverts commit 02660fd7a1202f9ff9a615cb7e83af6075d7a93d.
Reason for revert: crbug.com/1221221
Clusterfuzz found a use-after-poison caused by this CL. The root cause is observable in the debug build.
Original change's description:
> Auto-expand details elements for find-in-page
>
> This patch makes <details> expand automatically in response to
> find-in-page right before find-in-page tries to scroll to content inside
> a closed <details> element.
>
> This is gated behind the experimental web platform features flag.
>
> I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/ovNo2kFAgnE
>
> Bug: 1058732, 1185950
> Change-Id: Ie957d2835ce90e4c777341e0518c91442990fded
> Cq-Do-Not-Cancel-Tryjobs: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2702377
> Commit-Queue: Joey Arhar <jarhar@chromium.org>
> Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#893228}
Bug: 1058732, 1185950, 1221221
Change-Id: Iea6996494edbe4d803e956546f16caed8179b7cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2985840
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#895762}
--
wpt-commits: 1401e14cefbece7176892322f33193356362041e
wpt-pr: 29483
Automatic update from web-platform-tests
Test replace vs. push before/during load and pageshow
Follows whatwg/html#6714.
--
wpt-commits: c1bb1fdaa510c14d31ca8307f4778b015a6bb30d
wpt-pr: 28480