c19205f65af76eca2160873f3438561d1888ac4a: Bug 1507586 [wpt PR 14079] - Fetch: test no-cors Headers API better, a=testonly
Anne van Kesteren <annevk@annevk.nl> - Mon, 19 Nov 2018 18:46:10 +0000 - rev 447491
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507586 [wpt PR 14079] - Fetch: test no-cors Headers API better, a=testonly Automatic update from web-platform-testsFetch: test no-cors Headers API better For https://github.com/whatwg/fetch/pull/833. -- wpt-commits: ccb1c202a4ad83d88fe9bc133e2816b86e4bcfd2 wpt-pr: 14079
15de90ba7ca81e1b83c8b0f62b37c4ab5a5c68ca: Bug 1506089 [wpt PR 14002] - ServiceWorker: Add t.add_cleanup() in WPT tests., a=testonly
Asami Doi <d0iasm.pub@gmail.com> - Mon, 19 Nov 2018 18:46:03 +0000 - rev 447490
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1506089 [wpt PR 14002] - ServiceWorker: Add t.add_cleanup() in WPT tests., a=testonly Automatic update from web-platform-testsServiceWorker: Add t.add_cleanup() in WPT tests. This CL adds t.add_cleanup() that calls service_worker_unregister() in WPT tests to ensure registrations are removed on test completion. Bug: 824647 Change-Id: Ieb790d4d7f63fc4810f6062d7e288aad1e88f45d Reviewed-on: https://chromium-review.googlesource.com/c/1328545 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#608693} -- wpt-commits: ab42c6d20fe627c4580ca1f0d5f6fbd106cbe04f wpt-pr: 14002
b9b654151838eff7b4ac713fe0d08fe093a11041: Bug 1488424 [wpt PR 12826] - [SVG] Scripts are valid content for SVG+HTML, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Mon, 19 Nov 2018 18:46:01 +0000 - rev 447489
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1488424 [wpt PR 12826] - [SVG] Scripts are valid content for SVG+HTML, a=testonly Automatic update from web-platform-tests[SVG] Scripts are valid content for SVG+HTML (#12826) -- wpt-commits: 706ee77bda06b58f4e317bc317bc0e7c25d34f12 wpt-pr: 12826
47f01bb0b976c4d087b91f5d93ddb24f844d98fe: Bug 1507064 [wpt PR 14046] - Implement RTCQuicStream.waitForWriteBufferedAmountBelow(), a=testonly
Steve Anton <steveanton@chromium.org> - Mon, 19 Nov 2018 18:45:54 +0000 - rev 447488
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507064 [wpt PR 14046] - Implement RTCQuicStream.waitForWriteBufferedAmountBelow(), a=testonly Automatic update from web-platform-testsImplement RTCQuicStream.waitForWriteBufferedAmountBelow() Bug: 874296 Change-Id: I694325a0cc85ad520c18762e34ba05e2204e2c74 Reviewed-on: https://chromium-review.googlesource.com/c/1286902 Commit-Queue: Steve Anton <steveanton@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#608648} -- wpt-commits: d84cf823ac8a9bee7df5be37f4fafdbe218ab6a7 wpt-pr: 14046
c409ea7851c69dfa22240bc1e443afcf33468e22: Bug 1507080 [wpt PR 14048] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 14 Nov 2018 14:47:01 +0000 - rev 447487
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507080 [wpt PR 14048] - Update wpt metadata, a=testonly wpt-pr: 14048 wpt-type: metadata
9fb1d44b189576a641165e28f5fb0c75b5952d20: Bug 1507080 [wpt PR 14048] - service worker: Let register('data://blah') throw a TypeError, a=testonly
Amos Lim <eui-sang.lim@samsung.com> - Mon, 19 Nov 2018 18:45:50 +0000 - rev 447486
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507080 [wpt PR 14048] - service worker: Let register('data://blah') throw a TypeError, a=testonly Automatic update from web-platform-testsservice worker: Let register('data://blah') throw a TypeError register('data://blah') should throw a TypeError instead of SecurityError. If scopeURL’s scheme is not one of "http" and "https", reject promise with a TypeError and abort these steps.[1] [1]: https://w3c.github.io/ServiceWorker/#start-register-algorithm Bug: 877138 Change-Id: Ic1e8cae52ec9393152044aa37da389eb499165bb Reviewed-on: https://chromium-review.googlesource.com/c/1189688 Commit-Queue: Amos Lim <eui-sang.lim@samsung.com> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#608635} -- wpt-commits: 64ee30dc4f4c7cd5016ffcfbbb6e1012b978ed66 wpt-pr: 14048
65a2135472b542f302594c39593a7e8a8a52cb71: Bug 1507549 [wpt PR 14077] - Fix serialization of computed style for 'paint-order', a=testonly
Fredrik Söderquist <fs@opera.com> - Mon, 19 Nov 2018 18:45:48 +0000 - rev 447485
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507549 [wpt PR 14077] - Fix serialization of computed style for 'paint-order', a=testonly Automatic update from web-platform-testsFix serialization of computed style for 'paint-order' We were always serializing as the completed (all keywords present) form, which is not the shortest canonical form. https://svgwg.org/svg2-draft/painting.html#PaintOrder Fold the ComputedStyleUtils helper into the PaintOrder CSSProperty class, since this is very specific to this property. Matches WebKit and almost Gecko (which seems to handle some "two keyword" cases differently.) Bug: 904898 Change-Id: Ib796a111e601485e339fdf2739a587fb5f893b8a Reviewed-on: https://chromium-review.googlesource.com/c/1335579 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#608623} -- wpt-commits: 8ffe6b78eb915feefba921914f47c40b6f1880e6 wpt-pr: 14077
b5b203f13d4b19e7d907f11fedfe89fad54d2032: Bug 1506919 [wpt PR 14036] - Implement rejectionhandled event, a=testonly
CYBAI <cyb.ai.815@gmail.com> - Mon, 19 Nov 2018 18:45:45 +0000 - rev 447484
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1506919 [wpt PR 14036] - Implement rejectionhandled event, a=testonly Automatic update from web-platform-testsCheck including the error message from Error constructor as required -- wpt-commits: b4c61af0f410976b96279df7f75715091619057d wpt-pr: 14036
d366cf85ff776643dda946b0808dc1d1827dc802: Bug 1507660 [wpt PR 14084] - [UserTimingL3] Fix meature, mark API feature detection, a=testonly
Liquan(Max) Gu <maxlg@chromium.org> - Mon, 19 Nov 2018 18:45:43 +0000 - rev 447483
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507660 [wpt PR 14084] - [UserTimingL3] Fix meature, mark API feature detection, a=testonly Automatic update from web-platform-tests[UserTimingL3] Fix meature, mark API feature detection UserTimingL3 uses returned value for feature detection. If measure and mark API returns null, the APIs are L2 API; If the APIs return an entry, the APIs are L3 API. However, in the current implementation, when L3 API is enabled, the APIs do not always return the created entry. This CL is to fix this bug, and add layout tests to verify it. Change-Id: I9854f0abd0d64a3334701e09d6ce0fc245fcca3e Reviewed-on: https://chromium-review.googlesource.com/c/1338225 Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#608552} -- wpt-commits: a4efb68eb4bb30453a6c958ad58f8c2540dc967e wpt-pr: 14084
2589e6feb86ac62badb135d9634f055e0bd83924: Bug 1506716 [wpt PR 14026] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 12 Nov 2018 23:33:59 +0000 - rev 447482
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1506716 [wpt PR 14026] - Update wpt metadata, a=testonly wpt-pr: 14026 wpt-type: metadata
77b371d0cd7834a68f093fdd982d6f483c508fbf: Bug 1506716 [wpt PR 14026] - Adding more layout/WPT tests for backdrop-filter, a=testonly
Mason Freed <masonfreed@chromium.org> - Mon, 19 Nov 2018 18:45:38 +0000 - rev 447481
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1506716 [wpt PR 14026] - Adding more layout/WPT tests for backdrop-filter, a=testonly Automatic update from web-platform-testsAdding more layout/WPT tests for backdrop-filter These should reproduce (at least) these issues: - https://crbug.com/622128 - dark areas brought in from edges - https://crbug.com/632979 - dark areas brought in from edges - https://crbug.com/659501 - menus cause too much filtering - https://crbug.com/767997 - menus cause too much filtering - https://crbug.com/813796 - incorrect border used for filter - https://crbug.com/593307 - incorrect border used for filter Bug: 497522,622128,632979,659501,767997,813796,593307 Change-Id: Iafea2fc8fffba950f74d27f21170df647dc62e29 Reviewed-on: https://chromium-review.googlesource.com/c/1330888 Commit-Queue: Mason Freed <masonfreed@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#608537} -- wpt-commits: a2fb878b4b9e4164437357f2bfba4c28e8c0e1ea wpt-pr: 14026
a4f2948ebc5da670cc819dcb1852a767373c9ab3: Bug 1506886 [wpt PR 14034] - Keep animations running going to/from fullscreen., a=testonly
Rune Lillesveen <futhark@chromium.org> - Mon, 19 Nov 2018 18:45:36 +0000 - rev 447480
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1506886 [wpt PR 14034] - Keep animations running going to/from fullscreen., a=testonly Automatic update from web-platform-testsKeep animations running going to/from fullscreen. LazyReattachIfAttached() nukes the computed styles synchronously so that we are not able to keep animations alive for the next lifecycle update. Add a bit on Node to say that we need a forced layout tree reattach and trigger the re-attach from style recalc instead. Bug: 900162 Change-Id: I22f51f5e091932fc8a63213af88903c7866abbb4 Reviewed-on: https://chromium-review.googlesource.com/c/1333809 Reviewed-by: Robert Flack <flackr@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#608530} -- wpt-commits: 9fcbfa0a6c02e373780f897dcf5282907180e49a wpt-pr: 14034
5a02af0869cc9e135b62550ee653ca79d2af96e5: Bug 1505878 [wpt PR 13984] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 09 Nov 2018 00:03:43 +0000 - rev 447479
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1505878 [wpt PR 13984] - Update wpt metadata, a=testonly wpt-pr: 13984 wpt-type: metadata
91431840cca377524058fdd4715986ae537e67a8: Bug 1505878 [wpt PR 13984] - Add report-only mode to Feature Policy, a=testonly
Ian Clelland <iclelland@chromium.org> - Mon, 19 Nov 2018 18:45:31 +0000 - rev 447478
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1505878 [wpt PR 13984] - Add report-only mode to Feature Policy, a=testonly Automatic update from web-platform-testsAdd report-only mode to Feature Policy This change adds a "report-only" policy to each security context, which is local to that context (not replicated across processes) and is used to determine whether a report should be sent even if a feature is enabled, when the feature is used. Reports are now augmented with a "disposition" field, which is either "enforce", if the feature usage was actually blocked, or "report", if it was not. Feature policy directives are placed in the report-only policy if the feature name is suffixed with "-report-only", otherwise, they affect the regular (enforcing) policy. Explainer at https://github.com/WICG/feature-policy/blob/master/reporting.md Existing tests are updated, and new tests for report-only mode are added to ensure that reports are sent even when the feature is used successfully. Bug: 904878 Change-Id: I27bc42729c5ab5560160f3d993431e606a8a3a47 Reviewed-on: https://chromium-review.googlesource.com/c/1178811 Commit-Queue: Ian Clelland <iclelland@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#608004} -- wpt-commits: b39f5e0d0e0872cdd9b7592f0b9ff0b5c11bcef3 wpt-pr: 13984
1d062b58e9b47169735a582d0b3f853655a282ec: Bug 1507374 [wpt PR 14063] - [LongTasks] Change TaskAttributionTiming name to 'unknown', a=testonly
Nicolas Pena <npm@chromium.org> - Mon, 19 Nov 2018 18:45:29 +0000 - rev 447477
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507374 [wpt PR 14063] - [LongTasks] Change TaskAttributionTiming name to 'unknown', a=testonly Automatic update from web-platform-tests[LongTasks] Change TaskAttributionTiming name to 'unknown' At TPAC, we agreed that 'script' is confusing because it implies that longtasks only measure script work. Thus, we decided to change the name to 'unknown'. Also see https://github.com/w3c/longtasks/issues/47. Change-Id: I5a0666d0fa078bfeac8ab6e8397b9b51aca3e833 Reviewed-on: https://chromium-review.googlesource.com/c/1336367 Reviewed-by: Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#608479} -- wpt-commits: 4309ceb7b165a42534514ca9933846cc0912bdae wpt-pr: 14063
271c901b15036f82873bbd346c6030dce8d6752c: Bug 1507600 [wpt PR 14080] - Improve robustness of wpt animation interpolation tests., a=testonly
Kevin Ellis <kevers@chromium.org> - Mon, 19 Nov 2018 18:45:27 +0000 - rev 447476
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507600 [wpt PR 14080] - Improve robustness of wpt animation interpolation tests., a=testonly Automatic update from web-platform-testsImprove robustness of wpt animation interpolation tests. This patch fixes the problem where subtle changes to numerical values in matrix interpolation cause mismatches in the expected results. To address the issue: * Styles are checked to see if they are of the form matrix(...) or matrix3d(...). * If the style is a matrix, then arguments are rounded and the style is reconstructed. Bug: 797472 Change-Id: I44d6e0ed13e24dc2ecfeeacbcd4809d6dcdb6465 Reviewed-on: https://chromium-review.googlesource.com/c/1337640 Reviewed-by: Xida Chen <xidachen@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/master@{#608466} -- wpt-commits: 794b7ee9292f09802cd41e41a04be420b1d7bec3 wpt-pr: 14080
15344e2bbf8a82061d9c236343f8d8994aee08dc: Bug 1507345 [wpt PR 14062] - [css-flex] align-content should apply even when there's just a single line, a=testonly
Christian Biesinger <cbiesinger@chromium.org> - Mon, 19 Nov 2018 18:45:25 +0000 - rev 447475
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507345 [wpt PR 14062] - [css-flex] align-content should apply even when there's just a single line, a=testonly Automatic update from web-platform-tests[css-flex] align-content should apply even when there's just a single line In Jan 2015 the spec changed in https://drafts.csswg.org/css-flexbox/#change-201409-align-content-wrapping Change our code accordingly. This effectively reverts commit crrev.com/290823003 and relands crrev.com/2191683003 align-content-wrap-004 is a test for bug 641789, which was a regression from the previous attempt at landing this patch. Bug: 599828 Change-Id: I8de127c19203854922eb23a626cee4de9a772f22 Reviewed-on: https://chromium-review.googlesource.com/c/1323906 Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#608449} -- wpt-commits: 34ecd56f063821c113fd20bcb05b80aafd82d787 wpt-pr: 14062
446d46176729063c847603d3821ff1cfa0c59fa1: Bug 1507250 [wpt PR 14058] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 15 Nov 2018 02:09:57 +0000 - rev 447474
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507250 [wpt PR 14058] - Update wpt metadata, a=testonly wpt-pr: 14058 wpt-type: metadata
a83da6d08db05ded3959c548638583ccd5388f54: Bug 1507250 [wpt PR 14058] - Floats in a next fragmentainer may push lines down., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Mon, 19 Nov 2018 18:45:20 +0000 - rev 447473
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507250 [wpt PR 14058] - Floats in a next fragmentainer may push lines down., a=testonly Automatic update from web-platform-testsFloats in a next fragmentainer may push lines down. We cannot assume that when we push a line to the next fragmentainer (because it doesn't fit in the current one), the line is going to fit there. If the next fragmentainer has a float that nothing fits beside and the float is too tall to fit the line below it, we need to jump to yet another fragmentainer in order to find room for the line. Bug: 902762 Change-Id: Ied14694ed1ad4fc25d28527edd1ca7389f00664c Reviewed-on: https://chromium-review.googlesource.com/c/1335580 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#608414} -- wpt-commits: a218e2f1678badf75722fd444524d98cd5996b3f wpt-pr: 14058
bad0f7aa87afbea9f3bc26c6ede635855807a2fa: Bug 1507239 [wpt PR 14055] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 15 Nov 2018 01:29:42 +0000 - rev 447472
Push 110045 by james@hoppipolla.co.uk at Wed, 21 Nov 2018 14:01:55 +0000
Bug 1507239 [wpt PR 14055] - Update wpt metadata, a=testonly wpt-pr: 14055 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip