blink-dev

LGTM2 (it took me a minute to realize this exposes the top frame origin to the IDP, and offers a way

Would having this let authors somewhat more easily work around the intentionally-unsupported

IDL is not required in explainers, but surely it is not banned from explainers? Also, the entire

Hey, here's the best practice for testing support for scrollIntoView({container: 'nearest

Hi Alex, WebTransport provides web developers with a networking abstraction that is semantically

Here's the mini explainer from the chrome status entry motivation section: Tier1 lets developers

Contact emails dgr...@chromium.org, p...@chromium.org Explainer https://github.com/w3c/csswg-drafts/

LGTM2 On 9/22/25 2:41 pm, Alex Russell wrote: LGTM1 On Monday, September 22, 2025 at 9:00:30 AM UTC-7

On 9/22/25 11:20 am, Philip Jägenstedt wrote: On Thu, Sep 18, 2025 at 3:29 PM Philip Jägenstedt <

LGTM3 On Wednesday, September 17, 2025 at 8:38:36 AM UTC-7 Daniel Bratell wrote: LGTM2 conditional on

Contact emails jfern...@igalia.com Explainer None Specification https://drafts.csswg.org/css-

from a Web author perspective, it's quite common that we attempt to lock scrolling on the

Contact emails mmo...@google.com Explainer https://github.com/w3c/event-timing/pull/160 Specification

Thank you all! Much appreciated. On Fri, Sep 19, 2025 at 7:59 AM Mike Taylor <miketaylr@chromium.

marking it "test" CL is submitting Yoav Weiss (@Shopify) <yoav...@chromium.org>

Contact emails elad...@chromium.org Specification https://w3c.github.io/mediacapture-region/ Summary

Contact emails hc...@chromium.org Explainer https://github.com/WICG/local-network-access/blob/main/

Contact emails hc...@chromium.org Explainer https://github.com/WICG/local-network-access/blob/main/

Contact emails lwa...@igalia.com Explainer https://github.com/Igalia/explainers/tree/main/nodes-from

Contact emails pme...@chromium.org Explainer https://docs.google.com/document/d/1uAutnUWpC6V-ka_MA-

Contact emails nrose...@chromium.org, vmp...@chromium.org Explainer https://github.com/w3c/csswg-

LGTM3 On Monday, September 15, 2025 at 7:57:44 PM UTC+2 Alex Russell wrote: LGTM2. Jason, Dan and I

Thanks everyone, we are now landing this to M142. FYI, I wanted to call out the two part shipping

Forked the thread, and moved most people to bcc to avoid noise. Hi Jonathan (and Domenic): I already

Quick update on this, due to an implementation bug this change only affected users running with third

Contact emails jja0...@gmail.com Explainer None Specification https://drafts.csswg.org/css-ruby/#

Sure -- just opened https://issues.chromium.org/issues/445215592. Matt On Wednesday, September 10,

We've recently made two changes to this API: 1. The API has been renamed drawElementImage (2d)

If we find anything interesting we definitely will share it, the initial trial that just tested the

Ok, just one more small update, but as we moved forward with the prototype, we managed to narrow down