3956ac50444ce8efc28e7667ffe21a545eb1fb22: Bug 1503238 [wpt PR 13781] - [webdriver]: add checks for execute_script tests recognising promises, a=testonly
Christian Bromann <github@christian-bromann.com> - Tue, 13 Nov 2018 11:52:53 +0000 - rev 502717
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503238 [wpt PR 13781] - [webdriver]: add checks for execute_script tests recognising promises, a=testonly Automatic update from web-platform-testswebdriver add promise tests for execute_script (#13781) -- wpt-commits: cb1b82ae9314fade8ea8796aafd9c2fc409c3b4a wpt-pr: 13781
ce2b0b7cf4dd943548c605a79d449a4f6a3623df: Bug 1504935 [wpt PR 13941] - ServiceWorker: Modernize clients-matchall-include-uncontrolled.https.html using async/await, a=testonly
Hiroki Nakagawa <nhiroki@chromium.org> - Tue, 13 Nov 2018 11:52:51 +0000 - rev 502716
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504935 [wpt PR 13941] - ServiceWorker: Modernize clients-matchall-include-uncontrolled.https.html using async/await, a=testonly Automatic update from web-platform-testsServiceWorker: Modernize clients-matchall-include-uncontrolled.https.html using async/await Bug: 902201 Change-Id: Ib9fd5a5f0e9cc49cf653b6af768d00912c008deb Reviewed-on: https://chromium-review.googlesource.com/c/1319392 Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#605617} -- wpt-commits: 4c3ee3da47cafa07a045d99a2bca8a3ef688b1b3 wpt-pr: 13941
5d88abd3b62451df0802a115ede2367b694fc376: Bug 1504870 [wpt PR 13933] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 06 Nov 2018 03:13:38 +0000 - rev 502715
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504870 [wpt PR 13933] - Update wpt metadata, a=testonly wpt-pr: 13933 wpt-type: metadata
bd972083f3873bc87a81f502a280c9e15d97f0c1: Bug 1504870 [wpt PR 13933] - Change the button type to int in the pointerActionSequence API, a=testonly
Lan Wei <lanwei@chromium.org> - Tue, 13 Nov 2018 11:52:46 +0000 - rev 502714
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504870 [wpt PR 13933] - Change the button type to int in the pointerActionSequence API, a=testonly Automatic update from web-platform-testsChange the button type to int in the pointerActionSequence API In order to match with test_driver Actions API, we need to change the button type from string to int in the pointerActionSequence API and the related web platform tests and layout tests. Bug: 893480 Change-Id: I151849d31038cf40a2a603196e0f616e15d89072 Reviewed-on: https://chromium-review.googlesource.com/c/1297637 Commit-Queue: Lan Wei <lanwei@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#605605} -- wpt-commits: 41f76e27e00de380d5a100aa0c1065fa202e9c0a wpt-pr: 13933
82ada3c9b3a1f099818a1a02ab70360fc6081e1c: Bug 1504850 [wpt PR 13930] - Fix css-values/vh-support-margin.html, a=testonly
Francois Remy <frremy@microsoft.com> - Tue, 13 Nov 2018 11:52:44 +0000 - rev 502713
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504850 [wpt PR 13930] - Fix css-values/vh-support-margin.html, a=testonly Automatic update from web-platform-testsFix css-values/vh-support-margin.html -- wpt-commits: f77ee36ba4f40d99d3de090df01cfeb503065f6d wpt-pr: 13930
de65f79e9beac671dac641c415ebb8e9bba5912d: Bug 1502991 [wpt PR 13764] - Make XR FrameData and Environment mojo associated, a=testonly
Max Rebuschatis <lincolnfrog@chromium.org> - Tue, 13 Nov 2018 11:52:42 +0000 - rev 502712
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1502991 [wpt PR 13764] - Make XR FrameData and Environment mojo associated, a=testonly Automatic update from web-platform-testsMake XR FrameData and Environment mojo associated The XRFrameDataProvider now returns an associated XREnvironmentDataProvider interface so that the two share callback queues and thus allow strict ordering of the two interfaces. This is critical for frame synchronization between frames and the associated environment data. Note: We can't just mark the interfaceptrs for XRFrameDataProvider and XREnvironmentIntegrationProvider as associated in the XRSession struct. XRDevice implementations mostly live on separate threads from the XRFrameDataProviders, so we'd have extra thread hopping. For the VR headsets we explicitly live off the main thread to avoid latency, and because we do some work that may block the thread the XRFrameDataProvider lives on (for example waiting for vsync, or submitting frames to headset APIs). Bug: 867057, 876135, 843376 Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30 Reviewed-on: https://chromium-review.googlesource.com/c/1171794 Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Bill Orr <billorr@chromium.org> Reviewed-by: Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#605545} -- wpt-commits: 2ba8053bfa3946457355fa73d2873144fe4479d2 wpt-pr: 13764
f8bb87bd2f022dc4d30940aff9cdd74aa9c75e79: Bug 1504132 [wpt PR 13855] - Move getDisplayMedia to MediaDevices, a=testonly
Emircan Uysaler <emircan@chromium.org> - Tue, 13 Nov 2018 11:52:35 +0000 - rev 502711
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504132 [wpt PR 13855] - Move getDisplayMedia to MediaDevices, a=testonly Automatic update from web-platform-testsMove getDisplayMedia to MediaDevices Following https://github.com/w3c/mediacapture-screen-share/pull/86 Bug: 326740 Change-Id: Ifb65a33a7f998563640d9f508d26d91ecb16c32f -- wpt-commits: 032cd9cc630759609a901e37e158575fd265d353 wpt-pr: 13855
564d985f24d302a08470a8cd3b4bf7abd1c46747: Bug 1504593 [wpt PR 13912] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 05 Nov 2018 05:52:05 +0000 - rev 502710
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504593 [wpt PR 13912] - Update wpt metadata, a=testonly wpt-pr: 13912 wpt-type: metadata
294cee3a2512e9e065ba7f81eddb76304d2b8c51: Bug 1504593 [wpt PR 13912] - Redefine semantics of canMakePayment(), a=testonly
Marcos Cáceres <marcos@marcosc.com> - Tue, 13 Nov 2018 11:52:30 +0000 - rev 502709
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504593 [wpt PR 13912] - Redefine semantics of canMakePayment(), a=testonly Automatic update from web-platform-testsRedefine semantics of canMakePayment() (#13912) -- wpt-commits: c39c5a282ed46651faf0722961a89f8fc1f48a71 wpt-pr: 13912
bcab26cd215e82351a57aa54a17f68956192f35a: Bug 1504676 [wpt PR 13919] - Cope even better with the mess we leave behind after a continuation., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Tue, 13 Nov 2018 11:52:28 +0000 - rev 502708
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504676 [wpt PR 13919] - Cope even better with the mess we leave behind after a continuation., a=testonly Automatic update from web-platform-testsCope even better with the mess we leave behind after a continuation. Tried to fix this in https://chromium-review.googlesource.com/c/1309777 but incorrectly assumed that bogus continuation chains were formed by direct siblings. But they may also be arbitrary-level cousins. Need to walk through all non-atomic inlines between one continuation object and the next in the chain, to figure out whether there is an anonymous block between two objects in the continuation chain. Only then should we update the positionedness of anonymous blocks. Only perform this check if positionedness changed, since it's not for free. Bug: 901598 Change-Id: I3e49a4ce8081a4a3190cc1569480189cbcccdcc4 Reviewed-on: https://chromium-review.googlesource.com/c/1317627 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#605465} -- wpt-commits: fb4466fa28e359a770f6d7007a2a1302fec0c8a2 wpt-pr: 13919
15642a5e106d104d35ccb2c415fa56494f05a832: Bug 1501941 [wpt PR 13717] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Thu, 25 Oct 2018 09:22:01 +0000 - rev 502707
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1501941 [wpt PR 13717] - Update wpt metadata, a=testonly wpt-pr: 13717 wpt-type: metadata
e9425a9e1f4531babd4901b7340aba32900dc56c: Bug 1501941 [wpt PR 13717] - Correct inherited feature policy when allow attribute is used., a=testonly
Ian Clelland <iclelland@chromium.org> - Tue, 13 Nov 2018 11:52:23 +0000 - rev 502706
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1501941 [wpt PR 13717] - Correct inherited feature policy when allow attribute is used., a=testonly Automatic update from web-platform-testsCorrect inherited feature policy when allow attribute is used. This fixes an error in the inherited policy calculation where a frame which was explicitly allowed to use a feature through the Feature-Policy header would be blocked if the "allow" attribute was also present on the iframe element. The behaviour now matches the spec algorithm at https://wicg.github.io/feature-policy/#define-inherited-policy-in-container Tests have been added to catch this case. Change-Id: I7a394202c615be3088fda738d7fc65f16bcadf34 Reviewed-on: https://chromium-review.googlesource.com/c/1293610 Reviewed-by: Luna Lu <loonybear@chromium.org> Commit-Queue: Ian Clelland <iclelland@chromium.org> Cr-Commit-Position: refs/heads/master@{#605431} -- wpt-commits: d5f4dec283def0baeca6e5a88223dac67935e798 wpt-pr: 13717
650e078e8d5a2bdae5a3ce16fa5122c5b0f25c6b: Bug 1504631 [wpt PR 13917] - CSS: serialize pointer-events keywords in lower case, a=testonly
Zhuoyu Qian <zhuoyu.qian@samsung.com> - Tue, 13 Nov 2018 11:52:21 +0000 - rev 502705
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504631 [wpt PR 13917] - CSS: serialize pointer-events keywords in lower case, a=testonly Automatic update from web-platform-testsCSS: serialize pointer-events keywords in lower case https://drafts.csswg.org/cssom/#serializing-css-values "To serialize a CSS component value depends on the component, as follows: keyword The keyword converted to ASCII lowercase." Bug: 901666 Change-Id: Iff579a363de13441c75bbebfc951095b071f6060 Reviewed-on: https://chromium-review.googlesource.com/c/1317300 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by: Eric Willigers <ericwilligers@chromium.org> Reviewed-by: Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#605383} -- wpt-commits: f917e2dfc6649f9217f51dec9fd45eaef16188fc wpt-pr: 13917
bf112b4f198168fcb8c57e87e3a742ece5bfb272: Bug 1503567 [wpt PR 13811] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 31 Oct 2018 21:43:22 +0000 - rev 502704
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503567 [wpt PR 13811] - Update wpt metadata, a=testonly wpt-pr: 13811 wpt-type: metadata
63ad931acb1aa83c17251b208bdf5e9e56ce0fcd: Bug 1503567 [wpt PR 13811] - Update interfaces/screen-capture.idl, a=testonly
Automat af Gränssnitt <auto@foolip.org> - Tue, 13 Nov 2018 11:52:16 +0000 - rev 502703
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503567 [wpt PR 13811] - Update interfaces/screen-capture.idl, a=testonly Automatic update from web-platform-testsUpdate interfaces/screen-capture.idl Source: https://github.com/tidoust/reffy-reports/blob/825f02d/whatwg/idl/screen-capture.idl Build: https://travis-ci.org/tidoust/reffy-reports/builds/448699564 -- wpt-commits: 88d1eb8e58767c9387e8414977f47753d8eafaea wpt-pr: 13811
ff4f2d61936d7378afc6bd81fae11f668fac1c1a: Bug 1504467 [wpt PR 13888] - Add requirements_flake8.txt to .pyup.yml, a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 13 Nov 2018 11:52:14 +0000 - rev 502702
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504467 [wpt PR 13888] - Add requirements_flake8.txt to .pyup.yml, a=testonly Automatic update from web-platform-testsSort .pyup.yml list -- Add requirements_flake8.txt to .pyup.yml -- wpt-commits: b5243d6c3e0ea8f8c4695a94a801cd4ec39654e9, b3dd8fa1d7ad9c284abf77a1fb0d600116610e0f wpt-pr: 13888
617ea28eb87ea4ae9e183eedac5a27a180f32046: Bug 1504397 [wpt PR 13875] - Enable flake8 for py3 again, a=testonly
Philip Jägenstedt <philip@foolip.org> - Tue, 13 Nov 2018 11:52:12 +0000 - rev 502701
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504397 [wpt PR 13875] - Enable flake8 for py3 again, a=testonly Automatic update from web-platform-testsEnable flake8 for py3 again (#13875) This was accidentally dropped in https://github.com/web-platform-tests/wpt/pull/13865. Splitting flake8.ini into two is a bit unfortunate, but after trimming to just the errors and warnings that are hit, they differ a bit. Unfortunately using `--append-config` twice doesn't work. -- wpt-commits: ba70a57943fae3d69055b1c91b083e0d46d1067d wpt-pr: 13875
515a5e1b371a16a2637327bdb1b43b3a19aeb82a: Bug 1501380 [wpt PR 13685] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Tue, 23 Oct 2018 23:45:44 +0000 - rev 502700
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1501380 [wpt PR 13685] - Update wpt metadata, a=testonly wpt-pr: 13685 wpt-type: metadata
a5903021d8d0156a0daae195384d8f4972840c57: Bug 1501380 [wpt PR 13685] - SPV event should have some required init fields, a=testonly
Andy Paicu <andypaicu@chromium.org> - Tue, 13 Nov 2018 11:52:07 +0000 - rev 502699
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1501380 [wpt PR 13685] - SPV event should have some required init fields, a=testonly Automatic update from web-platform-testsSPV event should have some required init fields Spec: https://w3c.github.io/webappsec-csp/#dictdef-securitypolicyviolationeventinit Bug: 897646 Change-Id: Id4c4947455a095c09aa34d16c7ff298ba4ba046e Reviewed-on: https://chromium-review.googlesource.com/c/1292566 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#605300} -- wpt-commits: 33640efd70eaad4a6b482b98bd4e433d49934a50 wpt-pr: 13685
6547d97535b1aff9a1e8d15bb119cce10cc309bc: Bug 1502370 [wpt PR 13735] - Ensure eval flag is properly transfered to context from CSPRO, a=testonly
Andy Paicu <andypaicu@chromium.org> - Tue, 13 Nov 2018 11:52:04 +0000 - rev 502698
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1502370 [wpt PR 13735] - Ensure eval flag is properly transfered to context from CSPRO, a=testonly Automatic update from web-platform-testsEnsure eval flag is properly transfered to context from CSPRO When setting the eval flag for a worker context, report only policies were treated as enforcing. Because AllowEval with supress reporting does not take into account the ReportOnly state of the policy because it calls CheckEval directly. AllowEval: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/frame/csp/content_security_policy.cc?g=0&l=603 CheckEval is called here: https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/frame/csp/csp_directive_list.cc?g=0&l=712 Bug: 777076 Change-Id: I80994553037d29c9301aff1ea845386c776c6837 Reviewed-on: https://chromium-review.googlesource.com/c/1301439 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#605289} -- wpt-commits: 7e66d13f9ca425be0a2891f080a2e473c5d6cf24 wpt-pr: 13735
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip