Bug 1780589 - [wpt-sync] Update web-platform-tests to 708e66f1a0db7f22fef274cbf0d1dc55bc87b67e, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 708e66f1a0db7f22fef274cbf0d1dc55bc87b67e wpt-type: landing

Bug 1779283 [wpt PR 34814] - CORE-AAM: update subscript and superscript MSAA mapping, a=testonly Automatic update from web-platform-tests CORE-AAM: update subscript and superscript MSAA mapping (#34814) See issue: https://github.com/w3c/core-aam/issues/130 Co-authored-by: Valerie Young <spectranaut@igalia.com> -- wpt-commits: 708e66f1a0db7f22fef274cbf0d1dc55bc87b67e wpt-pr: 34814

Bug 1780467 [wpt PR 34920] - [TableFragmentation] Fix DCHECK in FinishFragmentation for rows., a=testonly Automatic update from web-platform-tests [TableFragmentation] Fix DCHECK in FinishFragmentation for rows. Previously we'd pass in the border/padding into the FinishFragmentation function for both rows & sections. Table sections/rows however don't (directly) have border/padding. In non-collapsed mode, they don't reserve any space, and for collapsed mode the specified border only affects the border on the actual table-cell. As such just pass in a LayoutUnit() for the trailing_border_padding variable. Fixed: 1336163 Change-Id: I49c71813db62f4d1ea01d7dbce4cd311166f8d30 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3778502 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026602} -- wpt-commits: 7643ce465a934b3b69d988fc33bfe9585469a185 wpt-pr: 34920

Bug 1780491 [wpt PR 34757] - Update wpt metadata, a=testonly wpt-pr: 34757 wpt-type: metadata

Bug 1780491 [wpt PR 34757] - [WPT] Refactor evaluation-order tests, a=testonly Automatic update from web-platform-tests [WPT] Refactor evaluation-order tests - Clean up directory structure - Use .any.js (that now supports module workers) Tests around Window load events are removed: - In order to generalize the tests between Window/Worker and make them more suited for `.any.js` style, and - Because the timing of Window load events are affected by https://github.com/whatwg/html/issues/5824 in `evaluation-order-4` tests. Before this CL, `evaluation-order-4-tla.html` was failing due to this, and after this CL the test passes, on Firefox. Bug: 1128214 Change-Id: I142314c3d5ef854b342976ec89edead818f51940 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3750081 Reviewed-by: Camillo Bruni <cbruni@chromium.org> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026552} -- wpt-commits: a15924677b5d5c85d1eafc30eb34e7a2d441181c wpt-pr: 34757

Bug 1780474 [wpt PR 34921] - Add a comment about the testing methodology, a=testonly Automatic update from web-platform-tests Add a comment about the testing methodology This comes from a comment on [1] - more of an explanatory comment is added to clarify why tests are skipped if they run too slowly. [1] https://chromium-review.googlesource.com/c/chromium/src/+/3760885 Bug: 1307772 Change-Id: I69b94218cf2b27eecbf2eac794bea9083e84c117 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3778249 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Mason Freed <masonf@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1026509} -- wpt-commits: deab937d37088151680a31dbe4871e474c535778 wpt-pr: 34921

Bug 1780427 [wpt PR 34917] - Fix the ResizeObserver devicePixel2.html test, a=testonly Automatic update from web-platform-tests Fix the ResizeObserver devicePixel2.html test (#34917) The call to set the body's pattern needs to be inside observer's callback so that if the user zooms the pattern size is recalculated. -- wpt-commits: b4c2c748711136ffd222d90a903b0599c8df4fe5 wpt-pr: 34917

Bug 1779512 [wpt PR 34839] - Fix hairlines along edges of mask bounding box in masked layers, a=testonly Automatic update from web-platform-tests Fix hairlines along edges of mask bounding box in masked layers The following caused the hairlines: 1. Both the mask layer and the masked layer were under the same clip node which clips the layers to the mask bounding box; 2. The mask layer and the masked layer used different raster scales, and mapping clip rects between the layer space and the screen space caused errors. In the screen space, if the rect on the masked layer was bigger than the mask layer, pixels along the edges of the mask bounding box in the masked layer would be visible. We can't force the same raster scale of the masked layer and the mask layer because sometimes they are determined independently for the best result of each layer. For example, we want to use the native scale for surface layers (used for composited videos). To solve the problem: 1. Change the output clip of the mask effect node and its isolation group node from the mask clip to the parent of the mask clip. 2. Change the painted result of the mask layer to the above output clip, so that the mask is no longer clipped by the mask bounding box. 3. Expand the bounds of the mask layer to make sure it always covers the masked layer. This won't change the rendered result (except for slight change in anti-aliased pixels when the surface/texture pixels are not 1:1 matching physical pixels) because the mask layer should be transparent outside of the mask bounding box, and these transparent pixels should mask off the pixels in the masked layers just like an exact mask clip. Bug: 1171601 Change-Id: I85ff66e54eb67d8be01a5791d38622397da3cdf7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3742680 Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Reviewed-by: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026396} -- wpt-commits: f461b6809f1fdb400f8a203a25001d2af121c088 wpt-pr: 34839

Bug 1780442 [wpt PR 34919] - Update wpt metadata, a=testonly wpt-pr: 34919 wpt-type: metadata

Bug 1780442 [wpt PR 34919] - Navigation API: Revamp intercepted-navigation scroll handling, a=testonly Automatic update from web-platform-tests Navigation API: Revamp intercepted-navigation scroll handling Follows https://github.com/WICG/navigation-api/pull/239 Intent to Ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/DKeklNbLG5s Bug: 1345507 Change-Id: Id5c1b9d77953388dbe287f6403b0a49c8359d51b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3758902 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026382} -- wpt-commits: 5fb15e04adca47cc972a2e4c665853aca6a1a5b9 wpt-pr: 34919

Bug 1776183 [wpt PR 34549] - Fix Sandbox WPT which might not throw immediately, a=testonly Automatic update from web-platform-tests Fix Sandbox WPT which might not throw immediately Firefox does not raise an exception when a sandboxed document is accessed through the opener proxy immediately after window.open. Instead wait for half a second before checking. This resulted in proper errors being raised during manual tests (due to cross origin access to the origin member). Change-Id: I8c2b1e57673f184b9443c07c51694bbece60c8bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3720559 Commit-Queue: Pâris Meuleman <pmeuleman@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026330} -- wpt-commits: 4318787abc85524c1121d608c8d6e8e658512f53 wpt-pr: 34549

