0c4f530017184bea5255ba74bab19db634e3e0ea: Bug 1523562 [wpt PR 14985] - Support document.referrer in SXG, a=testonly
Tsuyoshi Horo <horo@chromium.org> - Thu, 31 Jan 2019 18:59:27 +0000 - rev 457953
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14985] - Support document.referrer in SXG, a=testonly Automatic update from web-platform-tests Support document.referrer in SXG Before this CL, CreateRedirectInfo() in signed_exchange_loader.cc doesn't set redirect_info.new_referrer correctly. So document.referrer was always empty string after clicking a link of signed exchange. After this CL, CreateRedirectInfo() returns a RedirectInfo with new_referrer, so document.referrer will be set correctly. This CL introduces network::ResourceRequest argument in NavigationLoaderInterceptor::MaybeCreateLoaderForResponse(), PrefetchURLLoader, SignedExchangePrefetchHandler and SignedExchangeLoader. This value will be used to compute a correct RedirectInfo while handling the synthesized redirect for signed exchange. This CL uses "ignoreErrors" flag in generate-test-sxgs.sh while creating invalid signed exchange files. This flags was introduces by this change in webpackage repository. https://github.com/WICG/webpackage/commit/d3352199e0a074ef0ce4390232b861560d061425 Bug: 920905 Change-Id: I52a302d22c375b776874c996638b409cdcba8a9c Reviewed-on: https://chromium-review.googlesource.com/c/1415245 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#625094} -- wpt-commits: 5835a01f1f638f866215570119e88f9cac57e8c6 wpt-pr: 14985
492a748b9d5468661fc752fb138b08a2eba65011: Bug 1523562 [wpt PR 14903] - Always promote fixed and sticky positioned elements, if they stick to a scroller., a=testonly
Chris Harrelson <chrishtr@chromium.org> - Thu, 31 Jan 2019 18:59:25 +0000 - rev 457952
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14903] - Always promote fixed and sticky positioned elements, if they stick to a scroller., a=testonly Automatic update from web-platform-tests Always promote fixed and sticky positioned elements, if they stick to a scroller. Note that we will promote sticky-positioned elements even if the scroller is not composited. This allows us to remove a large amount of complex code having to do with ordering of decisions about compositing scroll vs the sticky-positioned element. Bug: 921242 Change-Id: I29d1ede06312325b1ee13c5b7d5d4987d7053d1e Reviewed-on: https://chromium-review.googlesource.com/c/1407922 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#624999} -- wpt-commits: bd951736b4d7dbfd862dfa0f27271b544e35ca30 wpt-pr: 14903
8dc4da778d4d153a0dc739683663e4766602761e: Bug 1523562 [wpt PR 14997] - Recalculate preferred widths on layout when necessary., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 31 Jan 2019 18:59:23 +0000 - rev 457951
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14997] - Recalculate preferred widths on layout when necessary., a=testonly Automatic update from web-platform-tests Recalculate preferred widths on layout when necessary. Some objects take the size of the containing block as input when calculating preferred inline-size, contrary to common sense; see the NeedsPreferredWidthsRecalculation() documentation in LayoutBox. In such cases we may need to recalculate the preferred inline-size as part of layout, even if no content inside changed. At the same time, we need to be careful not to do unnecessary work here. There is an optimization that just refuses to update preferred inline-size if it was already marked dirty, because the assumption then is that the preferred inline-size will in fact never be needed. This optimization caused trouble for the other optimization, which checks if the containing block also is a special object that needs this kind of preferred inline-size calculation as part of layout, because if it does, the idea is that the containing block will already have taken care of it as part of walking the subtree. The missing part here was to check if the containing block actually would calculate its preferred inline-size at all (or if it was skipped due the first optimization). Fixed that. Bug: 923568 Change-Id: I66064ee46de4769c9dc25d7ade727f6ccdc5d7c6 Reviewed-on: https://chromium-review.googlesource.com/c/1426677 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#624919} -- wpt-commits: 538eac8f698febbc6a4629b1269077ba0aff6c1b wpt-pr: 14997
dadb5e460082fd5532f43885e3331dbf380d1ab4: Bug 1523562 [wpt PR 14998] - Better fragmentation inside floats interrupted by spanners., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Thu, 31 Jan 2019 18:59:21 +0000 - rev 457950
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14998] - Better fragmentation inside floats interrupted by spanners., a=testonly Automatic update from web-platform-tests Better fragmentation inside floats interrupted by spanners. The current layout engine doesn't really handle this well, but we'll now look ahead for sibling column sets if the flow thread coordinate isn't contained by the current one. If we do this during layout, we then risk matching against flow thread boundaries from the previous layout pass, but that's really the best we can do. Also corrected a flow thread coordinate boundary check. page_boundary_rule == kAssociateWithFormerPage could actually hit the wrong column set because of an off-by-one comparison meant for page_boundary_rule == kAssociateWithLatterPage. Bug: 914912 Change-Id: I39a170da21e640154de141f30e363baa9f7c20ec Reviewed-on: https://chromium-review.googlesource.com/c/1425701 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#624914} -- wpt-commits: ca8756813e375d9743479b5f16a4066bbe034b05 wpt-pr: 14998
dc3f0a0a48a7691310298125769eb426b081def7: Bug 1523562 [wpt PR 15004] - [LayoutNG] Fix min/max size of atomic inlines with -ve margins., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Thu, 31 Jan 2019 18:59:19 +0000 - rev 457949
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 15004] - [LayoutNG] Fix min/max size of atomic inlines with -ve margins., a=testonly Automatic update from web-platform-tests [LayoutNG] Fix min/max size of atomic inlines with -ve margins. We were resolving %-margins during the min/max phase against LayoutUnit::Max(). This was bad. Now we explicitly set the percentage resolution sizes to zero. Bug: 923279 Change-Id: I619cef6ee2e4c18ad3a9bc213442a9a63a515e87 Reviewed-on: https://chromium-review.googlesource.com/c/1427539 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/master@{#624909} -- wpt-commits: 66202478658b87afab706f16e5835f0ae9073026 wpt-pr: 15004
00fc0cf059cdcaae2b264d24d8a13edd00211d0a: Bug 1523562 [wpt PR 14995] - Implement formdata event, a=testonly
CYBAI <cyb.ai.815@gmail.com> - Thu, 31 Jan 2019 18:59:17 +0000 - rev 457948
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14995] - Implement formdata event, a=testonly Automatic update from web-platform-tests Make a workaround for the test with about:blank onload As jdm mentioned in https://github.com/servo/servo/pull/22660#discussion_r249597546, the initial about:blank load event can be fired before the form navigation occurs. -- wpt-commits: c6fa4b6176b668287fef2d3ebdc54d5f992f7ca1 wpt-pr: 14995
1f6e65bcd4edccbf64a8b16829e2864c87033221: Bug 1523562 [wpt PR 15000] - Mark font-display feature policy tests as tentative, a=testonly
Yashar Dabiran <yashard@google.com> - Thu, 31 Jan 2019 18:59:15 +0000 - rev 457947
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 15000] - Mark font-display feature policy tests as tentative, a=testonly Automatic update from web-platform-tests Mark font-display feature policy tests as tentative * The feature is behind the "ExperimentalProductivityFeatures" flag Change-Id: I0a04cef9c7c10bcdd476a77c2d0ed28cc0a15f0a Reviewed-on: https://chromium-review.googlesource.com/c/1426144 Reviewed-by: Ian Clelland <iclelland@chromium.org> Commit-Queue: Yashar Dabiran <yashard@google.com> Cr-Commit-Position: refs/heads/master@{#624858} -- wpt-commits: c49631cfb6421835f50ee406d6b8478d1305be89 wpt-pr: 15000
0cdfd19c70f8e1ab650708e2cbf88777d32763be: Bug 1523562 [wpt PR 14973] - python3 de-linting, a=testonly
Refael Ackermann <refack@gmail.com> - Thu, 31 Jan 2019 18:59:11 +0000 - rev 457946
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14973] - python3 de-linting, a=testonly Automatic update from web-platform-tests python3 de-linting (#14973) xrange give a very very slight memory optimization but is incompatible with python3 -- wpt-commits: e4e6eeef32574aa928c8100a3c0d78b9129f5e86 wpt-pr: 14973
970d2e869999a3aae7f6245814b9fcc110e1fc98: Bug 1523562 [wpt PR 14989] - Update interfaces/css-pseudo.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 31 Jan 2019 18:59:09 +0000 - rev 457945
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14989] - Update interfaces/css-pseudo.idl, a=testonly Automatic update from web-platform-tests Update interfaces/css-pseudo.idl (#14989) Source: https://github.com/tidoust/reffy-reports/blob/8a0d273/whatwg/idl/css-pseudo.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/482751671 -- wpt-commits: 8564ea0c38b17a02f7b433933291202140fb76ab wpt-pr: 14989
acb8a28a0bb72cec4d10559d69223dbc4dde7639: Bug 1523562 [wpt PR 14991] - Update interfaces/pointerlock.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 31 Jan 2019 18:59:07 +0000 - rev 457944
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14991] - Update interfaces/pointerlock.idl, a=testonly Automatic update from web-platform-tests Update interfaces/pointerlock.idl (#14991) Source: https://github.com/tidoust/reffy-reports/blob/8a0d273/whatwg/idl/pointerlock.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/482751671 -- wpt-commits: 7aa7cc0d818afb22f338bf7db355a563d85c1c30 wpt-pr: 14991
708bc2182c357dd98da3b80035956cbf257a3a9d: Bug 1523562 [wpt PR 14990] - Update interfaces/picture-in-picture.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 31 Jan 2019 18:59:05 +0000 - rev 457943
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14990] - Update interfaces/picture-in-picture.idl, a=testonly Automatic update from web-platform-tests Update interfaces/picture-in-picture.idl (#14990) Source: https://github.com/tidoust/reffy-reports/blob/8a0d273/whatwg/idl/picture-in-picture.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/482751671 -- wpt-commits: 3ed3e070163bd165132913887da804d87da159c2 wpt-pr: 14990
d2652a6b3f77f3a7b4f663c53ab56d46ae936fb0: Bug 1523562 [wpt PR 14984] - SignedExchange: Reject uncached-headers, a=testonly
Kouhei Ueno <kouhei@chromium.org> - Thu, 31 Jan 2019 18:59:03 +0000 - rev 457942
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14984] - SignedExchange: Reject uncached-headers, a=testonly Automatic update from web-platform-tests SignedExchange: Reject uncached-headers This CL aligns the response header filter with the signed exchange spec update: https://github.com/WICG/webpackage/pull/339 Bug: 920897 Change-Id: I7819b560f4f7ec9d75145e74780ad0fd85008944 Reviewed-on: https://chromium-review.googlesource.com/c/1425842 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#624724} -- wpt-commits: 6f7e91a17cdd2f01105ccff43fc45a9db98507f3 wpt-pr: 14984
62f4234dae83d6e63d505fd2d38c9e0301f58985: Bug 1523562 [wpt PR 14143] - Update interfaces/web-bluetooth.idl, a=testonly
autofoolip <auto@foolip.org> - Thu, 31 Jan 2019 18:59:01 +0000 - rev 457941
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14143] - Update interfaces/web-bluetooth.idl, a=testonly Automatic update from web-platform-tests Update interfaces/web-bluetooth.idl (#14143) Source: https://github.com/tidoust/reffy-reports/blob/52b74b6/whatwg/idl/web-bluetooth.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/466372583 -- wpt-commits: df29f0e734ac60913d9f52d23097e188b7a651da wpt-pr: 14143
d36a6bc7d385b8a4e40efc92faa55796e93603ce: Bug 1523562 [wpt PR 14876] - SVG Interactivity: onwheel attribute, a=testonly
Eric Willigers <ewilligers@users.noreply.github.com> - Thu, 31 Jan 2019 18:58:59 +0000 - rev 457940
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14876] - SVG Interactivity: onwheel attribute, a=testonly Automatic update from web-platform-tests SVG Interactivity: onwheel attribute (#14876) * SVG Interactivity: onwheel attribute Test that script specified by the the onwheel attribute is run in response to mouse wheel events. https://github.com/w3c/svgwg/issues/627 * [svg] move test to svg/interact/manual -- wpt-commits: bdac00f5b982f0fa19d2c1cd91b373d83addde4e wpt-pr: 14876
2accf82c9d47991cb277f9087db9ef2e913afbb6: Bug 1523562 [wpt PR 14967] - WebShare: canShare() method in Level 2, a=testonly
Eric Willigers <ericwilligers@chromium.org> - Thu, 31 Jan 2019 18:58:57 +0000 - rev 457939
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14967] - WebShare: canShare() method in Level 2, a=testonly Automatic update from web-platform-tests WebShare: canShare() method in Level 2 canShare(data) returns false iff share(data) would reject with TypeError https://wicg.github.io/web-share/level-2/#canshare-method Intent to Implement: https://groups.google.com/a/chromium.org/d/msg/blink-dev/AiKgWvv3cq0/xAsjfSfMDQAJ Bug: 903010 Change-Id: I15e8a92a9d71b08da4e9e6d4bf2692c97dce5c0f Reviewed-on: https://chromium-review.googlesource.com/c/1351340 Commit-Queue: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Sam McNally <sammc@chromium.org> Reviewed-by: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#624658} -- wpt-commits: f5df77f83ba77088d354838b377eef5e3f770e36 wpt-pr: 14967
16070e332712930659b07b680ff0bba610c76297: Bug 1523562 [wpt PR 14851] - [ FeaturePolicy ] - Report for "legacy-image-formats", a=testonly
Ehsan Karamad <ekaramad@chromium.org> - Thu, 31 Jan 2019 18:58:56 +0000 - rev 457938
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14851] - [ FeaturePolicy ] - Report for "legacy-image-formats", a=testonly Automatic update from web-platform-tests [ FeaturePolicy ] - Report for "legacy-image-formats" This CL adds support for generating reports for violations of the "legacy-image-formats" feature policy. This also automatically starts counting the potential violations of this feature in web pages (Blink.UseCounter.FeaturePolicy.PotentialViolation). Bug: 915788 Change-Id: If72ec438b6038730907ac086bddd0c680cc60d97 Reviewed-on: https://chromium-review.googlesource.com/c/1409698 Reviewed-by: David Bokan <bokan@chromium.org> Reviewed-by: Ehsan Karamad <ekaramad@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#624657} -- wpt-commits: 0a63acfc690e69d0a4121469910a1ddfd05ce30f wpt-pr: 14851
d040100cca713dfb3df1e913acc5da091a0000db: Bug 1523562 [wpt PR 14982] - [Reland] Synthetic gestures wait on renderer ACK., a=testonly
David Bokan <bokan@chromium.org> - Thu, 31 Jan 2019 18:58:54 +0000 - rev 457937
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14982] - [Reland] Synthetic gestures wait on renderer ACK., a=testonly Automatic update from web-platform-tests [Reland] Synthetic gestures wait on renderer ACK. Currently, synthetic gestures invoke the "completed callback" as soon as the final gesture has been dispatched. This causes issues in client code, typically tests, that want to wait until the effects of a gesture are complete before sending further input or checking page state. This CL is the first step in a series of CLs to make this completion callback reliable. We add a new API in the renderer that resolves the completion callback once the input has been fully processed by the renderer. For now, this method just ACKs immediately but its implementation will be further fleshed out in a followup CL. Reland Node: This was reverted in https://crrev.com/d3d4d7c7480b4424a8d009194dd14405654843a4 due to causing failures on the LeakDetector bot. The leaks were a result of tests finishing before the synthetic gesture had completed. I've modified these tests (in wpt/pointerevents) to wait until the guesture is completed before finishing the test. TBR=dtapuska@chromium.org,rsesek@chromium.org,avi@chromium.org Bug: 902446 Change-Id: I6a6a517a719616b2536538686fa4d7b980f0b485 Reviewed-on: https://chromium-review.googlesource.com/c/1424219 Reviewed-by: David Bokan <bokan@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#624496} -- wpt-commits: 7703c45b553cfaca6e1b7b20981d13d06b7d43e9 wpt-pr: 14982
6f3a70401564461dd8366e89f81548633daf61c4: Bug 1523562 [wpt PR 14810] - SignedExchange: Migrate test cases to 1b3, a=testonly
Kouhei Ueno <kouhei@chromium.org> - Thu, 31 Jan 2019 18:58:52 +0000 - rev 457936
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1523562 [wpt PR 14810] - SignedExchange: Migrate test cases to 1b3, a=testonly Automatic update from web-platform-tests SignedExchange: Migrate test cases to 1b3 third_party/blink/web_tests/external/wpt/signed-exchange/sxg-head-request.tentative.html is no longer relevant, since 1b3 no longer have request method serialized. The request method in a 1b3 SXG is assumed to be always GET. Bug: 919414 Change-Id: I0f7ec3de66db70b9cc12af209b74a22a4187460c Reviewed-on: https://chromium-review.googlesource.com/c/1405156 Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#623604} -- wpt-commits: b604d66fb763cc20ce58848c6876a324a1498254 wpt-pr: 14810
1eb07b35e946b94912a3021be0107462c3a118e2: Bug 1517332 [wpt PR 14694] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 02 Jan 2019 20:49:05 +0000 - rev 457935
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1517332 [wpt PR 14694] - Update wpt metadata, a=testonly wpt-pr: 14694 wpt-type: metadata
0c92a84e66ce56c7bd45b96f1bd15aca2c425fb8: Bug 1517332 [wpt PR 14694] - Change web platform test with mouse inputs under "pinterevents/", a=testonly
Lan Wei <lanwei@chromium.org> - Thu, 31 Jan 2019 18:58:46 +0000 - rev 457934
Push 111763 by james@hoppipolla.co.uk at Thu, 07 Feb 2019 22:12:57 +0000
Bug 1517332 [wpt PR 14694] - Change web platform test with mouse inputs under "pinterevents/", a=testonly Automatic update from web-platform-tests Change web platform test with mouse inputs under "pinterevents/" Use test_driver Actions class in the web platform tests with mouse inputs in "pinterevents/" to simulate mouse inputs to make the tests pass on wpt serve. Bug: 606367 Change-Id: I2f00c3195fafb8bc600250631106cd9eabe79b90 Reviewed-on: https://chromium-review.googlesource.com/c/1383330 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#619697} -- wpt-commits: f4c7d842e879b63c1f6d40726e49cb178404f34b wpt-pr: 14694
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip