blink-dev

Background: presentation time itself has been exposed to many paint-related apis (like LCP), for

LGTM3 On 12/3/25 8:12 am, Vladimir Levin wrote: LGTM2 On Wednesday, December 3, 2025 at 11:07:16 AM

This is a good point, Dirk. My understanding of the ecosystem is that users who were previously

LGTM3 On Wed, Dec 3, 2025 at 4:29 PM Daniel Bratell <brat...@gmail.com> wrote: LGTM2 I can

Daniel Bratell <brat...@gmail.com> writes: > LGTM3 > > Other vendors don't seem

Amazing news! Great to see Chromium reconsidering JPEG XL given all it's benefits. Le vendredi 21

This is purely from memory, and could be inaccurate, but I seem to remember developers trying

LGTM3 On Tue, Dec 2, 2025 at 9:34 PM Mike Taylor <mike...@chromium.org> wrote: LGTM2 On 12/2/

The relevant Blink objects are garbage-collected (the Supplementable may not be the unique owner, and

Hi all, It's been a while since v139 was released. We've noticed that some Windows machines

Contact emails om...@blockcast.net Explainer https://github.com/kkroo/multicast-in-direct-sockets

Contact emails lemi...@google.com, tun...@google.com Explainer https://github.com/WICG/PEPC/blob/

D'oh. Thank you. On Wednesday, November 26, 2025 at 8:20:03 PM UTC+1 rei...@chromium.org wrote:

LGTM3. I'm very excited to see this ship! IMHO PEPC opens up a new sweet spot in the tradeoff

LGTM3 On Wed, Nov 26, 2025 at 8:16 AM Rick Byers <rby...@chromium.org> wrote: LGTM2 - excited

After a bit more consideration and consultation with a colleague, the WebView team isn't overly

LGTM3 On Tue, Nov 25, 2025 at 8:27 PM Chris Harrelson <chri...@chromium.org> wrote: LGTM2 On

LGTM3 On Wed, Nov 19, 2025 at 7:19 PM Mike Taylor <mike...@chromium.org> wrote: LGTM2 On 11/

Thank you all! This really helps me get started and saves me a lot of time. I appreciate it! mus...@

Thank you everyone! Just wanted to ack the concerns again and will try to report back on any bumps

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

Hello, It occurred to me that document-local terminology likely would have to be conveyed to the

> > Given that this is definitely going to break sites, this should be an Intent to Ship

This makes a lot of sense, thanks. On 11/21/25 4:54 am, 'Dominik Röttsches' via blink-dev

Hello, Unless I'm missing something, the linked "specification" (Issue #694) for FedCM

The Ship information does not appear to have been updated in chromestatus yet. https://chromestatus.

Filed crbug.com/462131663 to raise the question of whether the defaults should be improved. On Wed,

We are _finally_ shipping the feature on M144, after the root cause of the regression got fixed

Contact emails vk...@google.com Explainer https://github.com/explainers-by-googlers/security-info-web

LGTM3 /Daniel On 2025-11-19 17:25, Alex Russell wrote: LGTM2 On Wednesday, November 19, 2025 at 8:24: