aaf66fd7660f92887f2be75fe8acebe1244bc6ca: Bug 1468946 [wpt PR 11525] - ES Modules: Set referrer for top-level module script in ModuleScriptLoader, a=testonly
Hiroki Nakagawa <nhiroki@chromium.org> - Fri, 06 Jul 2018 17:22:15 +0000 - rev 816521
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468946 [wpt PR 11525] - ES Modules: Set referrer for top-level module script in ModuleScriptLoader, a=testonly Automatic update from web-platform-testsES Modules: Set referrer for top-level module script in ModuleScriptLoader Before this CL, referrer for top-level module script is set in BaseFetchContext::AddAdditionalRequestHeaders() using ExecutionContext::GetOutgoingReferrer(). This works for documents, but doesn't for workers because this execution context is corresponding to "module map settings object", not "fetch client settings object". To fix this, this CL sets the referrer for top-level module script using "fetch client settings object" in ModuleScriptLoader as the spec defines. Change-Id: I0878b13febdae4ee2dc56c998e7f2c100e9c1ba7 Bug: 842553 Reviewed-on: https://chromium-review.googlesource.com/1102236 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#567937} -- wpt-commits: 561fbb9d097472b33de81436f19ea28d00b1dc14 wpt-pr: 11525
b431f227a27055736e45654319a27f30571af954: Bug 1467737 [wpt PR 11401] - Consolidate label conversion tests + add timeLog, a=testonly
Dominic Farolino <domfarolino@gmail.com> - Fri, 06 Jul 2018 17:20:58 +0000 - rev 816520
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1467737 [wpt PR 11401] - Consolidate label conversion tests + add timeLog, a=testonly Automatic update from web-platform-testsConsolidate console label conversion tests + add timeLog -- wpt-commits: 38ef0a35c3890876923fe96d34e5ebbb56c4e568 wpt-pr: 11401
2899040768eaf25db4dbbdd685bb28c17c4537d4: Bug 1468934 [wpt PR 11523] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 16 Jun 2018 13:19:14 +0000 - rev 816519
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468934 [wpt PR 11523] - Update wpt metadata, a=testonly wpt-pr: 11523 wpt-type: metadata
0db3f2ae681d47dd4303cfa570899e959470385e: Bug 1468934 [wpt PR 11523] - [Picture-in-Picture] Resolve with current window if video is pipElement., a=testonly
François Beaufort <beaufort.francois@gmail.com> - Fri, 06 Jul 2018 17:19:31 +0000 - rev 816518
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468934 [wpt PR 11523] - [Picture-in-Picture] Resolve with current window if video is pipElement., a=testonly Automatic update from web-platform-tests[Picture-in-Picture] Resolve with current window if video is pipElement. This make sures requestPictureInPicture is resolved with existing Picture-in-Picture window when video is already pictureInPictureElement. Bug: 806249 Change-Id: I16e3fc2e8e19c2b623e8d2518fe4672a2a16b756 Reviewed-on: https://chromium-review.googlesource.com/1101686 Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#567934} -- wpt-commits: d42d45d61ec7359908878063b126bb09814e22c6 wpt-pr: 11523
e2f393089662da340cfdec72af65c0168b7f4b88: Bug 1469210 [wpt PR 11542] - Revert "Floats and out-of-flow objects may not be adjacent to anonymous blocks.", a=testonly
Abhishek Arya <inferno@chromium.org> - Fri, 06 Jul 2018 17:18:11 +0000 - rev 816517
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1469210 [wpt PR 11542] - Revert "Floats and out-of-flow objects may not be adjacent to anonymous blocks.", a=testonly Automatic update from web-platform-testsRevert "Floats and out-of-flow objects may not be adjacent to anonymous blocks." This reverts commit 2394d0acf8bf0b0236b2646e4c823a57de7bd941. Reason for revert: Caused ClusterFuzz regressions - 853522, 853537, 853538, 853540. Original change's description: > Floats and out-of-flow objects may not be adjacent to anonymous blocks. > > Floats and out-of-flow objects need to be true layout siblings of the > inlines, or rendering will be wrong. This means that such objects should > never be siblings of anonymous blocks, but rather inside them. This > already works correctly for initial layout tree building, and also for > many DOM manipulations. However, code was missing to satisfy this > requirement if we removed a regular block that was a sibling of an > anonymous block and either a float or out-of-flow positioned object. > > This even caused a crash triggered by ruby code, which ended up mixing > inline and block children within the same container. That is not > allowed. This happened in the MoveAllChildrenIncludingFloatsTo() call > inside LayoutRubyBase::MoveBlockChildren(). Added a DCHECK to > MoveAllChildrenIncludingFloatsTo() (which could fail prior to this fix); > When moving children from one container to another, either both or none > of the containers must have inline children. > > Bug: 852640 > Change-Id: I51d3de12c73ddd07d6b4c1aa55221b4f92359ca7 > Reviewed-on: https://chromium-review.googlesource.com/1102690 > Reviewed-by: Emil A Eklund <eae@chromium.org> > Commit-Queue: Morten Stenshorne <mstensho@chromium.org> > Cr-Commit-Position: refs/heads/master@{#567882} TBR=eae@chromium.org,mstensho@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 852640 Change-Id: I0af60d9eac770f21b6a0fbeccf88bb43d5efd6fb Reviewed-on: https://chromium-review.googlesource.com/1103503 Reviewed-by: Abhishek Arya <inferno@chromium.org> Commit-Queue: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#567914} -- wpt-commits: f055233bad9aab52e77148f36b79ca4f34dfa822 wpt-pr: 11542
50c66d30e5b3ec06474ff71b7790abf03282eb95: Bug 1469043 [wpt PR 11535] - Floats and out-of-flow objects may not be adjacent to anonymous blocks., a=testonly
Morten Stenshorne <mstensho@chromium.org> - Fri, 06 Jul 2018 17:16:50 +0000 - rev 816516
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1469043 [wpt PR 11535] - Floats and out-of-flow objects may not be adjacent to anonymous blocks., a=testonly Automatic update from web-platform-testsFloats and out-of-flow objects may not be adjacent to anonymous blocks. Floats and out-of-flow objects need to be true layout siblings of the inlines, or rendering will be wrong. This means that such objects should never be siblings of anonymous blocks, but rather inside them. This already works correctly for initial layout tree building, and also for many DOM manipulations. However, code was missing to satisfy this requirement if we removed a regular block that was a sibling of an anonymous block and either a float or out-of-flow positioned object. This even caused a crash triggered by ruby code, which ended up mixing inline and block children within the same container. That is not allowed. This happened in the MoveAllChildrenIncludingFloatsTo() call inside LayoutRubyBase::MoveBlockChildren(). Added a DCHECK to MoveAllChildrenIncludingFloatsTo() (which could fail prior to this fix); When moving children from one container to another, either both or none of the containers must have inline children. Bug: 852640 Change-Id: I51d3de12c73ddd07d6b4c1aa55221b4f92359ca7 Reviewed-on: https://chromium-review.googlesource.com/1102690 Reviewed-by: Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#567882} -- wpt-commits: ab2182ad1005c11556cf3c0c1ee063d57d13f63e wpt-pr: 11535
21616f27a8b50b21164eb6f683a97c42a84620de: Bug 1467678 [wpt PR 11395] - Ignore preventDefault on wheel (vertical-scroll), a=testonly
Ehsan Karamad <ekaramad@chromium.org> - Fri, 06 Jul 2018 17:15:32 +0000 - rev 816515
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1467678 [wpt PR 11395] - Ignore preventDefault on wheel (vertical-scroll), a=testonly Automatic update from web-platform-testsIgnore preventDefault on wheel (vertical-scroll) This CL implements the logic required for enforcing 'vertical-scroll' (through feature policy) on frames where a preventing mouse wheel handler may block vertical scrolling. The CL essentially overwrites the value of dispatch type from mouse wheel handlers iff the suggested direction of scrolling is vertical. Bug: 611982 Change-Id: I15230f11f616d093b21984fe0b526d94dc62dada Reviewed-on: https://chromium-review.googlesource.com/1073729 Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Reviewed-by: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#567773} -- wpt-commits: de3ae39cb59880a8245431e7f09817a2a4dad1a3 wpt-pr: 11395
9d7cb14fef163d7ac26b7f173d437eb440e0ad74: Bug 1473870 [wpt PR 11533] - Include subset-tests.js correctly in encoding tests, a=testonly
Simon Pieters <zcorpan@gmail.com> - Fri, 06 Jul 2018 17:14:15 +0000 - rev 816514
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1473870 [wpt PR 11533] - Include subset-tests.js correctly in encoding tests, a=testonly Automatic update from web-platform-testsInclude subset-tests.js correctly in encoding tests Fixes #11531. -- wpt-commits: 102eb1797986d6ea96545ebf5cc3fe358ea5d3e7 wpt-pr: 11533
ff88b0b8d873d553173a87b7f7f8157408010488: Bug 1449557 [wpt PR 10211] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Wed, 16 May 2018 13:15:51 +0000 - rev 816513
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1449557 [wpt PR 10211] - Update wpt metadata, a=testonly wpt-pr: 10211 wpt-type: metadata
3e8b63087211005dc8ddb27a72c75f4b71c363e1: Bug 1449557 [wpt PR 10211] - Prevent sandboxed documents from reusing the default window, a=testonly
Andy Paicu <andypaicu@chromium.org> - Fri, 06 Jul 2018 17:12:53 +0000 - rev 816512
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1449557 [wpt PR 10211] - Prevent sandboxed documents from reusing the default window, a=testonly Automatic update from web-platform-testsPrevent sandboxed documents from reusing the default window Bug: 377995 Change-Id: Iff66c6d214dfd0cb7ea9c80f83afeedfff703541 Reviewed-on: https://chromium-review.googlesource.com/983558 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#567663} -- wpt-commits: dc7c5d6b7eeb1ed264c7487a40a3f0f82f02907f wpt-pr: 10211
ac884732a71c4ab488442d724cbcdbef8cc52277: Bug 1467894 [wpt PR 11433] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sat, 09 Jun 2018 04:57:41 +0000 - rev 816511
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1467894 [wpt PR 11433] - Update wpt metadata, a=testonly wpt-pr: 11433 wpt-type: metadata
edb47e5bdd214d8b25412ab1b8322f7f5d09ae23: Bug 1467894 [wpt PR 11433] - Add test for WebSocket HTTP Authentication, a=testonly
Adam Rice <ricea@chromium.org> - Fri, 06 Jul 2018 17:11:30 +0000 - rev 816510
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1467894 [wpt PR 11433] - Add test for WebSocket HTTP Authentication, a=testonly Automatic update from web-platform-testsAdd test for WebSocket HTTP Authentication (#11433) User-agents should support HTTP authentication for WebSockets. Add a test of basic authentication to verify this. -- wpt-commits: f3bc9cfcbb9a0c5bbebc549ad37d93e2cf26167c wpt-pr: 11433
2d62820d3178a0a699a51acb10723443c9ec533a: Bug 1468715 [wpt PR 11501] - Fix/improve external/wpt/webrtc/RTCPeerConnection-addTrack.https.html., a=testonly
Henrik Boström <hbos@chromium.org> - Fri, 06 Jul 2018 17:10:12 +0000 - rev 816509
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468715 [wpt PR 11501] - Fix/improve external/wpt/webrtc/RTCPeerConnection-addTrack.https.html., a=testonly Automatic update from web-platform-testsFix/improve external/wpt/webrtc/RTCPeerConnection-addTrack.https.html. Updated all tests to use promise_tests(), async/await and added cleanup logic for pc.close() in tests that did not already have that. Replaced broken test: 'addTrack with existing sender with null track, same kind, and sendrecv direction should create new sender' With: 'addTrack with existing sender that has not been used to send should reuse the sender', 'addTrack with existing sender that has been used to send should create new sender' Per-spec[1], if a sender has not been used to send (currentDirection never having had the value 'sendrecv' or 'sendonly') it may be reused, so the original test was incorrect. The new tests make sure that in the original scenario the sender IS reused, and in the case where the sender has been used a new sender is created instead of reusing, even if the original sender is no longer sending. In Unified Plan[2], all tests PASS. [1] Step 7 of https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtrack [2] Work-in-Progress CL https://chromium-review.googlesource.com/c/chromium/src/+/1025771 Bug: 777617 Change-Id: I2b07bc03d84add30999e0e017bf008fbc9e9f89a Reviewed-on: https://chromium-review.googlesource.com/1100828 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#567592} -- wpt-commits: bb39a2f0ec57a4022609480d50c6074275f97f6b wpt-pr: 11501
373dbccf8e36152c74fe772255e4fa2113f24938: Bug 1468697 [wpt PR 11498] - v8binding: Changes @@unscopables's prototype to ES null., a=testonly
Yuki Shiino <yukishiino@chromium.org> - Fri, 06 Jul 2018 17:08:55 +0000 - rev 816508
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468697 [wpt PR 11498] - v8binding: Changes @@unscopables's prototype to ES null., a=testonly Automatic update from web-platform-testsv8binding: Changes @@unscopables's prototype to ES null. Implements step 8.1. of https://heycam.github.io/webidl/#create-an-interface-prototype-object Bug: 811029 Change-Id: I0feb1c16cf12585db8847c82d4efa342701bebcb Reviewed-on: https://chromium-review.googlesource.com/1098914 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#567580} -- wpt-commits: 0d616ece81edf50b2f6a284dfa98605ace62d3e7 wpt-pr: 11498
f2352e06afb33957abb9115b6902e5cb858aece3: Bug 1468710 [wpt PR 11500] - `Sec-Metadata`: `cause` is navigation-only., a=testonly
Mike West <mkwst@chromium.org> - Fri, 06 Jul 2018 17:07:37 +0000 - rev 816507
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468710 [wpt PR 11500] - `Sec-Metadata`: `cause` is navigation-only., a=testonly Automatic update from web-platform-tests`Sec-Metadata`: `cause` is navigation-only. This patch removes the `cause` member from `Sec-Metadata` headers generated for non-navigation requests. Spec: https://mikewest.github.io/sec-metadata/#cause-member Bug: 843478 Change-Id: I1cc35909ecdccd7ac0f4ab440be899acf67a0181 Reviewed-on: https://chromium-review.googlesource.com/1100820 Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org> Commit-Queue: Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#567571} -- wpt-commits: 83fd2205f71383d569f94fa50c4e74d0bf4dc5b7 wpt-pr: 11500
4c14779cf02648d2cea79d5f1fd6ae82f22d7510: Bug 1468881 [wpt PR 11512] - [testdriver.js] Correct typos, a=testonly
Mike Pennisi <mike@mikepennisi.com> - Fri, 06 Jul 2018 17:06:09 +0000 - rev 816506
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468881 [wpt PR 11512] - [testdriver.js] Correct typos, a=testonly Automatic update from web-platform-tests[testdriver.js] Correct typos -- wpt-commits: 8908785565303fd7ab90afb30dda868239401895 wpt-pr: 11512
f4f4a5e0ccd18c8301ca66c372a70a2187e29180: Bug 1468897 [wpt PR 11515] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Fri, 15 Jun 2018 08:50:38 +0000 - rev 816505
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468897 [wpt PR 11515] - Update wpt metadata, a=testonly wpt-pr: 11515 wpt-type: metadata MozReview-Commit-ID: Ep3hCydnRdA
25e29cb962897016e51df2607b126fdc7a943928: Bug 1468897 [wpt PR 11515] - Use Referrer Policy IDL as dependency for fetch, a=testonly
Chris Nardi <christopherncarmel@hotmail.com> - Fri, 06 Jul 2018 17:03:23 +0000 - rev 816504
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468897 [wpt PR 11515] - Use Referrer Policy IDL as dependency for fetch, a=testonly Automatic update from web-platform-testsUse Referrer Policy IDL as dependency for fetch (#11515) In newer versions of webidl2.js, empty enums are not allowed. We can easily switch to using the actual definition in the Referrer Policy spec to avoid running into any problems when upgrading webidl2.js. This change leads to the same number of passing/failing tests on Chrome. -- wpt-commits: 1249dcce0ee9ccc615d8b8edcff345a4f096ec37 wpt-pr: 11515
2d1c152130079c6c297075289e68490d1c5bba04: Bug 1468895 [wpt PR 11513] - Update references to OWNERS, a=testonly
Simon Pieters <zcorpan@gmail.com> - Fri, 06 Jul 2018 17:02:05 +0000 - rev 816503
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1468895 [wpt PR 11513] - Update references to OWNERS, a=testonly Automatic update from web-platform-testsUpdate references to OWNERS Fixes #11487. -- wpt-commits: 5b644a9f24eec684790f4c9970e72076b9c1f512 wpt-pr: 11513
22a0369846579df0e96e35ed1991ce1a052a8386: Bug 1473870 [wpt PR 9847] - Update the webappsec-referrer-policy IDL file, a=testonly
Luke Bjerring <lukebjerring@users.noreply.github.com> - Fri, 06 Jul 2018 17:00:35 +0000 - rev 816502
Push 115850 by bmo:tvijiala@mozilla.com at Wed, 11 Jul 2018 10:05:08 +0000
Bug 1473870 [wpt PR 9847] - Update the webappsec-referrer-policy IDL file, a=testonly Automatic update from web-platform-testsUpdate the webappsec-referrer-policy IDL file (#9847) Add webappsec-referrer-policy IDL file -- wpt-commits: 582057a7da89adbb777016a1367729eebc920a91 wpt-pr: 9847
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 tip