d1afd891ac348c1df050feb96de8b67419b34a72: Bug 1528721 [wpt PR 15403] - XMLSerializer: Support element prefix rewriting., a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 05 Mar 2019 12:15:16 +0000 - rev 464552
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528721 [wpt PR 15403] - XMLSerializer: Support element prefix rewriting., a=testonly Automatic update from web-platform-tests XMLSerializer: Support element prefix rewriting. We need to change the prefix of an element if: - The element's namespace is same as the inherited default namespace, and the element prefix is not empty, - The prefix-namespace pair of an element is not declared, and there is another prefix associated to the namespace, or - The namespace of an element is not associated to any prefixes, and the element's prefix is declared for another namespace in the element. This CL implements Step 11, 12.1 to 12.5 of [1]. * Add capability to serialize prefix which is not element.prefix() to MarkupFormatter * MarkupAccumulator::AppendElement() returns a serialized prefix, and AppendEndTag() takes it as an argument. * MarkupAccumulator::AppendStartTagOpen() implements the steps, and returns a serialized prefix as well as 'ignore namespace definition attribute' flag. * MarkupAccumulator::RetrievePreferredPrefixString(): Remove the code for empty prefix for elements. Empty prefix is handled in the callsite. * MarkupAccumulator::ShouldAddNamespaceElement(): Removed. It's not used any longer. * dom/domparsing/xmlserializer-xml-namespace-expected.txt: The new behavior is expected. We successfully find 'xml' prefix. [1] https://w3c.github.io/DOM-Parsing/#xml-serializing-an-element-node Bug: 929035 Change-Id: Icf63cb40b120d29a4b8678104592739d773f3a48 Reviewed-on: https://chromium-review.googlesource.com/c/1473090 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#632459} -- wpt-commits: 2767f92702b54d58cd8b4c289f00a7bc028c10fb wpt-pr: 15403
22da78af2c327e3296ca94ce093bedff27ca865e: Bug 1528719 [wpt PR 15397] - adding a new test on rgba() function, a=testonly
Gérard Talbot <github@gtalbot.org> - Tue, 05 Mar 2019 12:15:11 +0000 - rev 464551
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528719 [wpt PR 15397] - adding a new test on rgba() function, a=testonly Automatic update from web-platform-tests adding a new test on rgba() function -- wpt-commits: ad219567030d1f99f7310f52a17546b57b70d29e wpt-pr: 15397
ad337b335d8d92df29535f4ff7b30896937a4e0b: Bug 1528716 [wpt PR 15395] - Add @danyao, a=testonly
Marcos Cáceres <marcos@marcosc.com> - Tue, 05 Mar 2019 12:15:09 +0000 - rev 464550
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
2f840f6a520912ad49da1fc461244b4edf3dfadd: 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 464549
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
51e1957476b218de66b0d3587106a8fb7589e244: 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 464548
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
43322b4cde08eb96eb0ce8837af809d5c69ee508: 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 464547
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
35d0e81b48a8edd80664f47a99cf23b9331e9ce5: 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 464546
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1509034 [wpt PR 14163] - Update wpt metadata, a=testonly wpt-pr: 14163 wpt-type: metadata
3983aba2b0dfdb45a329a35961a726e45aafdf0c: 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 464545
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
9acf395a6242f447db603b86c78f32f722081cf9: 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 464544
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
cec99a4c022407f66cf57e2d5cb6987ea320adcb: 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 464543
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1527981 [wpt PR 15374] - Update wpt metadata, a=testonly wpt-pr: 15374 wpt-type: metadata
054360de14538a69798029c4918dc5c58e9e7f72: Bug 1527981 [wpt PR 15374] - Update interfaces/webxr.idl, a=testonly
autofoolip <auto@foolip.org> - Tue, 05 Mar 2019 12:14:18 +0000 - rev 464542
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
db38aa6ecb1650383ada623fb3f6138a04aeb449: 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 464541
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
c8eeaabc6e7804b4c59ccd205131a6556caf3db4: 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 464540
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528702 [wpt PR 15388] - Update wpt metadata, a=testonly wpt-pr: 15388 wpt-type: metadata
1c69ba77f5c990db4c5e9f3f75665f38285a830c: 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 464539
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
e62189593f435ecfc20424de84d5b98a1284a75d: 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 464538
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
6e9781f5e50fcc01521827c5743aec051ffd6a3d: 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 464537
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
b172a1750aecc02b5489415c7b78474918a5f236: 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 464536
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
9af6b8db40bd483d631ba7535aa16a3de3ae345f: 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 464535
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
c673e6572713ed725b687ef7bab2febed077e106: 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 464534
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +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
e76df98e1ed41f7ebd15d6e7e237e7e6a438111c: 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 464533
Push 35717 by aciure@mozilla.com at Sun, 17 Mar 2019 09:45:26 +0000
Bug 1528237 [wpt PR 15367] - Update wpt metadata, a=testonly wpt-pr: 15367 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip