Automatic update from web-platform-tests
Test percentage resolution for lspace/voffset for mpadded (#25175)
--
wpt-commits: 4b8d683b7153b567ea65fb03868bc174276a00cf
wpt-pr: 25175
Automatic update from web-platform-tests
Revert "[ChromeDriver] Support triple click in Chromedriver PerformActions"
This reverts commit 2576e02f3bddd1e0b8f93fb879e309139add9998.
Reason for revert: This CL is likely the cause of the build failure for test external/wpt/webdriver/tests/release_actions/sequence.py>>test_no_release_mouse_sequence_keeps_dblclick_state, in buildes first occurs in:
https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/91045 and
https://ci.chromium.org/p/chromium/builders/ci/linux-trusty-rel/14964
Original change's description:
> [ChromeDriver] Support triple click in Chromedriver PerformActions
>
> When we are using PerformActions from ChromeDriver to simulate three
> mouse click, it only set the click count to 2, not 3, so this test fails
> third_party/blink/web_tests/external/wpt/webdriver/tests/perform_actions
> /pointer_tripleclick.py.
>
> PerformActions should keep the mouse click count and decide if we should
> increase the count or set to 1 when we have a mouse press based on the
> interval of two mouse presses and difference between the current mouse
> positions and the last one.
>
> Bug: 1119679
> Change-Id: I2b941c5d295cdd457109c8866c55e02bb2360555
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366655
> Reviewed-by: John Chen <johnchen@chromium.org>
> Commit-Queue: Lan Wei <lanwei@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#800201}
TBR=lanwei@chromium.org,johnchen@chromium.org
Change-Id: Ie57866e4aef6ac88eca708a05459032c1fee2128
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 1119679
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368620
Reviewed-by: Maggie Cai <mxcai@chromium.org>
Commit-Queue: Maggie Cai <mxcai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800511}
--
wpt-commits: 020658e87d182f17092497b027cdf6e9e7b103ef
wpt-pr: 25174
Automatic update from web-platform-tests
Reland "Give blink::CueTimeline a timer for precisely handling cue events"
This is a reland of cb9cdc6693ba2ac64292494cca7ad28a6a00f084
Original change's description:
> Give blink::CueTimeline a timer for precisely handling cue events
>
> Cue-related events (enter, exit, cuechange) are fired up to 250ms late,
> and there is a similar latency in their display which is quite
> noticeable.
>
> The underlying problem is that we only update cues alongside the
> `timeupdate` event, which is fixed at 4 Hz.
>
> My solution is to add a separate timer to CueTimeline
> (`CueTimeline::cue_event_timer_`) which is given a timeout for the
> next cue event based on the current playback position and rate. This
> allows for significantly more precise cue timing accuracy without a
> significant performance penalty.
>
> Additionally, several web tests were written with the expectation that
> the 'time marches on' algorithm is run before video playback begins
> (ie, upon loading text track cues). This behavior is not in accordance
> with the spec (as outlined in crbug/1050767), so this CL fixes those
> expectations and adds a new test to prevent regressing.
>
> Bug: 576310, 1050767
> Change-Id: I675f5f030a68ba9cee10e12b3e79a9b174048193
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008079
> Commit-Queue: Will Cassella <cassew@google.com>
> Reviewed-by: Fredrik Söderquist <fs@opera.com>
> Cr-Commit-Position: refs/heads/master@{#800148}
Bug: 576310
Bug: 1050767
Change-Id: I735f5344005798b8d1543e020ba3920c9d2134dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368079
Auto-Submit: Will Cassella <cassew@google.com>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#800503}
--
wpt-commits: 030f04c3392fe22b7c4293c2323c846db8b9cc11
wpt-pr: 25171
Automatic update from web-platform-tests
Revert "Give blink::CueTimeline a timer for precisely handling cue events"
This reverts commit cb9cdc6693ba2ac64292494cca7ad28a6a00f084.
Reason for revert: This CL is likely the cause of build failure for Builder Linux Tests (dbg)(1) since https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29/91043. Revert to see if that fix the build
Original change's description:
> Give blink::CueTimeline a timer for precisely handling cue events
>
> Cue-related events (enter, exit, cuechange) are fired up to 250ms late,
> and there is a similar latency in their display which is quite
> noticeable.
>
> The underlying problem is that we only update cues alongside the
> `timeupdate` event, which is fixed at 4 Hz.
>
> My solution is to add a separate timer to CueTimeline
> (`CueTimeline::cue_event_timer_`) which is given a timeout for the
> next cue event based on the current playback position and rate. This
> allows for significantly more precise cue timing accuracy without a
> significant performance penalty.
>
> Additionally, several web tests were written with the expectation that
> the 'time marches on' algorithm is run before video playback begins
> (ie, upon loading text track cues). This behavior is not in accordance
> with the spec (as outlined in crbug/1050767), so this CL fixes those
> expectations and adds a new test to prevent regressing.
>
> Bug: 576310, 1050767
> Change-Id: I675f5f030a68ba9cee10e12b3e79a9b174048193
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008079
> Commit-Queue: Will Cassella <cassew@google.com>
> Reviewed-by: Fredrik Söderquist <fs@opera.com>
> Cr-Commit-Position: refs/heads/master@{#800148}
TBR=fs@opera.com,alancutter@chromium.org,mlamouri@chromium.org,cassew@google.com
Change-Id: I0563b173344cef976c16b4f2851b45762a67843f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 576310
Bug: 1050767
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368614
Reviewed-by: Maggie Cai <mxcai@chromium.org>
Commit-Queue: Maggie Cai <mxcai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800432}
--
wpt-commits: 5f8ee811d7e389f36bc435abf33566eae2ce832e
wpt-pr: 25170
Automatic update from web-platform-tests
Copy and destroy frames on encode()
This CL changes the behavior of VideoEncoder to make an internal copy
of frames passed in through encode(), before destroying the passed
frame. This means that users don't need to call destroy() after passing
frames to encode(), which could result in a frame being invalidated
before we send it to the internal encoder. It also means we can destroy
the frame internally when we no longer need it without risking that it
might still be in use by the user.
Users that which to keep their frames alive after giving them to the
encoder can send a cloned copy instead.
Bug: 1108023
Change-Id: Ie5cd98d688a53314ac16a6a3ac7afe2a65d742f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363863
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800296}
--
wpt-commits: 3bbe514f09fcd6241bac429bef8a36860a0e2732
wpt-pr: 25159
Automatic update from web-platform-tests
docs: Reference the right function in "Timeouts in Tests"
`step_wait_func` was being referenced twice; what we want instead is to
mention both `step_wait_func` and `step_wait_func_done`.
--
wpt-commits: 54ae6127dc1676c6363cf08a21e5bd1c047c2ad1
wpt-pr: 25143
Automatic update from web-platform-tests
[webcodecs] Implement Audio/VideoDecoder error callback.
This is implemented in terms of an |is_closed_| state, which prevents
reentrancy during shutdown.
Bug: 1045247
Change-Id: I69e8bd095979f6571fbe95b298f91166b61dc9f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363998
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800282}
--
wpt-commits: 4f4483cddb83ac78b64d0612aba2277b28441081
wpt-pr: 25124
Automatic update from web-platform-tests
Parse codecs on VideoEncoder::Configure()
This CL front-loads the configuration parsing and codec support
verification into the Configure() method. This means that and invalid
or unsupported config should immediately throw an exception, rather than
being reported in the error callback.
This CL also allows encoders to be re-configured.
Bug: 1116783, 1094166
Change-Id: I88df452cfa2a1b0fcfeb4da6c279665661d7380f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363711
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800277}
--
wpt-commits: be6aa0ccd2409613b0adc835580cec14def7d505
wpt-pr: 25082
Automatic update from web-platform-tests
ScrollAnchoring: Limit focus priority to editable elements.
This patch limits the selection of priority candidate to focused
elements with editable style. That is, previously we would consider
any focused element as a priority scroll anchor. Now, this is only
true if the element is editable.
This should be a middle ground that allows most cases in referenced
bug to be fixed (> 30 stars, multiple merged bugs). However, it would
also preserve the layout stability when editing forms with text
input.
R=chrishtr@chromium.org
Fixed: 1102229
Change-Id: I7341f0e513b70f8a4d836cebb68b931f2518534f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363079
Auto-Submit: vmpstr <vmpstr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800259}
--
wpt-commits: 41bff1fb76d6a0bd5c1fe4402ccc3d499c0a3077
wpt-pr: 25070
Automatic update from web-platform-tests
[ChromeDriver] Support triple click in Chromedriver PerformActions
When we are using PerformActions from ChromeDriver to simulate three
mouse click, it only set the click count to 2, not 3, so this test fails
third_party/blink/web_tests/external/wpt/webdriver/tests/perform_actions
/pointer_tripleclick.py.
PerformActions should keep the mouse click count and decide if we should
increase the count or set to 1 when we have a mouse press based on the
interval of two mouse presses and difference between the current mouse
positions and the last one.
Bug: 1119679
Change-Id: I2b941c5d295cdd457109c8866c55e02bb2360555
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366655
Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800201}
--
wpt-commits: ec174976221ab481a1cdaec1c8be450fa48a6c1e
wpt-pr: 25152
Automatic update from web-platform-tests
[SanitizerAPI] The initial commit.
This CL intends to create a prototyping Sanitizer API
(https://github.com/WICG/sanitizer-api) at very beginning
level.
Change-Id: I7327a3440d544b61becd81f4c9b058ee4823ffc4
Bug: 1116418
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346252
Commit-Queue: Yifan Luo <lyf@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Yifan Luo <lyf@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800191}
--
wpt-commits: dea703888c8e29162439a6e3980e03f3315a3fbe
wpt-pr: 25123
Automatic update from web-platform-tests
Give blink::CueTimeline a timer for precisely handling cue events
Cue-related events (enter, exit, cuechange) are fired up to 250ms late,
and there is a similar latency in their display which is quite
noticeable.
The underlying problem is that we only update cues alongside the
`timeupdate` event, which is fixed at 4 Hz.
My solution is to add a separate timer to CueTimeline
(`CueTimeline::cue_event_timer_`) which is given a timeout for the
next cue event based on the current playback position and rate. This
allows for significantly more precise cue timing accuracy without a
significant performance penalty.
Additionally, several web tests were written with the expectation that
the 'time marches on' algorithm is run before video playback begins
(ie, upon loading text track cues). This behavior is not in accordance
with the spec (as outlined in crbug/1050767), so this CL fixes those
expectations and adds a new test to prevent regressing.
Bug: 576310, 1050767
Change-Id: I675f5f030a68ba9cee10e12b3e79a9b174048193
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008079
Commit-Queue: Will Cassella <cassew@google.com>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#800148}
--
wpt-commits: 093d4eed8ba6b92f205f35d80ad91a750bbd4a2d
wpt-pr: 22071
Automatic update from web-platform-tests
Origin isolation: finish off popup test coverage
As part of this, we fix a bug in send-header-page-script.mjs which was
not correctly reading the "send-loaded-message" query parameter. In the
less-comprehensive tests that were there previously, the buggy code
still worked, but these new tests brought out the problem.
Bug: 1042415
Change-Id: Id34c627d1d7fdd41727f3db362ada25a6651498f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364172
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799870}
--
wpt-commits: 9f0103203082e75cc7be338c46165f32853909f6
wpt-pr: 25150
Automatic update from web-platform-tests
[html] Omit empty COOP/COEP reporting HTTP headers (#24343)
Prior to this patch, when a test made a request to the `coop-coep.py`
and did not specify a desired value for the "report only" headers, the
response would include the headers without values.
Only include "report only" headers when they have been explicitly
specified. Should tests require empty values for these headers (as in
the original behavior), they may specify query string parameters without
values, e.g.
coop-coep.py?coop-report-only=
--
wpt-commits: 2520b441890b9a2156e16732f97fbf7867fcbd68
wpt-pr: 24343
Automatic update from web-platform-tests
wpt: sensors: use of assert_implements
Taking in use new testharness.js API assert_implements instead of
assert_true.
Bug: 1119345
Change-Id: I4155d90968952e7bfa63a0c8755ba3c79e3145c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364494
Reviewed-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Cr-Commit-Position: refs/heads/master@{#800075}
--
wpt-commits: 79786c32128f010abeceaf6b27969b7b9026e76d
wpt-pr: 25132
Automatic update from web-platform-tests
Origin isolation: add initial popup WPTs
This introduces a couple basic web platform tests for the popup cases.
The main content of this CL is generalizing the test infrastructure,
which previous was iframe-specific. Subsequent CLs will add a more
comprehensive suite of popup tests.
Bug: 1042415
Change-Id: I4f993783613f32cf9ebfb10e29973820e2fc9aad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2364057
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#799695}
--
wpt-commits: 127286f9b8fe998db82add546285d2e509e5d87a
wpt-pr: 25109
Automatic update from web-platform-tests
[image-orientation] Fix background-position
An error introduced in a previous patch caused
background-position calculations to be broken due
to incorrect source rect transforms. Fix it and
add a more thorough test. The test fails pending
fuzzy matching in Chrome.
Bug: 1108698
Change-Id: Iabdc332474daa0c5dc4aeb61df338c6028212c65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365914
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#800083}
--
wpt-commits: f7d38f48f4be0522a695b7ed4e228e6ac3671605
wpt-pr: 25131
Automatic update from web-platform-tests
[LayoutNG] Correct border painting for block fragmentation.
Add a few new tests, as coverage seemed low.
Fix PhysicalBoxSides writing-mode converter to handle vertical-lr, and
skip sideways-lr and sideways-rl, since those aren't even supported by
the CSS parser.
Update BackgroundRoundedRectAdjustedForBleedAvoidance() to skip the
borders that aren't part of the fragment. I suppose inline fragmentation
wasn't using this code path, but block fragmentation uses it.
Bug: 829028
Change-Id: I7e3f78a4fde54c7da1442efdabe609651cd27d10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2362902
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800047}
--
wpt-commits: 01ce6e496d457671942418efae0a35583c425544
wpt-pr: 25119
Automatic update from web-platform-tests
[RTCInsertableStreams] Add support for readable/writable fields
This CL adds the readable and writable fields to the
RTCInsertableStreams dictionary.
These are equivalent to and will replace readableStream and writableStream.
The reason for this is consistency with other APIs that use stream pairs.
Drive-by: rename RTCCodedVideoFrameType to RTCEncodedVideoFrameType to
match the spec and update tests to comply with other API changes.
Bug: 1119653
Change-Id: I64bcafb2602fb952722f1845abaeebd09f3e77d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366592
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800032}
--
wpt-commits: b385c85f8210742df3764042b8f098a3a0c5f1a2
wpt-pr: 25138
Automatic update from web-platform-tests
Add interfaces/scroll-to-text-fragment.idl and test (#24658)
--
wpt-commits: cd5f4dfe123b7bdcb3c7904e883d181da4076fa2
wpt-pr: 24658
autofoolip
Rob Buis
Maggie Cai
Will Cassella
Dan Sanders
Matt Menke
moz-wptsync-bot
Olivier Yiptong
Thomas Guilbert
Raphael Kubo da Costa
Vladimir Levin
Lan Wei
Yifan Luo
Guido Urdaneta
Domenic Denicola
jugglinmike
Arnaud Mandy
Stephen Chenney
Morten Stenshorne
Philip Jägenstedt