a73350397302b7531c88c0ab2ae8e81aa197fab5: Bug 1528716 [wpt PR 15395] - Add @danyao, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Tue, 05 Mar 2019 12:15:09 +0000 - rev 464216
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528716 [wpt PR 15395] - Add @danyao, a=testonly Automatic update from web-platform-tests Add @danyao (#15395) -- wpt-commits: 0bd21dbf163460eed6f9af0d8ec40fe6f49a8435 wpt-pr: 15395
84b7e38be0cc0c0057ac4361a19f24b0509ec63a: Bug 1513857 [wpt PR 14491] - Add CEReactions tests for HTMLBaseElement, a=testonly
kaixinjxq <xiuqix.jiang@intel.com> - Tue, 05 Mar 2019 12:15:07 +0000 - rev 464215
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1513857 [wpt PR 14491] - Add CEReactions tests for HTMLBaseElement, a=testonly Automatic update from web-platform-tests Add CEReactions tests for HTMLBaseElement -- wpt-commits: ce667da7c2cf7485f9d818deb67641613b0c5ef3 wpt-pr: 14491
e63c628980332dd9094a0cd37e66765574e021e2: Bug 1528711 [wpt PR 15386] - [PaymentRequest][WPT] Automate manual tests that need user click., a=testonly
Danyao Wang <danyao@chromium.org> - Tue, 05 Mar 2019 12:14:50 +0000 - rev 464214
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528711 [wpt PR 15386] - [PaymentRequest][WPT] Automate manual tests that need user click., a=testonly Automatic update from web-platform-tests [PaymentRequest][WPT] Automate manual tests that need user click. Before this patch, test cases that need a user click were implemented as manual tests. This patch automates them using testdriver.bless() API, which simulates a user click action using WebDriver. Bug: 929773 Change-Id: I368e5867c2a889504a360d7d704aa83d3cf9c78e Reviewed-on: https://chromium-review.googlesource.com/c/1471297 Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Danyao Wang <danyao@chromium.org> Cr-Commit-Position: refs/heads/master@{#632259} -- wpt-commits: 85614961e6ee65fe339a7a8e770499c80cccae28 wpt-pr: 15386
a7ee2a24d89807ed007b8c244bf1d78dfab483af: Bug 1527353 [wpt PR 15335] - [LayoutNG] Invalidate layout when OOF-positioned gets added/removed., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Tue, 05 Mar 2019 12:14:48 +0000 - rev 464213
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1527353 [wpt PR 15335] - [LayoutNG] Invalidate layout when OOF-positioned gets added/removed., a=testonly Automatic update from web-platform-tests [LayoutNG] Invalidate layout when OOF-positioned gets added/removed. This patch allows us to reuse a cached layout result when we have OOF-positioned descendants in the result. In order to do this whenever a OOF-positioned object gets added or removed we invalidate the parent chain for all objects which may contain this element inside its layout result. There are more optimal versions of this approach, which I've noted inside a comment, but this seems good enough for now. Bug: 635619 Change-Id: I4b29fcc26154dcd76cee55455d83558c6cf798fa Reviewed-on: https://chromium-review.googlesource.com/c/1396777 Reviewed-by: Emil A Eklund <eae@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Aleks Totic <atotic@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#632256} -- wpt-commits: bbe1144015e708f62b9ae30b3770884db94e504b wpt-pr: 15335
5fb707e280c13e4f7e61d437c66dd59940078ac1: Bug 1509034 [wpt PR 14163] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 22 Nov 2018 07:09:20 +0000 - rev 464212
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1509034 [wpt PR 14163] - Update wpt metadata, a=testonly wpt-pr: 14163 wpt-type: metadata
be42c83c6e9797698bac9eb972158fde092dbc18: Bug 1509034 [wpt PR 14163] - fix: make PMIs conform to spec, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Tue, 05 Mar 2019 12:14:35 +0000 - rev 464211
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1509034 [wpt PR 14163] - fix: make PMIs conform to spec, a=testonly Automatic update from web-platform-tests fix: make PMIs conform to spec (#14163) -- wpt-commits: 94dd52b3f5a6e768d25a3cc459aeeb1e69fb9381 wpt-pr: 14163
2eb522ceb6e1c842c8c5b2950d4a4ab2ef88268c: Bug 1528709 [wpt PR 15391] - HTML: window.name, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 05 Mar 2019 12:14:32 +0000 - rev 464210
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528709 [wpt PR 15391] - HTML: window.name, a=testonly Automatic update from web-platform-tests HTML: window.name For https://github.com/whatwg/html/pull/4366. -- wpt-commits: 8e76fc76d3af0a56d0ccdd627fe844fd9c5a1554 wpt-pr: 15391
822ff0ac5f39581494eece446f71586dc003d7cb: Bug 1527981 [wpt PR 15374] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 18 Feb 2019 11:08:42 +0000 - rev 464209
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1527981 [wpt PR 15374] - Update wpt metadata, a=testonly wpt-pr: 15374 wpt-type: metadata
3fb86165ce50dd6cb220d7def829d09f40ec9a64: Bug 1527981 [wpt PR 15374] - Update interfaces/webxr.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 05 Mar 2019 12:14:18 +0000 - rev 464208
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1527981 [wpt PR 15374] - Update interfaces/webxr.idl, a=testonly Automatic update from web-platform-tests Update interfaces/webxr.idl (#15374) Source: https://github.com/tidoust/reffy-reports/blob/d3ee200/whatwg/idl/webxr.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/492560012 -- wpt-commits: fbbf9a6b68f06236be7cfbf75807e0fc2e5e0930 wpt-pr: 15374
7f5ce8587ad9a48d58e387db12b3e022881825d8: Bug 1528705 [wpt PR 15389] - XMLSerializer should drop xmlns="..." in some cases, a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 05 Mar 2019 12:14:01 +0000 - rev 464207
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528705 [wpt PR 15389] - XMLSerializer should drop xmlns="..." in some cases, a=testonly Automatic update from web-platform-tests XMLSerializer should drop xmlns="..." in some cases If an element has no prefix and its namespace is different from the current default namespace, the element needs to add xmlns="<elements-namesapce-uri>". In such case, we need to drop existing xmlns="<other-uri>" and need to take care of existing xmlns="<elements-namespace-uri>". Implementation: Follow the specification in the following points: - Stop registering default namespace to prefix-namespace / namespace-prefixes maps. - The default namespace is tracked by NamespaceContext:: context_namespace_. - 'local default namespace' is computed in 'recording the namespace information' algorithm. * NamespaceContext::Add(): Make sure arguments are not empty. * Move MarkupAccumulator::RecordNamespacInformation to NamespaceContext, and update the default namespace handling. * AppendElement() respects to 'ignore namespace definition attribute' flag. * Implement some parts of the specification to - keep track the default namespace - return correct 'ignore namespace definition attribute' value - add an appropriate xmlns="..." Bug: 929035 Change-Id: Id5f0090d5dc08334c202e6ef9b107f1645fb3120 Reviewed-on: https://chromium-review.googlesource.com/c/1471671 Commit-Queue: Kent Tamura <tkent@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#632142} -- wpt-commits: 1b2808938937c9e992eb469b345ca64f99182c29 wpt-pr: 15389
b571112619c2d35a0425b7d7b2a388a6bacec1ad: Bug 1528702 [wpt PR 15388] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 19 Feb 2019 15:57:09 +0000 - rev 464206
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528702 [wpt PR 15388] - Update wpt metadata, a=testonly wpt-pr: 15388 wpt-type: metadata
8b3668ee05790703111fa1db9988f9d27d37895f: Bug 1528702 [wpt PR 15388] - SignedExchange: Close response body data pipe on integrity error, a=testonly
Kunihiko Sakamoto <ksakamoto@chromium.org> - Tue, 05 Mar 2019 12:13:47 +0000 - rev 464205
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528702 [wpt PR 15388] - SignedExchange: Close response body data pipe on integrity error, a=testonly Automatic update from web-platform-tests SignedExchange: Close response body data pipe on integrity error This fixes a bug where data pipe for response body was not closed when Signed Exchange has payload integrity error. SourceStreamToDataPipe::OnComplete() attempts to close the pipe by resetting |pending_write_|. But if |source_| is a FilterSourceStream, it still retains a reference to |pending_write_|. We should explicitly call |pending_write_->Complete(0)| to free the pipe on error cases too. Bug: 931955 Change-Id: I63b2470dbb92aa57016c5c71222bcdabe889fd34 Reviewed-on: https://chromium-review.googlesource.com/c/1470355 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#632118} -- wpt-commits: 2867bad83ba14201d96f1eaf54027164251fe541 wpt-pr: 15388
0562ba7637c2f9326f482cd69b2c3f8d8019be83: Bug 1528058 [wpt PR 15378] - [Screen Orientation] Fix: add requestFullscreen to lock-basic, a=testonly
Johanna <Johanna-hub@users.noreply.github.com> - Tue, 05 Mar 2019 12:13:45 +0000 - rev 464204
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528058 [wpt PR 15378] - [Screen Orientation] Fix: add requestFullscreen to lock-basic, a=testonly Automatic update from web-platform-tests [Screen Orientation] Fix: add requestFullscreen to lock-basic (#15378) -- wpt-commits: 0f05661c8e441416e314cc6c5779671d29c81a09 wpt-pr: 15378
9e73b2eb508fa1a46770a422f0093f7ccd284e54: Bug 1528700 [wpt PR 15385] - [Screen Orientation] Fix: add requestFullscreen to onchange-event.html, a=testonly
Johanna <Johanna-hub@users.noreply.github.com> - Tue, 05 Mar 2019 12:13:43 +0000 - rev 464203
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528700 [wpt PR 15385] - [Screen Orientation] Fix: add requestFullscreen to onchange-event.html, a=testonly Automatic update from web-platform-tests Fix: add requestFullscreen (#15385) -- wpt-commits: 0db395ed1acb636ab0fa2686944a46d038d073d4 wpt-pr: 15385
d3e10f10f4c2acb28ce6ee88930c55f5d2c0c809: Bug 1528032 [wpt PR 15377] - WPT: service worker: Loosen postmessage-to-client-message-queue.https.html., a=testonly
Matt Falkenhagen <falken@chromium.org> - Tue, 05 Mar 2019 12:13:40 +0000 - rev 464202
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528032 [wpt PR 15377] - WPT: service worker: Loosen postmessage-to-client-message-queue.https.html., a=testonly Automatic update from web-platform-tests WPT: service worker: Loosen postmessage-to-client-message-queue.https.html. Chrome flakily failed the test because it doesn't guarantee the order between message and fetch event. That might violate the spec, but the test doesn't need to test this. It's meant to test that the client message queue isn't enabled until a certain time. We can test that without requiring message/fetch ordering. Loosen the test to just check that the messages arrive after |earliest_dispatch|. Bug: 926670 Change-Id: Ic291b25443358412936b4a5eeb24ee6f8efa6b71 Reviewed-on: https://chromium-review.googlesource.com/c/1469842 Auto-Submit: Matt Falkenhagen <falken@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#632030} -- wpt-commits: cde22888c0ffdde9842d380d11e0f09aab38006e wpt-pr: 15377
629c2a5b9013de68ac0e96f3792d0959803db9c8: Bug 1528029 [wpt PR 15376] - Remove a special handling for XLink namespace in XMLSerializer, a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 05 Mar 2019 12:13:23 +0000 - rev 464201
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528029 [wpt PR 15376] - Remove a special handling for XLink namespace in XMLSerializer, a=testonly Automatic update from web-platform-tests Remove a special handling for XLink namespace in XMLSerializer The new behavior matches to the standard, Firefox, and Safari. Bug: 927626 Change-Id: Ifc6687992c10fbca13faaaeb4a56e59f5469f594 Reviewed-on: https://chromium-review.googlesource.com/c/1469843 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#631984} -- wpt-commits: 6fb30bc55bf721c87d2ff32640deefc1b01061ab wpt-pr: 15376
78d3aefc44182764ee01790175826e4d800a29d8: Bug 1528023 [wpt PR 15375] - ensure sleep_at_least is guaranteed to sleep for the requested duration, a=testonly
Erik Anderson <Erik.Anderson@microsoft.com> - Tue, 05 Mar 2019 12:13:21 +0000 - rev 464200
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528023 [wpt PR 15375] - ensure sleep_at_least is guaranteed to sleep for the requested duration, a=testonly Automatic update from web-platform-tests ensure sleep_at_least is guaranteed to sleep for the requested duration Microsoft runs tests in a Hyper-V VM. The test external/wpt/resource-timing/resource-timing-level1.sub.html leverages wptserve's SyntheticResponse.py to request that each step of a response is delayed by 250ms. In our environment, even with the extra 15ms "padding" in sleep.py, we're seeing the timer return 5ms early which in turn causes the test to fail. This change updates the sleep_at_least function to, in a loop, explicitly check that it slept long enough and, if not, sleep again for a short interval. Change-Id: I2dbd8e6bd586dc661b45f94454d3b6b4613db1a5 Reviewed-on: https://chromium-review.googlesource.com/c/1469655 Reviewed-by: Robert Ma <robertma@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Commit-Queue: Erik Anderson <Erik.Anderson@microsoft.com> Cr-Commit-Position: refs/heads/master@{#631969} -- wpt-commits: 8f7ccae78b9a0e36aca3618f62e5bf558f4775d4 wpt-pr: 15375
48f705e0ae7ecb8b9af4d91516c8920532a279e4: Bug 1528237 [wpt PR 15367] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 18 Feb 2019 10:23:11 +0000 - rev 464199
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528237 [wpt PR 15367] - Update wpt metadata, a=testonly wpt-pr: 15367 wpt-type: metadata
f6690a972633487cbb8c5a3415bad810320d84a9: Bug 1528237 [wpt PR 15367] - [ElementTiming] Create entries for SVGImageElements, a=testonly
Nicolas Pena <npm@chromium.org> - Tue, 05 Mar 2019 12:13:07 +0000 - rev 464198
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528237 [wpt PR 15367] - [ElementTiming] Create entries for SVGImageElements, a=testonly Automatic update from web-platform-tests [ElementTiming] Create entries for SVGImageElements This change adds ElementTiming support for SVGImageElements. It adds a layout test to verify that the entry is being created in a simple example. Bug: 879270 Change-Id: I39ae0a1209f1b299d6a431ac1ba2fcfa94b25b3e Reviewed-on: https://chromium-review.googlesource.com/c/1467918 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#631923} -- wpt-commits: 679777df34300565db3d3dcca0f32424fb0472a0 wpt-pr: 15367
f62003f22992c78307a6d36deab204fb2f789f83: Bug 1528232 [wpt PR 15384] - [Azure] Use curl instead of InvokeRESTAPI@1, a=testonly
Robert Ma <bob1211@gmail.com> - Tue, 05 Mar 2019 12:13:04 +0000 - rev 464197
Push 35713 by cbrindusan@mozilla.com at Fri, 15 Mar 2019 21:55:43 +0000
Bug 1528232 [wpt PR 15384] - [Azure] Use curl instead of InvokeRESTAPI@1, a=testonly Automatic update from web-platform-tests [Azure] Use curl instead of InvokeRESTAPI@1 (#15384) InvokeRESTAPI@1 doesn't seem to allow us to customize the timeout (it has a builtin timeout of 20s), and the notify endpoint takes a while to complete as it needs to download the artifacts from Azure. Also, run both hooks (prod & staging) independently. Hope to alleviate #1131. -- wpt-commits: e0a7556f7d12da1dc38b6a051dacb224da442b72 wpt-pr: 15384
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip