25bca619e8e030896a6f2ebdc56acd1aa3aa1596: Bug 1439548 [wpt PR 9585] - Update supported font format specifiers, a=testonly
Dominik Röttsches <drott@chromium.org> - Mon, 26 Mar 2018 12:34:51 +0000 - rev 467111
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439548 [wpt PR 9585] - Update supported font format specifiers, a=testonly Automatic update from web-platform-testsUpdate supported font format specifiers While we do support variations, our format specifier support was not updated yet. Move all of that to FontCustomPlatformData and add a WPT test to cover common supported format specifiers. Test: external/wpt/css/css-fonts/format-specifiers-variations.html Bug: 804466 Change-Id: I06d7af65cf74e13cec49dc279efb8ffc2b56dda9 Reviewed-on: https://chromium-review.googlesource.com/926007 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#537799} wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c wpt-pr: 9585 wpt-commits: ee2e2949929d0d371404ec5a3a7bb2873f44b34c wpt-pr: 9585
df90f80286f147dd30a7e9c616650fdb7c7699da: Bug 1439612 [wpt PR 9587]- Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 20 Feb 2018 17:28:58 +0000 - rev 467110
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439612 [wpt PR 9587]- Update wpt metadata, a=testonly wpt-pr: 9587 wpt-type: metadata
9a0f47ccd297198e1563b507347096a8813e70ac: Bug 1439612 [wpt PR 9587] - Fix #8954: update wptrunner requirements, a=testonly
Geoffrey Sneddon <me@gsnedders.com> - Mon, 26 Mar 2018 12:34:16 +0000 - rev 467109
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439612 [wpt PR 9587] - Fix #8954: update wptrunner requirements, a=testonly Automatic update from web-platform-testsFix #8954: update wptrunner requirements Note this just uses the current stable release of all dependencies rather than trying to find what the minimum required actually is. -- Pin wptrunner dependencies Given it's an application, we should just define the environment we expect it to run in. This should stop #8954 from regressing, given it also means we'll be testing against the only possible set of versions of our dependencies. wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb wpt-pr: 9587 wpt-commits: 25f040e64a77219f8e5bde319adc8561d5750823, d936893f3ce7e2530994f8df62799d17cbd56dfb wpt-pr: 9587
9ec13701e6d895229325e0b2606d583f4debdc8b: Bug 1438529 [wpt PR 9539]- Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 28 Feb 2018 11:41:54 +0000 - rev 467108
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438529 [wpt PR 9539]- Update wpt metadata, a=testonly wpt-pr: 9539 wpt-type: metadata
3449fae574053483fba883d8e0a20c4376f0e39e: Bug 1438529 [wpt PR 9539] - OOR-CORS: Port WebCORSPreflightResultCacheItem to network service, a=testonly
Takashi Toyoshima <toyoshim@chromium.org> - Mon, 26 Mar 2018 12:33:40 +0000 - rev 467107
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438529 [wpt PR 9539] - OOR-CORS: Port WebCORSPreflightResultCacheItem to network service, a=testonly Automatic update from web-platform-testsOOR-CORS: Port WebCORSPreflightResultCacheItem to network service This patch reimplements WebCORSPreflightResultCacheItem equivalent in network service, and share the implementation between the network service and Blink. The next patch will replace whole WebCORSPreflightResultCache, and this is the preparation to make the next patch small. Bug: 803766 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo Change-Id: Ifa06967830465236dbe198908062e1952095e55b Reviewed-on: https://chromium-review.googlesource.com/915543 Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Cr-Commit-Position: refs/heads/master@{#537769} wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53 wpt-pr: 9539 wpt-commits: de9d5d19b70d2d8b39a9e6f9006d0a2fb4f93f53 wpt-pr: 9539
104ac5d6d660aa6f06f57a424caed075b6783592: Bug 1439495 [wpt PR 9582] - Fix a bug that document.importNode() doesn't clone Attr nodes with namespace., a=testonly
Kent Tamura <tkent@chromium.org> - Mon, 26 Mar 2018 12:33:12 +0000 - rev 467106
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439495 [wpt PR 9582] - Fix a bug that document.importNode() doesn't clone Attr nodes with namespace., a=testonly Automatic update from web-platform-testsFix a bug that document.importNode() doesn't clone Attr nodes with namespace. We should just call Attr::Clone(). Bug: 812089, 812105 Change-Id: I163769e134a52d82b88834ae29083a01a3480e95 Reviewed-on: https://chromium-review.googlesource.com/925865 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#537730} wpt-commits: a5a46d493b6d3ebb7a214095549874af779f2ee0 wpt-pr: 9582 wpt-commits: a5a46d493b6d3ebb7a214095549874af779f2ee0 wpt-pr: 9582
5e40376b614281ae175f341e423d429bf914a560: Bug 1439476 [wpt PR 9579] - [css-typed-om] Implement StylePropertyMap.clear., a=testonly
Darren Shen <shend@chromium.org> - Mon, 26 Mar 2018 12:32:45 +0000 - rev 467105
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439476 [wpt PR 9579] - [css-typed-om] Implement StylePropertyMap.clear., a=testonly Automatic update from web-platform-tests[css-typed-om] Implement StylePropertyMap.clear. This patch adds the clear() method to inline & declared StylePropertyMap Spec: https://drafts.css-houdini.org/css-typed-om-1/#dom-stylepropertymap-clear Bug: 813653 Change-Id: Ib56f60fa59dc8d241e7fb1a7695fce2bea094026 Reviewed-on: https://chromium-review.googlesource.com/925761 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#537717} wpt-commits: 03384b28f145fcf905960ba5fd6af233c838859a wpt-pr: 9579 wpt-commits: 03384b28f145fcf905960ba5fd6af233c838859a wpt-pr: 9579
2392e916b17992539a87cbef54906365f0bb9bb3: Bug 1439475 [wpt PR 9577] - [css-typed-om] Allow mutations of CSSTransformValues., a=testonly
Naina Raisinghani <nainar@chromium.org> - Mon, 26 Mar 2018 12:32:17 +0000 - rev 467104
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439475 [wpt PR 9577] - [css-typed-om] Allow mutations of CSSTransformValues., a=testonly Automatic update from web-platform-tests[css-typed-om] Allow mutations of CSSTransformValues. This patch allows CSSTransformValues items to be mutated/appended. Spec issue here: https://github.com/w3c/css-houdini-drafts/issues/690 Bug: 545318 Change-Id: I841704e1f2ec8db0f27ae254a0949d4f9b46c8f7 Reviewed-on: https://chromium-review.googlesource.com/925882 Reviewed-by: Darren Shen <shend@chromium.org> Commit-Queue: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#537710} wpt-commits: ae41c0ef35473e9288b6caad44573c37d1f5ea9d wpt-pr: 9577 wpt-commits: ae41c0ef35473e9288b6caad44573c37d1f5ea9d wpt-pr: 9577
40f9ffb35059144bc280130ef479472de5a1cba5: Bug 1438744 [wpt PR 9554] - Delete StylePropertyMap.update(), a=testonly
Naina Raisinghani <nainar@chromium.org> - Mon, 26 Mar 2018 12:31:49 +0000 - rev 467103
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438744 [wpt PR 9554] - Delete StylePropertyMap.update(), a=testonly Automatic update from web-platform-testsDelete StylePropertyMap.update() This is as there is a bug on the spec highlighting the lack of usefulness of the function: https://github.com/w3c/css-houdini-drafts/issues/656 Bug: 812912 Change-Id: If0b47a4bfa268f55f63e5c80168971164dc63199 Reviewed-on: https://chromium-review.googlesource.com/923501 Commit-Queue: nainar <nainar@chromium.org> Reviewed-by: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#537697} wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025 wpt-pr: 9554 wpt-commits: 8f3f3d57d537c956eed62f78172325e97f093025 wpt-pr: 9554
323db1b627849f84cdd2db2c8f908393277bfe21: Bug 1444940 [wpt PR 9576] - cc Update messages.json expectations formatting, a=testonly
Michael[tm] Smith <mike@w3.org> - Mon, 26 Mar 2018 12:31:12 +0000 - rev 467102
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1444940 [wpt PR 9576] - cc Update messages.json expectations formatting, a=testonly Automatic update from web-platform-testscc Update messages.json expectations formatting wpt-commits: 1e4920885ba16ae3bed2b73668827adf4e5a4223 wpt-pr: 9576 wpt-commits: 1e4920885ba16ae3bed2b73668827adf4e5a4223 wpt-pr: 9576
2618adb9143793bed62609bbe12f803f7e605711: Bug 1439427 [wpt PR 9572] - [css-typed-om] Allow mutations of CSSUnparsedValue., a=testonly
Darren Shen <shend@chromium.org> - Mon, 26 Mar 2018 12:30:45 +0000 - rev 467101
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439427 [wpt PR 9572] - [css-typed-om] Allow mutations of CSSUnparsedValue., a=testonly Automatic update from web-platform-tests[css-typed-om] Allow mutations of CSSUnparsedValue. This patch allows CSSUnparsedValue items to be mutated/appended. See https://github.com/w3c/css-houdini-drafts/issues/664 Bug: 812919 Change-Id: I3e3c1d91fa9bfaa3a1a4adde45202c36c9bdb37f Reviewed-on: https://chromium-review.googlesource.com/923670 Reviewed-by: nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#537691} wpt-commits: 8fed98324bc133df221d778c62cbff210d43b0ce wpt-pr: 9572 wpt-commits: 8fed98324bc133df221d778c62cbff210d43b0ce wpt-pr: 9572
dd8bcdee8a6f8bf0eb2e0e03ca02bbd38d81cd46: Bug 1439276 [wpt PR 9567] - [css-typed-om] Fix crash involving negative length perspectives., a=testonly
Darren Shen <shend@chromium.org> - Mon, 26 Mar 2018 12:30:17 +0000 - rev 467100
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439276 [wpt PR 9567] - [css-typed-om] Fix crash involving negative length perspectives., a=testonly Automatic update from web-platform-tests[css-typed-om] Fix crash involving negative length perspectives. We were crashing because converting CSSPerspective(-1px) to a CSSValue returns nullptr. The correct behaviour should be to convert it as CSSPerspective(calc(-1px)). Bug: 812620 Change-Id: I5ee70d4fb5eed064bcdad67391c3eb84531144d6 Reviewed-on: https://chromium-review.googlesource.com/924742 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#537690} wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d wpt-pr: 9567 wpt-commits: 969ae697f67e35fb93c18fa36a57ff605a47256d wpt-pr: 9567
bff5e3749fa6b03398e823f503c4e547c54e2298: Bug 1439277 [wpt PR 9568] - [css-typed-om] Handle out-of-range values correctly., a=testonly
Darren Shen <shend@chromium.org> - Mon, 26 Mar 2018 12:29:49 +0000 - rev 467099
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439277 [wpt PR 9568] - [css-typed-om] Handle out-of-range values correctly., a=testonly Automatic update from web-platform-tests[css-typed-om] Handle out-of-range values correctly. Currently, when we set width to something like -1, we would get an invalid value for width. According to the spec [1], we should be wrapping the invalid value in a calc. This patch wraps invalid values in calc, and changes the test harness to allow us to test this. Bug: 545318 Change-Id: I71769e1bc69164c9b7dcf0d2c54ca06b623b5d9e Reviewed-on: https://chromium-review.googlesource.com/923603 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by: nainar <nainar@chromium.org> Cr-Commit-Position: refs/heads/master@{#537685} wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20 wpt-pr: 9568 wpt-commits: ca39b1ed0fa70e60bfbcbfe5be7e305b0e5c2d20 wpt-pr: 9568
bb54635f2c3e630b2b0318a5e3e6e88e2c6e1755: Bug 1439116 [wpt PR 9564] - Fix #7142: Change manifest update process, a=testonly
vedantc98 <vedantc98@gmail.com> - Mon, 26 Mar 2018 12:29:21 +0000 - rev 467098
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439116 [wpt PR 9564] - Fix #7142: Change manifest update process, a=testonly Automatic update from web-platform-testsFix #7142: Change manifest update process Earlier, interrupting the manifest-update could end up causing errors due to the non-atomicity of the process. Used tempfile to ensure that the file is written correctly. wpt-commits: 38612167f54c475836c122013756e92b9a8859cc wpt-pr: 9564 wpt-commits: 38612167f54c475836c122013756e92b9a8859cc wpt-pr: 9564
60a77117927046d22f2726308122a75c591df770: Bug 1439298 [wpt PR 9569] - Fix wpt/beacon/headers/header-content-type.html slowness, a=testonly
Yutaka Hirano <yhirano@chromium.org> - Mon, 26 Mar 2018 12:28:54 +0000 - rev 467097
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1439298 [wpt PR 9569] - Fix wpt/beacon/headers/header-content-type.html slowness, a=testonly Automatic update from web-platform-testsFix wpt/beacon/headers/header-content-type.html slowness This CL uses ResourceTiming API to speed up the test cases while avoiding flakiness. Bug: 779965 Change-Id: I40dc2fae470df296c87c12e432fc7fc7644cc40a Reviewed-on: https://chromium-review.googlesource.com/923625 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#537664} wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102 wpt-pr: 9569 wpt-commits: b20bddda8e47b046fc6ffccda4897cb81df14102 wpt-pr: 9569
a0b2073919aa48d8c1930426c3770e565a998e1f: Bug 1438018 [wpt PR 9501] - Test whether javascript: navigation aborts fetches in earlier navigation, a=testonly
Simon Pieters <zcorpan@gmail.com> - Mon, 26 Mar 2018 12:28:26 +0000 - rev 467096
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438018 [wpt PR 9501] - Test whether javascript: navigation aborts fetches in earlier navigation, a=testonly Automatic update from web-platform-testsTest whether javascript: navigation aborts fetches in earlier navigation See https://github.com/whatwg/html/issues/2590. Tentative tests for now. wpt-commits: be7c5e5b09e85fcfa05135b335ff4a815236b1b6 wpt-pr: 9501 wpt-commits: be7c5e5b09e85fcfa05135b335ff4a815236b1b6 wpt-pr: 9501
1e8c2a65cb940c10a8d5991d5b4539ad35415a4b: Bug 1438840 [wpt PR 9558]- Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 16 Feb 2018 15:11:17 +0000 - rev 467095
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438840 [wpt PR 9558]- Update wpt metadata, a=testonly wpt-pr: 9558 wpt-type: metadata
967fc8e815a484715b625c540a36024c186c8057: Bug 1438840 [wpt PR 9558] - Streams: Tests for abuse of RSBYOBRequest, a=testonly
Adam Rice <ricea@chromium.org> - Mon, 26 Mar 2018 12:27:51 +0000 - rev 467094
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438840 [wpt PR 9558] - Streams: Tests for abuse of RSBYOBRequest, a=testonly Automatic update from web-platform-testsStreams: Tests for abuse of RSBYOBRequest (#9558) In https://github.com/whatwg/streams/pull/870 it was made impossible to directly construct a ReadableStreamBYOBRequest. Prior to that it was possible to violate the state invariants of ReadableByteStreamController by constructing then using a BYOBRequest directly. Add tests that verify that it is not possible to construct a ReadableStreamBYOBRequest directly. Also add tests that it isn't possible to violate the invariants of ReadableByteStreamController by re-using a BYOBRequest object. Also add a test that it isn't possible to keep a BYOBRequest object valid while releasing the reader lock, as this would also be a way to violate ReadableByteStreamController's invariants. Fixes whatwg/streams#870 wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db wpt-pr: 9558 wpt-commits: abcd6e9aeb4267511740c45bf8e484b5ca1d95db wpt-pr: 9558
8e7a50052c03167179489c7bf1ad0f811a736bb5: Bug 1438785 [wpt PR 9556] - Refactor tests for sandbox iframes controlled by service worker, a=testonly
Makoto Shimazu <shimazu@chromium.org> - Mon, 26 Mar 2018 12:27:23 +0000 - rev 467093
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438785 [wpt PR 9556] - Refactor tests for sandbox iframes controlled by service worker, a=testonly Automatic update from web-platform-testsRefactor tests for sandbox iframes controlled by service worker This patch is to split sandboxed-iframe-fetch-event.https.html into small chunks. Each promise_test has smaller number of assertions, so that now we can see the results for each situation. Bug: 771815 Change-Id: I75cdd67f92bbb07d6b538b209e1f0819752c3bc8 Reviewed-on: https://chromium-review.googlesource.com/923901 Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#537606} wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989 wpt-pr: 9556 wpt-commits: 63a5a6d7c789f004f09e5cbb801b49cfb4426989 wpt-pr: 9556
d9e926e5f731819768d45bef3bcb828a4cdc77f4: Bug 1438478 [wpt PR 9536] - Stop reusing MemoryCache entries for requests with a different source origin., a=testonly
Takeshi Yoshino <tyoshino@chromium.org> - Mon, 26 Mar 2018 12:26:55 +0000 - rev 467092
Push 1728 by jlund@mozilla.com at Mon, 18 Jun 2018 21:12:27 +0000
Bug 1438478 [wpt PR 9536] - Stop reusing MemoryCache entries for requests with a different source origin., a=testonly Automatic update from web-platform-testsStop reusing MemoryCache entries for requests with a different source origin. ResourceFetcher/ResourceLoader now saves the result of the CORS check on the Resource object. Though the result of the CORS check varies depending on the source origin, reusing an existing resource fetched by a different source origin is allowed by mistake. This patch introduces a logic to prevent MemoryCache entries from being reused for requests with a different source (requestor) origin by saving the source origin on the Resource object and comparing that with the new source origin in Resource::CanReuse(), so that the result of the CORS check is reused only when the source origin is the same. An alternative possibly-better approach is to isolate MemoryCache for different origins by changing the cache identifier to take into account the source origin of requests. However, to keep the patch small and fix the issue quickly, this patch just prevents reuse. Bug: 799477, 809350 Change-Id: Ib96c9e728abe969a53f3d80519118a83392067b4 Reviewed-on: https://chromium-review.googlesource.com/897040 Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#537580} wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3 wpt-pr: 9536 wpt-commits: e6bda363d5bc9722b326631c36333d41101c0cb3 wpt-pr: 9536
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip