35b297a3360247b8f3e6446680b0a3b0d6ff4b3d: Bug 1660570 [wpt PR 25195] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 25 Aug 2020 14:02:59 +0000 - rev 546503
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660570 [wpt PR 25195] - Update wpt metadata, a=testonly wpt-pr: 25195 wpt-type: metadata
54cc4ecca32bd7b7820b9d51d4265898e5fa3029: Bug 1660570 [wpt PR 25195] - [css-flex] Use definite cross size and aspect ratio for flex base size, a=testonly
David Grogan <dgrogan@chromium.org> - Wed, 26 Aug 2020 08:55:29 +0000 - rev 546502
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660570 [wpt PR 25195] - [css-flex] Use definite cross size and aspect ratio for flex base size, a=testonly Automatic update from web-platform-tests [css-flex] Use definite cross size and aspect ratio for flex base size When an aspect-ratio item has a definite cross size, we are supposed to compute the flex base size by multiplying those two. Blink did this when the item had a computed definite cross size, but not when the item had a definite cross size due to stretching. Firefox has the same bug. The modified canvas test relied on the buggy behavior. The tests we now fail also assert the buggy behavior, but are only one-way synced from mozilla's repository, so we can't change them. This fix is behind a flag. Bug: 704294 Change-Id: Ie17c451c7ec81ccb36fb96ff1543885bd7352bcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368321 Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: David Grogan <dgrogan@chromium.org> Cr-Commit-Position: refs/heads/master@{#800801} -- wpt-commits: 9503a10b444a62efb325d2b5d5ec393a0188e0ed wpt-pr: 25195
90a2631e4e987c618b18742dab0170553f5aadc2: Bug 1660512 [wpt PR 25185] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 25 Aug 2020 18:45:38 +0000 - rev 546501
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660512 [wpt PR 25185] - Update wpt metadata, a=testonly wpt-pr: 25185 wpt-type: metadata
05f416dc81a3b4428a9a5f08e784feeab5978e2e: Bug 1660512 [wpt PR 25185] - Audio|VideoDecoderBroker: more weakptr, keep callbacks on main thread., a=testonly
Chris Cunningham <chcunningham@chromium.org> - Wed, 26 Aug 2020 08:55:14 +0000 - rev 546500
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660512 [wpt PR 25185] - Audio|VideoDecoderBroker: more weakptr, keep callbacks on main thread., a=testonly Automatic update from web-platform-tests Audio|VideoDecoderBroker: more weakptr, keep callbacks on main thread. Using unretained for decoder/selector callbacks is generally not safe / fragile. For ex, some decoders (e.g. those that offload) will call the output callback after destruction. Another example: decoder selector internally posts the Select() callback, so it may run after destruction. Additionally, sending incoming callbacks as CrossThreadFunctions for invoking on the media thread is not safe. We may destruct while some callbacks are still pending, destroying the callbacks internal state (including bindings to blink GC types) off the main thread. Now we ensure that all callbacks are saved on the main thread and we extend the "client" interfaces of the broker for proxying the callbacks safely. Bug: 1120431 Change-Id: I2ccfe46982cda9b18e47a56424b25f54f8877883 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2366661 Commit-Queue: Chrome Cunningham <chcunningham@chromium.org> Auto-Submit: Chrome Cunningham <chcunningham@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Cr-Commit-Position: refs/heads/master@{#800776} -- wpt-commits: f32b898cd57d5dc50cfd4692e6145677358bf50b wpt-pr: 25185
3ab75d9dc47d57e2f4a587a14464836b3a1624c6: Bug 1660447 [wpt PR 25177] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 25 Aug 2020 13:56:16 +0000 - rev 546499
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660447 [wpt PR 25177] - Update wpt metadata, a=testonly wpt-pr: 25177 wpt-type: metadata
cf7b95e1841c91cfd3a2998f50fcc7692e72fe0d: Bug 1660447 [wpt PR 25177] - Fix COEP reporting tests, a=testonly
Yutaka Hirano <yhirano@chromium.org> - Wed, 26 Aug 2020 08:55:06 +0000 - rev 546498
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660447 [wpt PR 25177] - Fix COEP reporting tests, a=testonly Automatic update from web-platform-tests Fix COEP reporting tests (#25177) This is for https://github.com/whatwg/html/pull/5848. Co-authored-by: Domenic Denicola <d@domenic.me> -- wpt-commits: 8b381a62df79215dfe620cdec5cd8e18f66e099e wpt-pr: 25177
9a38734fe8144818125b3526b38206fa8cebb704: Bug 1660532 [wpt PR 25191] - wpt: Fix the content-visibility test to reflect sync-auto observation., a=testonly
Vladimir Levin <vmpstr@chromium.org> - Wed, 26 Aug 2020 08:54:59 +0000 - rev 546497
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660532 [wpt PR 25191] - wpt: Fix the content-visibility test to reflect sync-auto observation., a=testonly Automatic update from web-platform-tests wpt: Fix the content-visibility test to reflect sync-auto observation. The spec has changed to ensure that 'auto' content-visibility intersection observations are synchronous (after lifecycle) on the first frame. The test change is to expect new behavior as well as test previous behavior by making a container off-screen first. R=chrishtr@chromium.org, jarhar@chromium.org Change-Id: I0ef3182b04a2a8731a80a044689581f2a5ac3c2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368509 Reviewed-by: Joey Arhar <jarhar@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#800669} -- wpt-commits: 81e5ffd05b7a2676e5b4d080c6566e890636a494 wpt-pr: 25191
30c70717a13a6af4e6cafe63035d112f1312dafc: Bug 1660535 [wpt PR 25193] - Update interfaces/mediacapture-streams.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:54 +0000 - rev 546496
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660535 [wpt PR 25193] - Update interfaces/mediacapture-streams.idl, a=testonly Automatic update from web-platform-tests Update interfaces/mediacapture-streams.idl (#25193) Source: https://github.com/tidoust/reffy-reports/blob/d920ea7/ed/idl/mediacapture-streams.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/720023372 -- wpt-commits: ec0de4fefb1997fdc487ca1e8025277e21300ac8 wpt-pr: 25193
974e804d40138689b772ef5b165a0dae5ba28fef: Bug 1660382 [wpt PR 25163] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 25 Aug 2020 13:39:22 +0000 - rev 546495
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660382 [wpt PR 25163] - Update wpt metadata, a=testonly wpt-pr: 25163 wpt-type: metadata
1279bd47fd7d095ec4f2ddcf65b94adc8e820e31: Bug 1660382 [wpt PR 25163] - Quota: Fix null dereference., a=testonly
Jarryd <jarrydg@chromium.org> - Wed, 26 Aug 2020 08:54:46 +0000 - rev 546494
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660382 [wpt PR 25163] - Quota: Fix null dereference., a=testonly Automatic update from web-platform-tests Quota: Fix null dereference. Bug: 1117159 Change-Id: I8d8088cb7ca703d579754d880faf2926e483236b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2363258 Reviewed-by: Victor Costan <pwnall@chromium.org> Commit-Queue: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#800578} -- wpt-commits: cc83e7f5168f23316703a767094e3b3de3f8a175 wpt-pr: 25163
213d8449eeaacdc83bf5c5db0192858b66e8f46a: Bug 1659586 [wpt PR 25057] - Fix flaky pointermove on chorded buttons when locked test, a=testonly
Liviu Tinta <liviutinta@chromium.org> - Wed, 26 Aug 2020 08:54:38 +0000 - rev 546493
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1659586 [wpt PR 25057] - Fix flaky pointermove on chorded buttons when locked test, a=testonly Automatic update from web-platform-tests Fix flaky pointermove on chorded buttons when locked test Pointer lock is acquired and released asynchronously. Remove reliance on timeout from the test by waiting until lock is properly acquired/released during the test steps. Bug: 1025944 Change-Id: Ibd5b1c19efb9c00794f1b900e12a5f5a4edab16e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2360494 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Liviu Tinta <liviutinta@chromium.org> Cr-Commit-Position: refs/heads/master@{#800553} -- wpt-commits: 036f979463508b074bd145bb9d7d9582c675f2b9 wpt-pr: 25057
e99d52ed05de4bd5fb563dd4386fe51697b5a165: Bug 1660412 [wpt PR 25173] - Enable IceGatheringState test, a=testonly
Harald Alvestrand <hta@chromium.org> - Wed, 26 Aug 2020 08:54:29 +0000 - rev 546492
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660412 [wpt PR 25173] - Enable IceGatheringState test, a=testonly Automatic update from web-platform-tests Enable IceGatheringState test Rewrite test so that it does not hang (create promise before event that it is waiting for). Bug: chromium:1115080 Change-Id: Ic445bef22561a1d997b4d3657a76e1b0779a1259 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2367854 Reviewed-by: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#800544} -- wpt-commits: 5951ff0f5044bc6122d8c79ad808247ecef5aab9 wpt-pr: 25173
bad89fe12d7a70b20657b6550040b92cbe639d34: Bug 1660390 [wpt PR 25169] - Update interfaces/xhr.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:24 +0000 - rev 546491
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660390 [wpt PR 25169] - Update interfaces/xhr.idl, a=testonly Automatic update from web-platform-tests Update interfaces/xhr.idl (#25169) Source: https://github.com/tidoust/reffy-reports/blob/a1daebd/ed/idl/xhr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/719056521 -- wpt-commits: 2a93a8b3c5ba1dc94665ffc6803efae7e76f5c53 wpt-pr: 25169
d5f1d4b71d0aea9a32ce4181d6114b5967f610d6: Bug 1660389 [wpt PR 25168] - Update interfaces/worklets.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:19 +0000 - rev 546490
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660389 [wpt PR 25168] - Update interfaces/worklets.idl, a=testonly Automatic update from web-platform-tests Update interfaces/worklets.idl (#25168) Source: https://github.com/tidoust/reffy-reports/blob/4cba804/ed/idl/worklets.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/719138445 -- wpt-commits: 62518dd64307b06b838936e7f7251558305ad164 wpt-pr: 25168
663b16ac9029d4225822fe50b54c6da531489afb: Bug 1660388 [wpt PR 25167] - Update interfaces/webxr.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:14 +0000 - rev 546489
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660388 [wpt PR 25167] - Update interfaces/webxr.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webxr.idl (#25167) Source: https://github.com/tidoust/reffy-reports/blob/4cba804/ed/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/719138445 -- wpt-commits: ac2867238ffdddcec48e485dd101f70cbb98d745 wpt-pr: 25167
9e7232e5daa3dd547ddc3502ed01b27f1af0b541: Bug 1660387 [wpt PR 25166] - Update interfaces/webusb.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:09 +0000 - rev 546488
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660387 [wpt PR 25166] - Update interfaces/webusb.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webusb.idl (#25166) Source: https://github.com/tidoust/reffy-reports/blob/4cba804/ed/idl/webusb.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/719138445 -- wpt-commits: d0cec627edfdcc8840ee307e1ca3127e872d4aa8 wpt-pr: 25166
817609ebfcb01fa06e0f3c3c0ae3e82e9d9438e1: Bug 1660386 [wpt PR 25165] - Update interfaces/webrtc-identity.idl, a=testonly
autofoolip <auto@foolip.org> - Wed, 26 Aug 2020 08:54:03 +0000 - rev 546487
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660386 [wpt PR 25165] - Update interfaces/webrtc-identity.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webrtc-identity.idl (#25165) Source: https://github.com/tidoust/reffy-reports/blob/2ffcc31/ed/idl/webrtc-identity.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/719187604 -- wpt-commits: 77fc6de54b03bfe81d9c060fdfd9621cc24ac2c0 wpt-pr: 25165
877d9b7f273e2e3472b2a963159c39cd08690950: Bug 1660432 [wpt PR 25175] - Test percentage resolution for lspace/voffset for mpadded, a=testonly
Rob Buis <rbuis@igalia.com> - Wed, 26 Aug 2020 08:53:56 +0000 - rev 546486
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660432 [wpt PR 25175] - Test percentage resolution for lspace/voffset for mpadded, a=testonly Automatic update from web-platform-tests Test percentage resolution for lspace/voffset for mpadded (#25175) -- wpt-commits: 4b8d683b7153b567ea65fb03868bc174276a00cf wpt-pr: 25175
4464897c08dc10446749bc33805a44c37e5f3868: Bug 1660430 [wpt PR 25174] - Revert "[ChromeDriver] Support triple click in Chromedriver PerformActions", a=testonly
Maggie Cai <mxcai@chromium.org> - Wed, 26 Aug 2020 08:53:51 +0000 - rev 546485
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660430 [wpt PR 25174] - Revert "[ChromeDriver] Support triple click in Chromedriver PerformActions", a=testonly 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
d9277569d56d9a3af7391e51574bfb5fb8a77af2: Bug 1660401 [wpt PR 25171] - Reland "Give blink::CueTimeline a timer for precisely handling cue events", a=testonly
Will Cassella <cassew@google.com> - Wed, 26 Aug 2020 08:53:46 +0000 - rev 546484
Push 37735 by abutkovits@mozilla.com at Thu, 27 Aug 2020 21:29:40 +0000
Bug 1660401 [wpt PR 25171] - Reland "Give blink::CueTimeline a timer for precisely handling cue events", a=testonly 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
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip