d like to request other LGTMs as well: https://chromestatus.com/feature/5915984063889408?gate=6183183769403392 On Wednesday, June 24, 2026 at 5:21:52 PM UTC+2 rby...@chromium

that came to mind is when there is CPU hotplug is involved (eg ChromeOS does this for battery saver). It seems like as of today there isn't a way for apps to react when the core count

drag starts to ensure the event stream doesn't look like the pointer is still down? 2. How would developers recreate something like the chrome UI - the natural way to write the HTML

great addition to the platform - LGTM1 > On 6/25/26 3:00 pm, Chromestatus wrote: > > *Contact emails* > shivanisha@chromium.org, mkwst@chromium.org, skmanickam@

-class to control and detect > animated images like GIFs and APNGs. 1. image-animation: Can be set to > "normal", "running", or "paused" to

is the Intent to Ship: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a3e71b6.cff415cc.dde5e.00b1.GAE%40google.com (Apologies for the delay, I had a long

shadowrootslotassignment attribute to the element, allowing declarative shadow roots to use manual slot assignment. Until now this option was only available imperatively, via

16 PM To: Daniel Clark Cc: blink-dev@chromium.org Subject: Re: [blink-dev] Intent to Ship: Reference Target Thanks for working on this API, it solves an important a11y and functional

issues related to both interoperability and missing functionality. > > `redirectCount`, `redirectStart` and `redirectEnd` are not > currently exposed in Chromium for

that need to optimize the performance of the > compute shader using subgroup operations with specifc subgroup > size on certain platforms, such as the AI workloads. > >

CL 8006126 to address and ensure we aren't exposing the API on platforms that don't have corresponding platform implementations. On Thursday, June 25, 2026 at 5:34:25 AM

api, to a relatively thorough list of mechanisms for task > scheduling, supported dom modifications, different element paint types, > different history navigation mechanisms

> this to us. From a compat perspective, the Finch'd rollout plan >> sounds good, and we wish you luck. >> >> From a Blink process perspective, we think this

would need to be incorporated to the already-shipped >> pseudo-elements as well. >> >> On Thursday, June 4, 2026 at 11:01:29 PM UTC+3 Daniil Sakhapov wrote: >

no response to the web feature >>>> question. Reading the guidance >>>> , >>>> I think probably you should request a new web feature ID for this

sounds good to me! > > Can you share anything about planned timeframe for next milestones on the > eval suite and open sourcing work? When should API owners expect to > check

enough reason to do this > given they're cheap to support. LGTM1. > > On Wednesday, June 17, 2026 at 1:34:34 AM UTC-7 mt...@igalia.com > wrote: > > > It looks

be fine to remove quicker but this is fine. /Daniel On 2026-06-17 17:12, Yoav Weiss (@Shopify) wrote: > LGTM1 to deprecate and remove > > On Tuesday, June 16, 2026 at 2:31:17

28 PM To: Alex Russell ; blink-dev Cc: Huanpo Lin ; Yoav Weiss ; Chromestatus Subject: [EXTERNAL] Re: [blink-dev] Re: Intent to Ship: Speculation rules: form_submission field LGTM2

updates related to any of the data Mike asked for here? Best, Alex On Sunday, April 19, 2026 at 7:35:42 AM UTC-7 Mike Taylor wrote: > On 4/16/26 2:31 am, Yoav Weiss (@Shopify) wrote

animation attribute to the AnimationEvent and >>> TransitionEvent interfaces. This attribute returns the associated Animation >>> object that triggered

WPTs seem to be failing, is that expected? (including one >>> overhang-spaces).* >>> ruby-overhang-spaces-vertical-003.html >>> seems >>

an FYI to the tag? I think we want their > help in making sure that all interfaces that could add such a > method do so. > > > > > > How do I do that? It seems all TAG templates

WG) to a spec that already has a TAG review. In the past, this type of >> small addition to an already reviewed spec was usually exempted from a new >> TAG review. We can request

spec PR to reflect the resolution: Change path-length > property value type from number to length by viralipurbey · Pull Request > #1118 · w3c/svgwg . > > > > Is there

is intended to replace our usage > of libxml2 (written in C) with a safe alternative. We are > in the process of deprecating XSLT, see > https://chromestatus.com/feature

? According to this CL , the tests were originally moved to wpt_internal because they "need to load JS modules to continue using Mojo JS bindings. JS modules cannot be loaded from

is close to complete. /Daniel On 2026-06-06 01:09, 'Stephanie Zhang' via blink-dev wrote: > I'll update the ChromeStatus descriptions and explainers with the new

in order to give more time to address some of the feedback. > > On Tue, May 5, 2026 at 3:58 PM 'Thomas Nguyen' via blink-dev < > blin...@chromium.org> wrote:

WebKit is currently implementing `alpha()`, and they have raised a new issue[1] with the CSSWG. I think we should wait for the CSSWG's decision