Bug 1779537 [wpt PR 34842] - Update wpt metadata, a=testonly wpt-pr: 34842 wpt-type: metadata

Bug 1779537 [wpt PR 34842] - Add CSS properties to control pop-up hover behaviors, a=testonly Automatic update from web-platform-tests Add CSS properties to control pop-up hover behaviors This CL adds these two CSS properties (which are still subject to bikeshedding on the name): - hover-pop-up-delay - hover-pop-up-hide-delay Both properties are time valued properties. The first controls the delay after hovering an invoking element (using the hoverpopup attribute) before the pop-up is triggered. The second controls the delay after which a showing pop-up will be hidden if it isn't hovered for a period of time. The first is connected to the behavior, the second will be connected in a followup CL. Discussion: https://github.com/openui/open-ui/issues/526#issuecomment-1161917067 Bug: 1307772 Change-Id: Ia44cbf63f91732935d620c527265129ffeb4f96b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3760885 Auto-Submit: Mason Freed <masonf@chromium.org> Reviewed-by: David Baron <dbaron@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026338} -- wpt-commits: c5e0cf072b586315c1e0cd79dec9a0d2d13771f6 wpt-pr: 34842

Bug 1779661 [wpt PR 34853] - Remove support for popup invoking attributes on text inputs, a=testonly Automatic update from web-platform-tests Remove support for popup invoking attributes on text inputs Per the [1] resolution, we will not support this use case for now. [1] https://github.com/openui/open-ui/issues/420#issuecomment-1184841802 Bug: 1307772 Change-Id: Iecb548d80a50135aa08e81aa2aacf5b9d9755f36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764298 Reviewed-by: Joey Arhar <jarhar@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026329} -- wpt-commits: 7d1e56e895c2e7f8ff37a5ea504a79cecb7fcec8 wpt-pr: 34853

Bug 1773369 [wpt PR 34353] - Update wpt metadata, a=testonly wpt-pr: 34353 wpt-type: metadata

Bug 1773369 [wpt PR 34353] - Implement navigateEvent.intercept() and navigateEvent.canIntercept, a=testonly Automatic update from web-platform-tests Implement navigateEvent.intercept() and navigateEvent.canIntercept Follows https://github.com/WICG/navigation-api/pull/235 intercept() works very similarly to transitionWhile(), except that instead of taking a mandatory Promise, it takes an optional handler function. If a function is provided and it returns a promise, navigation finish will be delayed until the Promise resolve, just as transitionWhile() delays navigation finish for its Promise. canIntercept is identical to canTransition. Intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/jyWqjAEv5LU Bug: 1336000 Change-Id: I94edd7fdc727080594f16fe4511cb7c302d88941 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3688177 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026325} -- wpt-commits: 5f0779f40dbb30349778db64db04754df8c4a4ef wpt-pr: 34353

Bug 1780141 [wpt PR 34891] - Update wpt metadata, a=testonly wpt-pr: 34891 wpt-type: metadata

Bug 1780141 [wpt PR 34891] - FSA: Add WPTs for isSameEntry on handles pointing to the same path, a=testonly Automatic update from web-platform-tests FSA: Add WPTs for isSameEntry on handles pointing to the same path Handles of the same type pointing to the same path should be considered the same handle, even if the underlying entry of the original handle was at one point removed. It's impossible for a file and directory of the same path to exist on disk simultaneously, but it IS possible for a FileSystemFileHandle and FileSystemDirectoryHandle of the same path to exist simultaneously, since handles are still valid even if their backing store is removed. Change-Id: If0deb9e6ea64e228b3c54e14711c58a9e378142c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3771038 Auto-Submit: Austin Sullivan <asully@chromium.org> Reviewed-by: Joshua Bell <jsbell@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026308} -- wpt-commits: 7a627776fb044b848bee82ee64eb04841c7b390d wpt-pr: 34891

Bug 1779901 [wpt PR 34864] - Update wpt metadata, a=testonly wpt-pr: 34864 wpt-type: metadata

Bug 1779901 [wpt PR 34864] - Add IDL reflections of pop-up triggering attributes, a=testonly Automatic update from web-platform-tests Add IDL reflections of pop-up triggering attributes Per the (new) resolution [1], this CL adds IDL reflections of the new triggering content attributes: popuptoggletarget, popupshowtarget, and popuphidetarget. These IDL attributes set/return just the text content of the content attribute, and cannot set elements directly, per the [2] resolution. [1] https://github.com/openui/open-ui/issues/382#issuecomment-1184773425 [2] https://github.com/openui/open-ui/issues/382#issuecomment-1158101375 Bug: 1307772 Change-Id: Iefe60ea7b86b606b0b3b8447fcebdcf576ac1771 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764319 Auto-Submit: Mason Freed <masonf@chromium.org> Commit-Queue: Mason Freed <masonf@chromium.org> Reviewed-by: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1026302} -- wpt-commits: a4e9e57e74d671be0525568fbc7dec17b7ab4149 wpt-pr: 34864

Bug 1780275 [wpt PR 34901] - Met AttributeError due to screenshot returns None, a=testonly Automatic update from web-platform-tests Met AttributeError due to screenshot returns None (#34901) * Met AttributeError due to screenshot returns None Check and raise ValueError in such situation. The exception will be processed later. Stack trace as below: File "/b/s/w/ir/third_party/wpt_tools/wpt/tools/wptrunner/wptrunner/executors/executorwebdriver.py", line 405, in run_func self.result = True, self.func(self.protocol, self.url, self.timeout) File "/b/s/w/ir/third_party/wpt_tools/wpt/tools/wptrunner/wptrunner/executors/executorwebdriver.py", line 620, in _screenshot if screenshot.startswith("data:image/png;base64,"): AttributeError: 'NoneType' object has no attribute 'startswith' -- wpt-commits: bd821de5ba38e360b3f9f160d24b6fdf35dc721c wpt-pr: 34901

Bug 1780116 [wpt PR 34884] - Only use asyncio.wait_for in bidi navigation tests which expect a timeout, a=testonly Automatic update from web-platform-tests Change approach for navigation bidi test -- wpt-commits: dd6ce9135708328697055801a8438ee4f04f12e2 wpt-pr: 34884

Bug 1779735 [wpt PR 34858] - Update wpt metadata, a=testonly wpt-pr: 34858 wpt-type: metadata

Bug 1779735 [wpt PR 34858] - New tests for gradient interpolation, a=testonly Automatic update from web-platform-tests New tests for gradient interpolation (#34858) Co-authored-by: Mike Bremford <mike@bfo.com> -- wpt-commits: 450ee0dbe9b4118bd7cee620d524bb4a5e53a0d1 wpt-pr: 34858

Bug 1780309 [wpt PR 34908] - Bump types-python-dateutil from 2.8.18 to 2.8.19 in /tools, a=testonly Automatic update from web-platform-tests Bump types-python-dateutil from 2.8.18 to 2.8.19 in /tools Bumps [types-python-dateutil](https://github.com/python/typeshed) from 2.8.18 to 2.8.19. - [Release notes](https://github.com/python/typeshed/releases) - [Commits](https://github.com/python/typeshed/commits) --- updated-dependencies: - dependency-name: types-python-dateutil dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> -- wpt-commits: 55af6a6f4eb90d2026c353d47c02b59ad9862aad wpt-pr: 34908

Bug 1780373 - [wpt-sync] Update web-platform-tests to 894c17b1c273bcdba5cbef544994782ee2ffff03, a=testonly MANUAL PUSH: wpt sync bot wpt-head: 894c17b1c273bcdba5cbef544994782ee2ffff03 wpt-type: landing

Bug 1780314 [wpt PR 34909] - Update wpt metadata, a=testonly wpt-pr: 34909 wpt-type: metadata

Bug 1780314 [wpt PR 34909] - [ComputePressure] Rename classes, a=testonly Automatic update from web-platform-tests [ComputePressure] Rename classes The class name has changed from ComputePressureXXX to PressureXXX in the spec. This patch rename classes in implementation to make them align with the spec. Detailed information can be found here: https://github.com/WICG/compute-pressure/commit/3a41340edaae5299e374b2ebfeab283e6e0080f9 Bug: 1340165 Change-Id: Ie34740a15b253ba2f8b95d66fc186b86862df362 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3771085 Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Wei4 Wang <wei4.wang@intel.com> Cr-Commit-Position: refs/heads/main@{#1026071} -- wpt-commits: 894c17b1c273bcdba5cbef544994782ee2ffff03 wpt-pr: 34909

Bug 1777760 [wpt PR 34682] - Add new devicePixel ref test, a=testonly Automatic update from web-platform-tests Add new devicePixel ref test (#34682) See comments in test for details -- wpt-commits: 8e8ed6f4bdeac2a8a12cbf608b772f696d3833e8 wpt-pr: 34682

Bug 1780139 [wpt PR 34890] - [ComputePressure] Remove CPU frequency information., a=testonly Automatic update from web-platform-tests [ComputePressure] Remove CPU frequency information. CPU frequency statistics are not a good metric. A CPU can have multiple boost modes depending on which core is running and depending on whether on AC or DC power. We cannot deduct that a CPU is stressed just because it is running at a high frequency. Also it might be running at a lower frequency due to power settings or being on DC power and then the system can easily be under pressure at this lower frequency. (GitHub issue: https://github.com/WICG/compute-pressure/issues/24, Spec change: https://github.com/WICG/compute-pressure/commit/e3da844ddb2a9bf5d8c86ab561f62bf666ed6d27). We remove CPU frequency information from the implementation in this patch and use only CPU utilization temporarily. We will switch to PressureState in the future according to the newest spec (https://wicg.github.io/compute-pressure/#pressure-states) and we are working on a robust algorithm to calculate PressureState. Bug: 1339205 Change-Id: I15a17fd1eefeeefaddc5f3df5e2a98b04cac4368 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3725753 Reviewed-by: Matthew Denton <mpdenton@chromium.org> Commit-Queue: Wei4 Wang <wei4.wang@intel.com> Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025486} -- wpt-commits: b9afc4f837c1ebaade07b0d04ecc40fc3b28f21d wpt-pr: 34890

Bug 1780289 [wpt PR 34903] - Fix typo in StyleRuleLayerStatement::Copy() name, a=testonly Automatic update from web-platform-tests Fix typo in StyleRuleLayerStatement::Copy() name The function is currently incorrectly named as `copy()`, and hence unable to shadow `StyleRuleBase::Copy()`, causing an infinite recursion when `Copy()` is called. This patch fixes it. Fixed: 1345181 Change-Id: I1171f87ad619d491ef86c4f0d7c368f2d061eafb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3773449 Reviewed-by: David Baron <dbaron@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025947} -- wpt-commits: be604a19721dd818bcc4059cbaf9193600c02585 wpt-pr: 34903

Bug 1779639 [wpt PR 34852] - Update wpt metadata, a=testonly wpt-pr: 34852 wpt-type: metadata

Bug 1779639 [wpt PR 34852] - Add missing step_func() in a couple of cookie tests, a=testonly Automatic update from web-platform-tests Add missing step_func() in a couple of cookie tests Without this, any subtest failure would result in a rejected promise which would cause the test to time out. -- wpt-commits: 9deda95926faed241b9090ff4770561c24e9137d wpt-pr: 34852

Bug 1780069 [wpt PR 34879] - Fix document.referrer on about:blank creation, a=testonly Automatic update from web-platform-tests Fix document.referrer on about:blank creation The HTML Standard assigns `document.referrer` [1] in two ways: 1.) During Document/browsing context creation 2.) Upon navigation to a new Document For creation (1): Per the HTML Standard's "create a new browsing context" algorithm [2] step 3, all new browsing contexts with a non-null creator (always same-BCG) have their "creator URL" set to the creator document's full URL, unredacted and subjected to no referrer policy sanitization. Later in step 20, we set the referrer of the newly-created document to the newly-created browsing context's creator URL. For navigation (2): In "create and initialize a Document object", with the referrer from "navigation params" [3] ---- In Blink, we handle `document.referrer` assignment the same for both creation and navigation; we simply set `DocumentLoader::referrer_` to what the resulting `WebNavigationParams` carries [4], and we don't do anything special for the browsing context creation case. This leads to the final `document.referrer` on Documents being created in new BCs actually being incorrectly subjected to referrer policy sanitization/redaction. Due to existing issues, Chrome does not perfectly follow the HTML Standard for creation of new browsing contexts. In short, for iframes we create a new browsing context/document [5] and immediately navigate it to about:blank [6]. This navigation commits synchronously via a special path that tries to make up for Blink's mismatch with the spec [7]. During this synchronous about:blank navigation, the request's referrer is computed as "" (in FrameLoadRequest::ctor), because the origin of the "about:blank" URL is opaque and therefore cross-origin with the embedder, and the default referrer policy is `strict-origin-when-cross-origin`. For newly created windows (with openers, since this is only relevant for windows with "creators"), something very similar happens. We create a FrameLoadRequest whose referrer gets set to "" (in FrameLoadRequest::ctor as well as [8]), and we perform the special-case synchronous navigation which ends up with the resulting document having an empty referrer, just like in the iframe case. ---- This CL fixes the above issues by modifying `RenderFrameImpl::SynchronouslyCommitAboutBlankForBug778318()` to find the initiator frame (should be equivalent to the spec's "creator" Document), if it is local (should be the case for about:blank subframes and new windows w/o "noopener"), and sets the navigation params's referrer member to the initiator Document's full unredacted URL. This will be used to set the eventual `DocumentLoader::referrer_` member when the synchronous navigation commits, which will be used to reflect the correct value to `document.referrer`. In cases where we don't go through Blink's special sync navigation case, `document.referrer` is unchanged. ---- [1]: https://html.spec.whatwg.org/multipage/dom.html#dom-document-referrer and https://html.spec.whatwg.org/multipage/dom.html#the-document's-referrer [2]: https://html.spec.whatwg.org/multipage/browsers.html#creating-a-new-browsing-context [3]: https://html.spec.whatwg.org/multipage/browsing-the-web.html#navigating-across-documents:the-document's-referrer-2 [4]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/loader/document_loader.cc;l=322;drc=5dffcc4991ab32edc7dbc99c3b4685882c029ab0 [5]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/html_frame_owner_element.cc;l=827-828;drc=6fd9edfbb85bc5fb2ed8f9300abe83cd03ab54b7 [6]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/html_frame_owner_element.cc;l=862-863;drc=6fd9edfbb85bc5fb2ed8f9300abe83cd03ab54b7 [7]: https://source.chromium.org/chromium/chromium/src/+/main:content/renderer/render_frame_impl.h;l=929-953;drc=5575ddb21068841ba19e1ea957b4fdb5adcd0250 [8]: https://source.chromium.org/chromium/chromium/src/+/main:content/renderer/render_view_impl.cc;l=290-292;drc=5dffcc4991ab32edc7dbc99c3b4685882c029ab0 Bug: 1075729 Change-Id: I6c01ece280bc8702dda6ba60015eaafb3989f3d3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3763042 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: Daniel Rubery <drubery@chromium.org> Reviewed-by: Domenic Denicola <domenic@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025876} -- wpt-commits: 48ce7be7c6af5153d589bde659f97385e724e273 wpt-pr: 34879

Bug 1780234 [wpt PR 34897] - [WPT] Fix the test for initially empty iframe, a=testonly Automatic update from web-platform-tests [WPT] Fix the test for initially empty iframe The head script tag was not finishing the test. This version fails on CHrome Stable but passes on a dev build, confirming that it is still testing the behavior. Bug: 1231231 Change-Id: I0afdec9278c1c9b5d7bab9c87850ced5347e9952 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3773613 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025783} -- wpt-commits: ce11f1f8de568b9efd18f9bb0c17fa46b8c1af1c wpt-pr: 34897

Bug 1774104 [wpt PR 34416] - Update wpt metadata, a=testonly wpt-pr: 34416 wpt-type: metadata

Bug 1774104 [wpt PR 34416] - [Delegate-CH] (1) Add support to chromium, a=testonly Automatic update from web-platform-tests [Delegate-CH] (1) Add support to chromium This adds support for the delegate-ch meta tag. It works like the accept-ch meta tag, except it uses the same syntax as the allow iframe attribute. https://groups.google.com/a/chromium.org/g/blink-dev/c/cGOjmfOamsE/ This CL is part of a series: (1) Add support to chromium (2) Add tests to devtools Bug: 1334152 Change-Id: I19ce426da8a0aa158aad1fde24f3bd4f19581c52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3702967 Reviewed-by: Yue Ru Sun <yrsun@chromium.org> Commit-Queue: Ari Chivukula <arichiv@chromium.org> Reviewed-by: Charlie Reis <creis@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> Auto-Submit: Ari Chivukula <arichiv@chromium.org> Reviewed-by: Victor Tan <victortan@chromium.org> Reviewed-by: Yoav Weiss <yoavweiss@chromium.org> Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025731} -- wpt-commits: f830fcfb39d68d271b6b5a558784de69bb8fdfce wpt-pr: 34416

Bug 1776194 [wpt PR 34550] - Update wpt metadata, a=testonly wpt-pr: 34550 wpt-type: metadata

Bug 1776194 [wpt PR 34550] - Add CSSTrigonometricFunctions feature flag and sin() function, a=testonly Automatic update from web-platform-tests Add CSSTrigonometricFunctions feature flag and sin() function According to the CSS Values and Units Module Level 4 [1], the trigonometric function should be parsed and evaluated. Therefore, this initial feature CL adds the feature flag 'CSSTrigonometricFunctions' and 'sin, cos, asin, acos, atan, atan2' keywords to css_value_keywords.json5. (tan keyword is already defined) Also, Implement parsing and evaluation for sin(). Feature status: [2] Intent to prototype: [3] [1] https://www.w3.org/TR/css-values-4/#trig-funcs [2] https://chromestatus.com/feature/5165381072191488 [3]https://groups.google.com/a/chromium.org/g/blink-dev/c/-c9p-Sq_gWg Bug: 1190444 Change-Id: Ibd190fcdc61980f81e456b259ecd5bac86c4612b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3713201 Reviewed-by: Mason Freed <masonf@chromium.org> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Commit-Queue: Seokho Song <seokho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025665} -- wpt-commits: 4d2d72a77c336a552866e955557e63fd54f8615c wpt-pr: 34550

Bug 1779928 [wpt PR 34865] - Add CSS values test for mixed units in calc & media query, a=testonly Automatic update from web-platform-tests Add CSS values test for mixed units in calc & media query (#34865) -- wpt-commits: c274b5986f80b02329289df959dbb786bb54c80e wpt-pr: 34865

Bug 1780118 [wpt PR 34885] - Further refine the regex used to find STP releases, a=testonly Automatic update from web-platform-tests Further refine the regex used to find STP releases This also substantially increases the number of tests we have for this; these are based on a subset of the download pages fetched from the Wayback Machine, manually filtered to those which are perhaps more 'interesting'. -- wpt-commits: 267d169d4f376775a33394164fae8471e7424e55 wpt-pr: 34885

Bug 1780179 [wpt PR 34894] - Update infrastructure metadata for Firefox touch support, a=testonly Automatic update from web-platform-tests Update infrastructure metadata for Firefox touch support -- wpt-commits: fd64a55ccd24da176a82c1d9cc4e777f1832ab30 wpt-pr: 34894

Bug 1780162 [wpt PR 34893] - Reland again "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box.", a=testonly Automatic update from web-platform-tests Reland again "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box." This is a reland of commit 2c20b99e08731c4bae71da9d4598d10146f52848 The differences from the original CL: Because the original CL caused a performance regression, this CL adds a cache of the state of CanContainAbsolutePositionObjects(). LayoutObjectBitfields already has 96 bits, and this CL adds a bit flag between full_paint_invalidation_reason_ and the bitfields. The size of LayoutObject is not changed by this CL. The differences from the first reland CL: Fix Windows x64 build failure. Original change's description: > Fieldset NG: Fix paint order of OOF objects in a LEGEND and the > corresponding anonymous content box. > > If a FIELDSET is an OOF container, we made its anonymous content box > an OOF container by setting position:relative. It's bad because OOF > objects in the LEGEND is painted behind the anonymous content box. So > this CL updates OOF container conditions for anonymous fieldset content > boxes, and avoids setting position:relative. > > * ng_fieldset_algorithm.cc: > Handle NGBreakStatus::kDisableFragmentation. > Without this change, floated-multicol-in-multicol-crash.html in WPT has > a DCHECK failure. > > Bug: 1341413 > Change-Id: I650b3020df53eba5d05f930bc44675b80ff4e90b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764404 > Reviewed-by: Koji Ishii <kojii@chromium.org> > Commit-Queue: Kent Tamura <tkent@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1025081} Bug: 1341413 Change-Id: Ib539ae3b11700cc7f51eb11ae33a8e972c940538 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3767050 Auto-Submit: Kent Tamura <tkent@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025608} -- wpt-commits: 384950f6620d46ac4b08fff887d48a8783129850 wpt-pr: 34893

Bug 1780151 [wpt PR 34892] - Revert "Reland "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box."", a=testonly Automatic update from web-platform-tests Revert "Reland "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box."" This reverts commit c65216f57e6cfab266510c77e5472fb126e3d23a. Reason for revert: Findit (https://goo.gl/kROfz5) identified this CL at revision c65216f57e6cfab266510c77e5472fb126e3d23a as the culprit for failures in the continuous build including: Sample Failed Build: https://ci.chromium.org/b/8808235698216366977 Sample Failed Step: compile If it is a false positive, please report it at https://bugs.chromium.org/p/chromium/issues/entry?status=Available&comment=Datastore+key+for+the+culprit+entity%3A+chromium.googlesource.com%2Fchromium%2Fsrc%2Frefs%2Fheads%2Fmain%2Fc65216f57e6cfab266510c77e5472fb126e3d23a&labels=Test-Findit-Wrong&components=Tools%3ETest%3EFindIt&summary=Wrongly+blame+c65216f57e6cfab266510c77e5472fb126e3d23a Original change's description: > Reland "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box." > > This is a reland of commit 538bf46dd9ac492c74cf720bbde3d7fe2d681fe4 > > The difference from the original CL: > Because the original CL caused a performance regression, this CL adds > a cache of the state of CanContainAbsolutePositionObjects(). > LayoutObjectBitfields already has 96 bits, and this CL adds a bit flag > between full_paint_invalidation_reason_ and the bitfields. The size > of LayoutObject is not changed by this CL. > > Original change's description: > > Fieldset NG: Fix paint order of OOF objects in a LEGEND and the > > corresponding anonymous content box. > > > > If a FIELDSET is an OOF container, we made its anonymous content box > > an OOF container by setting position:relative. It's bad because OOF > > objects in the LEGEND is painted behind the anonymous content box. So > > this CL updates OOF container conditions for anonymous fieldset content > > boxes, and avoids setting position:relative. > > > > * ng_fieldset_algorithm.cc: > > Handle NGBreakStatus::kDisableFragmentation. > > Without this change, floated-multicol-in-multicol-crash.html in WPT has > > a DCHECK failure. > > > > Bug: 1341413 > > Change-Id: I650b3020df53eba5d05f930bc44675b80ff4e90b > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764404 > > Reviewed-by: Koji Ishii <kojii@chromium.org> > > Commit-Queue: Kent Tamura <tkent@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1025081} > > Bug: 1341413 > Change-Id: I63cc9938a1a63f11bb7ea1c418839d3155313166 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3771160 > Reviewed-by: Koji Ishii <kojii@chromium.org> > Commit-Queue: Kent Tamura <tkent@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1025577} Change-Id: If4937f0ca23707f890161bf1f78422b69bc6290f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1341413 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3770852 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Owners-Override: Nancy Wang <nancylingwang@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025584} -- wpt-commits: b413cbbbeb9666486342ebc6c512efaac513d309 wpt-pr: 34892

Bug 1780136 [wpt PR 34889] - Reland "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box.", a=testonly Automatic update from web-platform-tests Reland "Fieldset NG: Fix paint order of OOF objects in a LEGEND and the corresponding anonymous content box." This is a reland of commit 538bf46dd9ac492c74cf720bbde3d7fe2d681fe4 The difference from the original CL: Because the original CL caused a performance regression, this CL adds a cache of the state of CanContainAbsolutePositionObjects(). LayoutObjectBitfields already has 96 bits, and this CL adds a bit flag between full_paint_invalidation_reason_ and the bitfields. The size of LayoutObject is not changed by this CL. Original change's description: > Fieldset NG: Fix paint order of OOF objects in a LEGEND and the > corresponding anonymous content box. > > If a FIELDSET is an OOF container, we made its anonymous content box > an OOF container by setting position:relative. It's bad because OOF > objects in the LEGEND is painted behind the anonymous content box. So > this CL updates OOF container conditions for anonymous fieldset content > boxes, and avoids setting position:relative. > > * ng_fieldset_algorithm.cc: > Handle NGBreakStatus::kDisableFragmentation. > Without this change, floated-multicol-in-multicol-crash.html in WPT has > a DCHECK failure. > > Bug: 1341413 > Change-Id: I650b3020df53eba5d05f930bc44675b80ff4e90b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3764404 > Reviewed-by: Koji Ishii <kojii@chromium.org> > Commit-Queue: Kent Tamura <tkent@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1025081} Bug: 1341413 Change-Id: I63cc9938a1a63f11bb7ea1c418839d3155313166 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3771160 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025577} -- wpt-commits: a3a90eec974a7713b95b780256b29dd2b835ee8a wpt-pr: 34889

