8bd615a461b7b032b658093cd5734111b6801873: Bug 1616007 - Invalid hasPolicies check. r=mconley
Michael Kaply <mozilla@kaply.com> - Tue, 18 Feb 2020 19:42:05 +0000 - rev 514522
Push 107612 by mozilla@kaply.com at Tue, 18 Feb 2020 20:05:36 +0000
Bug 1616007 - Invalid hasPolicies check. r=mconley Differential Revision: https://phabricator.services.mozilla.com/D63209
a9091629c4f81bc5da7143cf64a187b5e1fbb97e: Bug 1609324 - Disable BFCache when remote subframes are present, r=smaug
Nika Layzell <nika@thelayzells.com> - Sun, 16 Feb 2020 13:40:12 +0000 - rev 514521
Push 107611 by nlayzell@mozilla.com at Tue, 18 Feb 2020 19:54:17 +0000
Bug 1609324 - Disable BFCache when remote subframes are present, r=smaug Differential Revision: https://phabricator.services.mozilla.com/D62831
66e8f8552963b2713414be030c6a1842ba1e9035: Bug 1616327 - Use fallible SetLength in XPCConvert::JSData2Native. r=nika
Andrew McCreight <continuation@gmail.com> - Tue, 18 Feb 2020 19:46:14 +0000 - rev 514520
Push 107610 by amccreight@mozilla.com at Tue, 18 Feb 2020 19:46:52 +0000
Bug 1616327 - Use fallible SetLength in XPCConvert::JSData2Native. r=nika Differential Revision: https://phabricator.services.mozilla.com/D63219
870496388ab86dab002b8fd7a5872924bf2691c9: Bug 1607214, the implementation of the HTMLInputElement.controllers getter can return null, r=bzbarsky
Neil Deakin <neil@mozilla.com> - Tue, 18 Feb 2020 19:16:12 +0000 - rev 514519
Push 107609 by neil@mozilla.com at Tue, 18 Feb 2020 19:36:27 +0000
Bug 1607214, the implementation of the HTMLInputElement.controllers getter can return null, r=bzbarsky Differential Revision: https://phabricator.services.mozilla.com/D58789
292082ca1880af67d427b994ab851e8da203e831: Bug 1616083 - [wpt-sync] Update web-platform-tests to 9521d69a5d737712abb2ef6387d227445e2999dd, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 17 Feb 2020 17:04:29 +0000 - rev 514518
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1616083 - [wpt-sync] Update web-platform-tests to 9521d69a5d737712abb2ef6387d227445e2999dd, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 9521d69a5d737712abb2ef6387d227445e2999dd wpt-type: landing
7f40ffaa3a12cf348a6e69a71403398e1dbb372e: Bug 1615689 [wpt PR 21808] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 17 Feb 2020 16:07:14 +0000 - rev 514517
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615689 [wpt PR 21808] - Update wpt metadata, a=testonly wpt-pr: 21808 wpt-type: metadata
f760e424a9c2bbdf17f3b233125ec88799612d4b: Bug 1615689 [wpt PR 21808] - [css-pseudo] Fix text selection and drag-and-drop for pseudo-elements, a=testonly
Oriol Brufau <obrufau@igalia.com> - Mon, 17 Feb 2020 17:04:15 +0000 - rev 514516
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615689 [wpt PR 21808] - [css-pseudo] Fix text selection and drag-and-drop for pseudo-elements, a=testonly Automatic update from web-platform-tests [css-pseudo] Fix text selection and drag-and-drop for pseudo-elements Before this patch, if you had a tree like <div><div::before>abc</div::before>def</div> and you tried to select "bc", Chromium would end up selecting "ef" in some cases. Similarly, trying to drag a text and drop it between "bc", would end up inserting the text between "ef". This patch fixes the problem, now trying to select "bc" won't select anything. And dropping some text between "bc" will insert it between the "cd". BUG=1051685 TEST=external/wpt/css/css-pseudo/text-selection.html TEST=fast/css-generated-content/drag-and-drop.html The 2nd test is internal because I didn't manage to properly simulate drag and drop using testdriver.js Change-Id: Iedd594b46022ed434bdb1462232c717ec08f5304 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047287 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#741909} -- wpt-commits: 410f5ece454de3f304f4ac885be244ed9755ac18 wpt-pr: 21808
5e9f8bf1d4debb9e7eadc2dfeeb30b48fe7ca08e: Bug 1615894 [wpt PR 21821] - Fix resources path in lazy load tests, a=testonly
Rob Buis <rbuis@igalia.com> - Mon, 17 Feb 2020 17:04:02 +0000 - rev 514515
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615894 [wpt PR 21821] - Fix resources path in lazy load tests, a=testonly Automatic update from web-platform-tests Fix resources path in lazy load tests When moving lazy load tests to html/semantics/embedded-content/the-img-element the internal resources paths were not adjusted, so do it in this change. -- wpt-commits: 0ffd3515e2a53c04c5465687153d77bc50328c86 wpt-pr: 21821
417651cd1779fd2d20cba7c5868bd4b849225a07: Bug 1616026 [wpt PR 21835] - Use six.iteritems to iterate over dictionary's items in tools, a=testonly
Ziran Sun <zsun@igalia.com> - Mon, 17 Feb 2020 17:03:57 +0000 - rev 514514
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1616026 [wpt PR 21835] - Use six.iteritems to iterate over dictionary's items in tools, a=testonly Automatic update from web-platform-tests Use six.iteritems to iterate over dictionary's items in tools This corresponds to dictionary.iteritems() on Python 2 and dictionary.items() on Python 3. -- wpt-commits: 70efafb7da25cb0c44beb95dfbb4198e80a557b9 wpt-pr: 21835
ff8bf380fbb17b59a248855e38c3f5775e2f9297: Bug 1615997 [wpt PR 21832] - [WPT/mixed-content] Remove websocket + redirect tests, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Mon, 17 Feb 2020 17:03:52 +0000 - rev 514513
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615997 [wpt PR 21832] - [WPT/mixed-content] Remove websocket + redirect tests, a=testonly Automatic update from web-platform-tests [WPT/mixed-content] Remove websocket + redirect tests Redirects are forbidden (see Step 12 and the warning at the bottom: https://fetch.spec.whatwg.org/#concept-websocket-establish ). Previously, websocket + redirect tests were generated, but their behavior was the same as websocket + no-redirect, because the websocket subresource endpoint ignores redirect-related parameters. This CL removes such redundant tests. Bug: 906850 Change-Id: I86be33d1812b4d16ba463f14320fb23369321cc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058707 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#741851} -- wpt-commits: 2d1c196b4bb245aa80b4fafe5824384fee386a82 wpt-pr: 21832
d74fa0c646fa5731c798183e067ff4bd0e01e961: Bug 1615937 [wpt PR 21826] - [WPT/common/security-features] Transition `spec.src.json` to JSON5, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Mon, 17 Feb 2020 17:03:47 +0000 - rev 514512
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615937 [wpt PR 21826] - [WPT/common/security-features] Transition `spec.src.json` to JSON5, a=testonly Automatic update from web-platform-tests [WPT/common/security-features] Transition `spec.src.json` to JSON5 To allow inline comments in `spec.src.json` to make it more descriptive, this CL parses `spec.src.json`s as JSON5, using `json5` non-standard library. After parsing, we still use `json` module for outputting JSON objects. Subsequent CLs e.g. [1] will actually add inline comments to `spec.src.json`s. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2049953 This CL doesn't change the generated results. Bug: 906850, https://github.com/web-platform-tests/wpt/issues/21824 Change-Id: I8c6472b41ae55a051889fc29cf57d392ef60b69f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058706 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#741850} -- wpt-commits: 8205a7e07caf3606abed03306d5b51c0d688252a wpt-pr: 21826
3d93a80c7e0bc643b7c0c43305b38792297cd2c4: Bug 1615519 [wpt PR 21795] - SharedWorker: Fire an error event when type or credentials mismatch, a=testonly
Eriko Kurimoto <elkurin@google.com> - Mon, 17 Feb 2020 17:03:42 +0000 - rev 514511
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615519 [wpt PR 21795] - SharedWorker: Fire an error event when type or credentials mismatch, a=testonly Automatic update from web-platform-tests SharedWorker: Fire an error event when type or credentials mismatch This CL adds the step to check if type and credentials values are same with these of matched SharedWorkerGlobalScope before connecting to it. This is just added to the spec. Spec issue: https://github.com/whatwg/html/issues/5235 Pull request: https://github.com/whatwg/html/pull/5258 WPT: https://github.com/web-platform-tests/wpt/pull/21651 This changes the behavior, and WPT is already added from the public pull requests to WPT GitHub: wpt/workers/shared-worker-options-mismatch.html In this CL, http/tests/workers/shared-worker-shared.html is modified. Since the way to catch worker's error had changed, this test was no longer catching the error properly. This test was attempting to create SharedWorker with non-existing script url so ErrorEvent had been fired. However, this test couldn't successfully catch ErrorEvent and this is found out since the console error log added in this CL is printed as "text diff". Fixing this test is out-of-scope, so this CL avoid this console error by using an existing script url. Bug: 1050438 Change-Id: I03232ff19db89560d99d3ddc6a25cdd8f1898222 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2041386 Commit-Queue: Eriko Kurimoto <elkurin@google.com> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#741848} -- wpt-commits: 497675f53a9542bdb77c0640cd683e5990659a94 wpt-pr: 21795
06705ec6ae73173f1eede4bc59f5311cad6a9a89: Bug 1615898 [wpt PR 21822] - Iterating over dictionary's items with six library for PY2 & PY3 comp…, a=testonly
Ziran Sun <zsun@igalia.com> - Mon, 17 Feb 2020 17:03:37 +0000 - rev 514510
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615898 [wpt PR 21822] - Iterating over dictionary's items with six library for PY2 & PY3 comp…, a=testonly Automatic update from web-platform-tests Iterating over dictionary's items with six library for PY2 & PY3 compatibility. -- wpt-commits: ef72cc2212e324334032148aea9169edf2562ef5 wpt-pr: 21822
5fd7a1490e6224276edc49552f4124d73d87a74a: Bug 1615933 [wpt PR 21823] - [WPT/mixed-content] Flatten subresource types, a=testonly
Hiroshige Hayashizaki <hiroshige@chromium.org> - Mon, 17 Feb 2020 17:03:32 +0000 - rev 514509
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615933 [wpt PR 21823] - [WPT/mixed-content] Flatten subresource types, a=testonly Automatic update from web-platform-tests [WPT/mixed-content] Flatten subresource types To unify `spec.src.json`, this CL flattens subresource types in `mixed-content/spec.src.json`, to match the structure with other `spec.src.json`s. A subsequent CL https://chromium-review.googlesource.com/c/chromium/src/+/2049953 will actually merge some parts of `spec.src.json`s. This CL doesn't change the generated results. Bug: 906850 Change-Id: I38963dbc847b09fb314907e8d068232c15e7cffc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058705 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/master@{#741847} -- wpt-commits: b2331fccbc54f5b0a57d66190d30d40341cbc957 wpt-pr: 21823
9fd520a3fece64a38d59970f7789141e223bded6: Bug 1612706 [wpt PR 21539] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Mon, 17 Feb 2020 09:04:42 +0000 - rev 514508
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1612706 [wpt PR 21539] - Update wpt metadata, a=testonly wpt-pr: 21539 wpt-type: metadata
9e75d903108034bc94493f1309fda5f669778f86: Bug 1612706 [wpt PR 21539] - Add new comprehensive test for image-set rendering, a=testonly
Noam Rosenthal <noamr@users.noreply.github.com> - Mon, 17 Feb 2020 17:03:23 +0000 - rev 514507
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1612706 [wpt PR 21539] - Add new comprehensive test for image-set rendering, a=testonly Automatic update from web-platform-tests Add new comprehensive test for image-set rendering (#21539) * Add new comprehensive test for image-set rendering * Use dpr 1 for now for test - no sufficient infra for DPR setting -- wpt-commits: 1b7dcb06ea477226e90ca0fbc0b86262a410f7ad wpt-pr: 21539
ec7efef9ea874e5edf5fdb6f7c96ea5f7612de5f: Bug 1615951 [wpt PR 21828] - Remove CSS Rhythmic Sizing tests, a=testonly
Koji Ishii <kojii@chromium.org> - Mon, 17 Feb 2020 17:03:18 +0000 - rev 514506
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615951 [wpt PR 21828] - Remove CSS Rhythmic Sizing tests, a=testonly Automatic update from web-platform-tests Remove CSS Rhythmic Sizing tests Two years ago, when applying vertical rhythm algorithms, the risk of accidental rounding up was raised. This is a widely known, unavoidable risk in any vertical rhythm algorithms. The CSSWG was in favor to accept it 8 years ago, but this time, two members considered the risk is critical. https://github.com/w3c/csswg-drafts/issues/938 Last month, the CSSWG discussed this again. One invited expert was still strong not to accept the risk, and that the CSSWG resolved to remove tests. https://github.com/w3c/csswg-drafts/issues/938#issuecomment-577640685 Reduces 4 failures, as the feature is no longer implemented in LayoutNG nor in any other implementations. TBR=ikilpatrick@chromium.org, tabatkins@chromium.org Bug: 586413 Change-Id: Ia0d50d77550cc5c8b681f001a4f25a825e6504ab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059692 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741820} -- wpt-commits: ac16628eb7eb601957382053011363d2bcf8ce44 wpt-pr: 21828
7f1ee3df709eb0bc6695abcc16e58a1fdd36876c: Bug 1615869 [wpt PR 21820] - [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm., a=testonly
Ian Kilpatrick <ikilpatrick@chromium.org> - Mon, 17 Feb 2020 17:03:13 +0000 - rev 514505
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615869 [wpt PR 21820] - [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm., a=testonly Automatic update from web-platform-tests [LayoutNG] Generate first baseline for kInlineBlock baseline algorithm. In https://chromium-review.googlesource.com/c/chromium/src/+/1988376 I simplified the logic a little too much. We (occasionally) need the first-baseline of a child inside an inline-block. We need this when we are aligning a list-marker. This modifies the NGBaselineAlgorithmType::kInlineBlock to always produce both the first and last baselines. Bug: 1051181 Change-Id: I4844dfe44d3525a68ee8b8d7f0f50bd995de9367 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057344 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741798} -- wpt-commits: 2cd67814c72b152489684d47023a7a5ce9d0aced wpt-pr: 21820
2d343ee199327a05929787abde1d2fd5d603a088: Bug 1615754 [wpt PR 21811] - Update test processing of StageParameters changes, a=testonly
Alex Cooper <alcooper@chromium.org> - Mon, 17 Feb 2020 17:03:08 +0000 - rev 514504
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615754 [wpt PR 21811] - Update test processing of StageParameters changes, a=testonly Automatic update from web-platform-tests Update test processing of StageParameters changes Currently the test code only sends the stage parameters as Display Info updates. Now that WebVr has been removed, this code path is one that is being considered for removal. The real runtimes utilize both this VRDisplayInfo update path as well as updating the stage parameters with frame data. This changes the test runtime to do the same (i.e. send up stage parameters via both DisplayInfo and FrameData). Fixed: 983363 Change-Id: I3c0a3f59b97163c3ac3b8f4b6529183142688d0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056501 Commit-Queue: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/master@{#741671} -- wpt-commits: 8debe68e88d3b10393ea3dc5862d4130c663f496 wpt-pr: 21811
2157de86143ff7a756926e7be0f5008f28e42ba9: Bug 1615440 [wpt PR 21788] - Update wpt metadata, a=testonly
moz-wptsync-bot <wptsync@mozilla.com> - Sun, 16 Feb 2020 16:08:39 +0000 - rev 514503
Push 107608 by wptsync@mozilla.com at Tue, 18 Feb 2020 19:32:13 +0000
Bug 1615440 [wpt PR 21788] - Update wpt metadata, a=testonly wpt-pr: 21788 wpt-type: metadata
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip