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 522430
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528237 [wpt PR 15367] - Update wpt metadata, a=testonly wpt-pr: 15367 wpt-type: metadata
641af081b5e6f38ac2d24d707f41de5cfb80ba81: 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 522429
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +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
1e4f678f8bf97200cb609a08342e3c70b3d00b8e: 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 522428
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +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
c24abbb7f7e91a2501a438c1c8eba45e11cde21c: Bug 1528229 [wpt PR 15371] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 18 Feb 2019 10:16:20 +0000 - rev 522427
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528229 [wpt PR 15371] - Update wpt metadata, a=testonly wpt-pr: 15371 wpt-type: metadata
fa01f97677855f1e3853979f65afa7f97879e961: Bug 1528229 [wpt PR 15371] - [Import Maps] Implement Import Maps v0.5 behind a flag, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Tue, 05 Mar 2019 12:12:50 +0000 - rev 522426
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528229 [wpt PR 15371] - [Import Maps] Implement Import Maps v0.5 behind a flag, a=testonly Automatic update from web-platform-tests [Import Maps] Implement Import Maps v0.5 behind a flag Design doc: https://docs.google.com/document/d/1vFQzbmxg9ilpg8CT_P8roEYcpTfZ06Q5N4J9-ZQqqZo/edit This CL implements an initial version of Import Maps that supports - Inline import maps (i.e. no src attribute), - Layered API/Built-in modules fallback, and - Basic bare specifier mapping. The import maps are behind the flag of LayeredAPI. Bug: 848607 Change-Id: I31efa6f9ce470375a07592f627b525f48dc2d504 Reviewed-on: https://chromium-review.googlesource.com/c/1449093 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#631880} -- wpt-commits: 7ddae5400caf476583cfbe71238254f8cbb217b9 wpt-pr: 15371
1d35d06964626a7a283b924892bb81eefeb563b5: Bug 1528204 [wpt PR 15368] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Feb 2019 17:32:17 +0000 - rev 522425
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528204 [wpt PR 15368] - Update wpt metadata, a=testonly wpt-pr: 15368 wpt-type: metadata
2c7bc14204be05e3c4c0a53fb79ae74f7b5412ab: Bug 1528204 [wpt PR 15368] - [LayoutStability] Move layout tests to WPT, a=testonly
Nicolás Peña <npm@chromium.org> - Tue, 05 Mar 2019 12:12:35 +0000 - rev 522424
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528204 [wpt PR 15368] - [LayoutStability] Move layout tests to WPT, a=testonly Automatic update from web-platform-tests [LayoutStability] Move layout tests to WPT Bug: 581518 Change-Id: I475757c9dc66e192275b1ae02353f15a1fc8f926 Reviewed-on: https://chromium-review.googlesource.com/c/1468581 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#631861} -- wpt-commits: 92d1f6c0a381ca9c56910b9bbe6788175e8f8460 wpt-pr: 15368
24c31f79b5add4d2b053c5faaaf6fcdb1c123436: Bug 1526260 [wpt PR 15175] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Feb 2019 13:04:46 +0000 - rev 522423
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1526260 [wpt PR 15175] - Update wpt metadata, a=testonly wpt-pr: 15175 wpt-type: metadata
3712f9fd213a880081984ca55447eae36057f4f5: Bug 1526260 [wpt PR 15175] - [IntersectionObserver] Upstream V2 tests to wpt, a=testonly
Stefan Zager <szager@chromium.org> - Tue, 05 Mar 2019 11:12:29 +0000 - rev 522422
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1526260 [wpt PR 15175] - [IntersectionObserver] Upstream V2 tests to wpt, a=testonly Automatic update from web-platform-tests [IntersectionObserver] Upstream V2 tests to wpt BUG=827639 Change-Id: I38fcdd0ae40cd3122541ffa8521d4ee30adffc22 Reviewed-on: https://chromium-review.googlesource.com/c/1447267 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#631836} -- wpt-commits: 4122c04d5d5fb30cf69f5c8ca993d74162688884 wpt-pr: 15175
4e826d648be4e6be0a756d7e06d2a4ad5605d28f: Bug 1527222 [wpt PR 15332] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Feb 2019 12:51:32 +0000 - rev 522421
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527222 [wpt PR 15332] - Update wpt metadata, a=testonly wpt-pr: 15332 wpt-type: metadata
a6925bbf0b58ab3c0c3a46baf0a19893137a4186: Bug 1527222 [wpt PR 15332] - [Payment Request][WPT] Fix inactive page tests., a=testonly
Rouslan Solomakhin <rouslan@chromium.org> - Tue, 05 Mar 2019 11:12:13 +0000 - rev 522420
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527222 [wpt PR 15332] - [Payment Request][WPT] Fix inactive page tests., a=testonly Automatic update from web-platform-tests [Payment Request][WPT] Fix inactive page tests. Before this patch, the tests for calling PaymentRequest.show() in an inactive document failed because the renderer checked for an IPC connection to the browser and rejected the show() promise with an InvalidStateError because of the lack of the IPC connection. This happens because the IPC connection is terminated after the browser payment sheet closes, which happens upon a page becoming inactive. Instead, the renderer should check for an active document first and reject with AbortError in an inactive document. This patch makes PaymentRequest.show() check for an active document first and reject with AbortError in an inactive document. The IPC connection is checked second. This patch also makes a couple of active document test cases manual for ease of testing. The last test case is not moved and is still failing. It is unlikely to ever pass in Chrome, because it navigates away the context where a PaymentRequest.show() promise object was created. After the navigation, the promise object cannot change state in Chrome. After this patch, two manual test cases for active document are passing in Chrome. Bug: 929773 Change-Id: Idbe9dbd03a69c18a4d24ba34642e6c7046026c62 Reviewed-on: https://chromium-review.googlesource.com/c/1463664 Reviewed-by: Danyao Wang <danyao@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Cr-Commit-Position: refs/heads/master@{#631791} -- wpt-commits: e6645a41093b3516eaa5bab63cd0ba65b3778a4e wpt-pr: 15332
e10cfd0d9d60429e61c583a7e4a326962420161a: Bug 1527669 [wpt PR 15358] - HTML: make <a>'s rel setter test work, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Tue, 05 Mar 2019 11:12:10 +0000 - rev 522419
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527669 [wpt PR 15358] - HTML: make <a>'s rel setter test work, a=testonly Automatic update from web-platform-tests HTML: make <a>'s rel setter test work -- wpt-commits: d1f77cdd373524b0f348e47464ced3cfda7ca05b wpt-pr: 15358
7ef3ea73361d89af4b57f70f0710acb2a263ad69: Bug 1528109 [wpt PR 15363] - Correct format string in logging messages, a=testonly
jugglinmike <mike@mikepennisi.com> - Tue, 05 Mar 2019 11:12:08 +0000 - rev 522418
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1528109 [wpt PR 15363] - Correct format string in logging messages, a=testonly Automatic update from web-platform-tests Correct format string in logging messages (#15363) -- wpt-commits: c18a2a49589f9cac44270f2daee298a79989951c wpt-pr: 15363
ba63a52c10157ccfeec051a6aef6c21c1b87babb: Bug 1527560 [wpt PR 15348] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 14 Feb 2019 20:39:36 +0000 - rev 522417
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527560 [wpt PR 15348] - Update wpt metadata, a=testonly wpt-pr: 15348 wpt-type: metadata
f61a049759af467cdad157d0827d0b9f30178ee7: Bug 1527560 [wpt PR 15348] - Implement `Sec-Fetch-Mode`, a=testonly
Mike West <mkwst@chromium.org> - Tue, 05 Mar 2019 11:11:53 +0000 - rev 522416
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527560 [wpt PR 15348] - Implement `Sec-Fetch-Mode`, a=testonly Automatic update from web-platform-tests Implement `Sec-Fetch-Mode` This patch implements `Sec-Fetch-Mode`, which adds the current CORS mode to outgoing, secure requests, as defined in https://mikewest.github.io/sec-metadata/#sec-fetch-mode-header. Bug: 843478 Change-Id: I811bfa86bdac1600b8abdd275d9526f6408e62e2 Reviewed-on: https://chromium-review.googlesource.com/c/1466362 Reviewed-by: Camille Lamy <clamy@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#631651} -- wpt-commits: 86bfe06b7260f552913b3274c30377ce7e9968b8 wpt-pr: 15348
9bb616490c7c600f6d29e82360447f4d8b6a8867: Bug 1526836 [wpt PR 15296] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 14 Feb 2019 14:38:17 +0000 - rev 522415
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1526836 [wpt PR 15296] - Update wpt metadata, a=testonly wpt-pr: 15296 wpt-type: metadata
41177907128bdc7babb664a503c90d36fc842f0d: Bug 1526836 [wpt PR 15296] - Implement `navigator.getUserAgent()`, a=testonly
Mike West <mkwst@chromium.org> - Tue, 05 Mar 2019 11:11:39 +0000 - rev 522414
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1526836 [wpt PR 15296] - Implement `navigator.getUserAgent()`, a=testonly Automatic update from web-platform-tests Implement `navigator.getUserAgent()` This patch is smaller than it looks. It basically does the following: 1. It introduces `blink::UserAgentMetadata`, and a corresponding mojo type in order to hold the various shards of data we'd like to expose about user agents (brand, version, platform, architecture, and model). 2. It threads these new types down from //chrome and //content/shell's implementations of `ContentBrowserClient` down into Blink via the same route we're using for the existing user-agent string (ChromeContentBrowserClient -> RenderProcessHost -> RenderThread -> Platform -> LocalFrameClient -> FrameLoader). 3. It extends `Navigator` with a new `NavigatorUserAgent` mixin that exposes `navigator.getUserAgent()`. This returns a promise that resolves with a newly defined `UserAgent` IDL dictionary type. So, the patch is huge, but not really that complex. Bug: 928670 Change-Id: I4f267e373864162264ad4d721650942b147b378d Reviewed-on: https://chromium-review.googlesource.com/c/1458098 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#631613} -- wpt-commits: 290e4d77cd6418cf7b37351549c1ed2e5c62f557 wpt-pr: 15296
2e35ac1f3c2141c3986777b67b155216346bb028: Bug 1527540 [wpt PR 15343] - domparsing: Fix an issue that XMLSerializer generates new prefix for an attribute with an existing namespace, a=testonly
Kent Tamura <tkent@chromium.org> - Tue, 05 Mar 2019 11:11:22 +0000 - rev 522413
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527540 [wpt PR 15343] - domparsing: Fix an issue that XMLSerializer generates new prefix for an attribute with an existing namespace, a=testonly Automatic update from web-platform-tests domparsing: Fix an issue that XMLSerializer generates new prefix for an attribute with an existing namespace Add an implementation of "retrieving a preferred prefix string" [1], and apply it to attribute serialization. As the specification defines, this CL introduces another map [2] like: namespace URI => [older prefix, ..., newer prefix] in order to retrieve most-recently-declared prefix. When we search the map for a prefix, we check availability of the prefix by the existing prefix-namespace map. There are two failing test cases in XMLSerializer-serializeToString.html. They follow the specification. * The first failing one: An non-well-formed XML is produced if we follow the specification. Chrome's new behavior matches to Firefox. Safari also produces a bad XML. * The second failing one: Firefox, Safari, and Chrome without this CL preserve prefix in such case. This CL keeps the interoperable behavior. [1] https://w3c.github.io/DOM-Parsing/#dfn-retrieving-a-preferred-prefix-string [2] https://w3c.github.io/DOM-Parsing/#dfn-namespace-prefix-map Bug: 906807 Change-Id: Idaea590ba19c9c21acbaf456ea91ce550c74db5a Reviewed-on: https://chromium-review.googlesource.com/c/1445033 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Auto-Submit: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#631573} -- wpt-commits: 2647e1e8f6995d12f44edbf0b4fce752e5cb7ec5 wpt-pr: 15343
5ed7c1d98107bfd6ad021d706e1b09c3a3b4ac82: Bug 1527643 [wpt PR 15197] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 14 Feb 2019 14:27:51 +0000 - rev 522412
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527643 [wpt PR 15197] - Update wpt metadata, a=testonly wpt-pr: 15197 wpt-type: metadata
c20dbdb5add0eb1406a7bdb90e3a968616a7d23e: Bug 1527643 [wpt PR 15197] - Add tentative WPT tests for Built-in Module Infra and Import Maps, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Tue, 05 Mar 2019 11:11:07 +0000 - rev 522411
Push 10871 by cbrindusan@mozilla.com at Mon, 18 Mar 2019 15:49:32 +0000
Bug 1527643 [wpt PR 15197] - Add tentative WPT tests for Built-in Module Infra and Import Maps, a=testonly Automatic update from web-platform-tests Add tentative WPT tests for Built-in Module Infra and Import Maps Bug: 848607, 927477, 928435 Change-Id: Id0573736a762c26df28f32da0716d94a566cfce3 Reviewed-on: https://chromium-review.googlesource.com/c/1449072 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#631546} -- wpt-commits: 896ca12d8a73e7679ef3a4c7402301a5603b5faa wpt-pr: 15197
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip