Automatic update from web-platform-tests
Handle all `white-space` values when intrinsically sizing an IFC
There were various cases like `text-wrap-mode: nowrap` and
`white-space-collapse: break-spaces` that weren't handled well.
Fixes#33335
flexbox_flex-formatting-interop.html fails now because we don't support
`table-layout: fixed`.
Signed-off-by: Oriol Brufau <obrufau@igalia.com>
--
wpt-commits: 15415f53267f1375901637b800ceba073724aecc
wpt-pr: 48041
Automatic update from web-platform-tests
Trigger Safari & Safari Technology Preview runs after epochs
GitHub Actions doesn't create new workflow runs for events dispatched
from a workflow (or, pedantically, using the provided GITHUB_TOKEN),
thus we need to manually trigger the Safari and Safari Technology
Preview workflows after the epochs workflow has run.
While we're at it, we should allow these workflows to be manually run
via workflow_dispatch.
--
wpt-commits: 24199363d2a25d3c1b562c0065ed214cb59ca49b
wpt-pr: 48087
Automatic update from web-platform-tests
[Masonry] Introduce parsing for masonry-slack
This CL introduces the parsing for css masonry property:
masonry-slack
https://tabatkins.github.io/specs/css-masonry/#propdef-masonry-slack
This is part of: https://chromestatus.com/feature/5149560434589696
The properties are behind the CSSMasonryLayout feature flag.
Bug: 343257585
Change-Id: If6759bf828c8e8d52e0e307e3e9642f9fbfc1c1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5801223
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Reviewed-by: Ethan Jimenez <ethavar@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1354110}
--
wpt-commits: b59254693ac30adf72b4aabf4466a7fb3aeb9f45
wpt-pr: 47796
Automatic update from web-platform-tests
IDB WPTs: Extend 2 more cursor continue() index WPTs to run on workers
These IndexedDB WPTs currently only run in a window environment. This
change moves them into the idbcursor_continue_index.any.js file. This
extends them to also run in dedicated, shared, and service worker
environments.
Bug: 41455766
Change-Id: I25c2da4f7a4a3a79469d85cd4b3c69fff2657359
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5852860
Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Rahul Singh <rahsin@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1354089}
--
wpt-commits: d35f9879ca483cc3ddf9706de94a9ee29959f039
wpt-pr: 48105
Automatic update from web-platform-tests
[css-flex] Change test expectations to be web-compatible
Current expectations for a test are what the spec dictates but no one
implements (except Servo, notably) because it has been found to be not
web compatible.
Relevant spec discussions ongoing at
https://github.com/w3c/csswg-drafts/issues/8884
Change-Id: I18ac3c1b1c03db960ef187736bc781370e33a577
Fixed: 361124377
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5855162
Auto-Submit: David Grogan <dgrogan@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354066}
--
wpt-commits: d0ebe58a84aa9d588bd6b49ae0210308fd6c5743
wpt-pr: 48104
Automatic update from web-platform-tests
[Editing] Inline and Text Control elements should stay open without
placeholder
The logic for determining whether the root element remains open has
been modified. Previously, there was special handling for text
nodes, which has now been removed. A new check has been introduced to
verify if the root editable element is an inline or text control. If
it is not, a placeholder will be added.
The following tests and expectations have been updated as they were
not expecting <br> with the current baseline. After this change,
these tests will now start to expect the <br> tag.
Currently, Firefox is adding the <br> tag, which is not
the case with Chrome. However, post this change, the same behavior
will be observed in Chrome as well.
The tests below are under
third_party/blink/web_tests/third_party/blink/web_tests/editing/
deleting/5847330-2-expected.txt
deleting/delete_select_all.html
deleting/delete-across-editable-content-boundaries-1-expected.txt
deleting/delete-and-cleanup.html
deleting/delete-and-cleanup-expected.txt
execCommand/delete-non-editable-range-crash.html
commands/apply_style_command_test.cc
commands/delete_selection_command_test.cc
commands/typing_command_test.cc
The tests below are under
third_party/blink/web_tests/third_party/blink/web_tests/fast/events/
event-input-contentEditable-expected.txt
inputevents/inputevent-yank.html
key-events-in-editable-flexbox.html
key-events-in-editable-flexbox-expected.txt
key-events-in-editable-gridbox.html
key-events-in-editable-gridbox-expected.txt
script-tests/event-input-contentEditable.js
The test below is under
third_party/blink/web_tests/dom/mutation-event-tests/
editing/selection/crash-on-drag-with-mutation-events-expected.txt
The test below is under
third_party/blink/web_tests/wpt_internal/
css/css-ui/webkit-user-modify-all-revert.html
Bug: 40702380
Change-Id: I3418b167b759d136fbc33b3593b5eb1698b14af6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5787236
Reviewed-by: Siye Liu <siliu@microsoft.com>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Tanu Jain <tanujain@microsoft.com>
Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1354046}
--
wpt-commits: e73b22db7d6b11412c803eff0c30a2cc29270f42
wpt-pr: 48102
Automatic update from web-platform-tests
Make notifyEvent transfer transient activation.
The `window.fence.notifyEvent()` API should "transfer"
transient activation from the fenced frame to its embedder. To transfer
transient activation, the fenced frame consumes it and then applies it
the outer document afterwards. This ensures that the embedder can use
an activation-gated API in response to an event occurring in the
fenced frame, but that only one of those APIs can be used per event.
Change-Id: I97749cd94fe1040ae118086a6b23890bcc62ef3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5577336
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Liam Brady <lbrady@google.com>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Andrew Verge <averge@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353940}
--
wpt-commits: 219a3e717b2377251ce28e09d39a48e64508ab88
wpt-pr: 48100
Automatic update from web-platform-tests
FLEDGE: Add WPT for high-level problems with serverResponse payload
In particular error injection at various layers and failing to
find/authorize the response.
Change-Id: Id6d77d7866ab7acf4d1c2fef5cb637c7f0a8065a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850614
Reviewed-by: Russ Hamilton <behamilton@google.com>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353884}
--
wpt-commits: 4342b3fe13533967b3d1509fe851338887ebabd6
wpt-pr: 48091
Automatic update from web-platform-tests
WebNN: Add IDL and mojo definitions for `scatterND` operator
The `scatterND` operator is proposed by WebML WG [1] for improving
performance of passing partial MLBuffer/MLTensor between transformers
decoder iterations for key-value reuse.
This CL also implements data type limits, inputs validation and adds
validation tests for `scatterND` operator.
[1]: https://github.com/webmachinelearning/webnn/issues/375#issuecomment-2292466613
Bug: 363677531
Change-Id: Ib68db63c7b51b99f9976b1eb3c06f8b7f0de9f97
Cq-Include-Trybots: luci.chromium.try:win11-blink-rel, mac14.arm64-blink-rel, mac14-blink-rel, mac15.arm64-blink-rel, mac15-blink-rel, linux-blink-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5829103
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Weizhong Xia <weizhong@google.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Commit-Queue: ningxin hu <ningxin.hu@intel.com>
Cr-Commit-Position: refs/heads/main@{#1353781}
--
wpt-commits: 49e41159a0edc30eb8a0316a457caba99e73a801
wpt-pr: 48082
Automatic update from web-platform-tests
[line-clamp] Add test for -webkit-line-clamp as a block-in-inline
This also fixes a bug in the existing `webkit-line-clamp-047` test.
Bug: 40336192
Change-Id: I1b0d665bccfc8d79e52091b3155e9795db0c2240
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5850277
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Andreu Botella <abotella@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1353690}
--
wpt-commits: dbca9cf6c43a2a4125a32fbcd6a8d92b0596b211
wpt-pr: 48093
Automatic update from web-platform-tests
Reject multi-channel Opus config w/o description
Opus decoders configured with 2 or fewer channels do not need an
extradata field.
For more than 2 channels, we need to pass in extradata through
`AudioDecoderConfig.description` when calling configure(). This is
necessary because we cannot guess whether the encoded Opus streams are
mono or stereo streams. For example, a 5.1 channel Opus file can be
encoded as 6 mono streams, or 3 stereo streams, or anywhere in between.
This CL updates WebCodecs code and WPTs to ensure that Opus configs
with more than 2 channels and no description are rejected when
isConfigSupported() is called, rather than causing an error during the
actual configure() call.
Bug: 360083330
Change-Id: I428623ee5497e78db32a46824769951d8d66b9a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5819914
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353634}
--
wpt-commits: 1fe7db97e6d2347220763a2ac2697b9779e1960f
wpt-pr: 48089
Automatic update from web-platform-tests
FSA: Fix file cleanup code in WPTs
Recently attempted to add cleanup code to these tests but the cleanup
code was incorrect. The tests continued to pass so it wasn't caught by
the CQ.
This fixes the cleanup code.
Bug: 363601806
Change-Id: Ice9f23cc1400854002c3e9b4f3a45ce11dbc0cc8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5846508
Reviewed-by: Christine Hollingsworth <christinesm@chromium.org>
Commit-Queue: Nathan Memmott <memmott@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353627}
--
wpt-commits: fa10aa8d9de06b5db6f21a720d2b4677817c8aa7
wpt-pr: 48088
Automatic update from web-platform-tests
Mark tests failed with 500 disconnected error as crash (#48059)
* Mark tests failed with 500 disconnected error as crash
In a multiple processes architecture, when the renderer processes
crashed, the liveness check won't necessary fail as the browser process
is still running. One common error we see in Chromium is that webdriver
will report 500 disconnected, with an error message "Unable to receive
message from renderer". Previously the test result is Internal Error
instead of Crash.
Bug: 362506646
* update per comments
--
wpt-commits: e32d13885824ca43d5dfd7a23948cb61f2dac125
wpt-pr: 48059
Automatic update from web-platform-tests
idle-detection: Add test for full activation in requestPermission()
Adds a Web Platform Test for the "document is fully active" check in the
requestPermission() method steps and fixes the behavior in that case to
return a rejected promise rather than returning undefined.
Change-Id: I85c3487ef0a26fe0d35d13c05da0b605108a9be1
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5847720
Reviewed-by: Jeffrey Yasskin <jyasskin@google.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1353502}
--
wpt-commits: 618894272981cfa82c3ce19263784515b9704a91
wpt-pr: 48080
Automatic update from web-platform-tests
Support all non-absolute colors as a basis for relative color syntax
This is simply a matter of lifting the restriction in the parsing code.
Existing recursive behaviors in CSSColorFunctionParser and
StyleColor::UnresolvedColorFunction are already set up to handle cases
beyond just `currentcolor` as an origin.
Bug: 325309578, 41492196
Change-Id: I5ce01dc6eb7757955583c7ae4a606a3306478dca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5757594
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Kevin Babbitt <kbabbitt@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1353402}
--
wpt-commits: 90ee8c65751cdc73f31909e64ef5ebd6c52b8d2c
wpt-pr: 48071
Glean metrics are described in yaml, which is notably slow to parse.
Instead of repeatedly parsing the same metrics again and again, cache
the parsing result.
Differential Revision: https://phabricator.services.mozilla.com/D221944
This makes Ion compilation of the Wasm module in bug 1916442 about 7% faster.
The patch also renames `prevRange` to `nextRange`. The `prevRange` name was likely
copy/pasted from `HasPrecedingRangeSharingVreg`.
Differential Revision: https://phabricator.services.mozilla.com/D221581
Gamma-aware ClearType rendering is used on Windows even when requesting
grayscale AA, as we still sample the approximate luminance of the ClearType
result to generate the grayscale result. To compensate for this, we have to
use preblending for grayscale AA, even when no subpixel AA is requested.
Differential Revision: https://phabricator.services.mozilla.com/D222229
The iterator uses both explicitly set element attributes and content attributes
with IDs to iterate over all associated elements
Differential Revision: https://phabricator.services.mozilla.com/D215688
According to test result on tryserver, the constructor may receive text frame,
although I couldn't reproduce it with writing tests. Then, it'll return
the text node as the mouse event target after dispatching a pointer event.
However, mouse events need to be targeted to element node. Therefore, it's
wrong to use the frame when `aTargetContent` is specified.
Additionally, for the last resort, it should refer an inclusive ancestor element
of the target frame content if `aTargetContent` is not specified and the event
should be targeted to an element.
Finally, there is another path to set non-element node in
`PresShell::EventHandler::DispatchEventToDOM`. The path is not the cause of
the reported case, but we should fix it too.
Differential Revision: https://phabricator.services.mozilla.com/D222091
Do it at the same time as UpdateRemoteFrameEffects() (so, intersection
observer timing). Otherwise we can see flickering sometimes from the
resize with the previous patch (and this should be less work, when we
resize).
Non-remote frames need to synchronously communicate their resizes
(because JS could access the frame), but that's not an issue for
remote frames.
This should also more reliably prevent issues like bug 1910887 or like
bug 1764655, and paves the way for fixing bug 1750189 (which stalled) in
a similar fashion.
I tested this in a build with a couple hundred tabs open and it doesn't
measurably show up. I think we should consider not communicating resizes
to background tabs / hidden remote iframes, at least for top levels.
Differential Revision: https://phabricator.services.mozilla.com/D221405
This patch adds support for exposing the capture time, receive time,
processing duration and RTP timestamp parameters on the callback for
rVFC for WebRTC related elements.
It also improves the accuracy of the media time paramater for normal
playback.
Differential Revision: https://phabricator.services.mozilla.com/D221671