Bug 1779970 [wpt PR 34871] - WPT: Add test for user_preferences manifest member, a=testonly Automatic update from web-platform-tests WPT: Add test for user_preferences manifest member Explainer: https://github.com/WICG/manifest-incubations/blob/gh-pages/user-preferences-explainer.md Bug: 1318305 Change-Id: I148c354ecb135eaf8cd5bc7a44be18a3b805c50a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3767017 Reviewed-by: Glen Robertson <glenrob@chromium.org> Commit-Queue: Louise Brett <loubrett@google.com> Cr-Commit-Position: refs/heads/main@{#1025530} -- wpt-commits: 5e488929a9428290e0843f9abb63e775846a9c40 wpt-pr: 34871

Bug 1780115 [wpt PR 34883] - Update wpt metadata, a=testonly wpt-pr: 34883 wpt-type: metadata

Bug 1780115 [wpt PR 34883] - [wpt] Fix test for crbug.com/1238243, a=testonly Automatic update from web-platform-tests [wpt] Fix test for crbug.com/1238243 Updates test as per: https://github.com/w3c/csswg-drafts/issues/6230 Fixed: 1238243 Change-Id: I75ef894dabf63daf7c49a0a728668aac44e8ce7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3770091 Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: David Grogan <dgrogan@chromium.org> Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025504} -- wpt-commits: cc0620f158fa70053f2fa72aa9c2e77329338dc9 wpt-pr: 34883

Bug 1773946 [wpt PR 34387] - Update wpt metadata, a=testonly wpt-pr: 34387 wpt-type: metadata

Bug 1773946 [wpt PR 34387] - [ComputePressure] Make ComputePressure as a service., a=testonly Automatic update from web-platform-tests [ComputePressure] Make ComputePressure as a service. The patch makes ComputePressure as a service and the major changes are: 1. Move ComputePressureManager and related classes from content/browser to services/device. Rename ComputePressureManager to ComputePressureManagerImpl. 2. Rename ComputePressureHost to ComputePressureServiceImpl. 3. ComputePressureSample data are collected in service now and then send to ComputePressureServiceImpl. If the data changes and meets frequency requirement, ComputePressureServiceImpl will send the data to Blink. 4. CpuProbe collects data only when there is active ComputePressureObserver. It stops collecting when all ComputePressureObservers become inactive. The compute_pressure_different_quantizations_across_iframes test fails in this patch. However, there is no concept of the quantization in the newest spec any more and we will remove this test in the future. Bug: 1205695, 1311945 Change-Id: I388ce2ea3d7be2e717c080d92c77b8d0b3570f03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3661519 Reviewed-by: Alexander Timin <altimin@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Wei4 Wang <wei4.wang@intel.com> Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by: Joshua Bell <jsbell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1025483} -- wpt-commits: 8eefb4deef4e29455582ba460bfd1fcc19abb5a6 wpt-pr: 34387