be nice to resolve (and > I see that there's a pending PR to resolve issue 88 > ) > in the near future, but I don't think we need to block on them (as long as > they get addressed

Thank you to *chrishtr@*, *miketaylr@*, and *yoavweiss@* for the LGTMs! >> (and *barryp@* for your guidance!) >> >> I'm happy to report that this feature

I wanted to officially close the loop on this thread that we no longer plan to ship PRTs given the decision not to ship IP Protection. Eric On Wed, Aug 20, 2025 at 11:07 AM Yoav Weiss (@Shopify

, I intent to implement the percentage unit support for context-2d-letterspacing separately at a later time. Thank you. 2025년 12월 8일 월요일 PM 7시 21분 41초 UTC+9에 一丝님이 작성: > I'm wondering

and reference to existing browser tests: > > Web Platform Tests or other automated test description > The pseudo-wpt test is implemented here > chrome/test/data/controlled_frame

a fresh intent for this? That would enable the API owners tooling to pick it up and ensure it's properly reviewed. On Mon, Dec 29, 2025 at 7:12 PM Maciej Czarnecki wrote: > Refreshed

follow up to get that article and codepens fixed. On Tue, Dec 23, 2025 at 4:30 AM PhistucK wrote: > I know it has been a while, but is the RFC up to date? > https://developer.chrome

LGTM to experiment M144-M148 inclusive On Wednesday, December 17, 2025 at 6:57:15 PM UTC+1 Minh Le wrote: > Dear Blink-dev owners, > > I added "Experiment goals"

select support to the listbox rendering > mode, including single-select and multi-select in listbox mode. The listbox > rendering mode means that the select element is rendered

should apply to existing >>>>> installations, and allowing removal of the 'update check throttle' that >>>>> user agents currently need

be useful to add a section to the explainer to outline the >> differences and relationship to Trusted Types. >> >> >>> >>>> >>>

m happy to see this ship and continue to iterate if > needed. > > > On Wed, Dec 17, 2025 at 10:12 AM Chris Harrelson > wrote: > >> LGTM1 >> >> On Wed

was able to test >> what PayPal does on Android. New pop-up behavior should be available on >> Stable in 26Q2, after Android 17 is released. >> >> Best, >

Functionality added to the WebGPU spec after its first shipment in a >>> browser. Adds a new scope to the uniformity analysis and changes which >>> parts of the language

navigationtransition-to >> >> *Specification* >> https://html.spec.whatwg.org/#dom-navigationtransition-to >> >> *Summary* >>

the time to summarize my reasoning here for those who are interested: > > - The debate in this space is fundamentally a tradeoffs among multiple > goals all important to Chromium

I managed to track down this open issue > , which has some > discussions around the `unadjustedMovement` flag support on Linux & > other platforms. > > For the other

d like to ship it separately. > > LGTM2 > > > >> >> On Fri, Dec 12, 2025 at 3:36 AM TAMURA, Kent wrote: >> >>> *Contact emails* >>>

just wanted to add my thoughts that I think this API would add > a lot of value! I read through the explainer and I think it makes a lot of > sense. 👍 > > I'm the developer Rick

we want to exempt the request from LNA policy, and from what I understand is that we need to add a flag `targetAddressSpace` when making the request to our API server, for eg: *smoke.our

be able to > quickly revert and handle it. > > On Monday, December 8, 2025 at 2:19:51 PM UTC+1 Daniel Vogelheim wrote: > >> Hi Daniel, et al., >> >> Unfortunately

Does this intent deprecate or change behavior of existing > APIs, such that it has potentially high risk for Android > WebView-based applications? > > /No information

been exposed to many paint-related apis (like LCP), for years already. This new API doesn't change in any way what is exposed to developers in Chromium-- but today these values

be happy to. > > -mike > > On Thursday, November 20, 2025 at 5:41:06 PM UTC+1 Mike West > wrote: > > (Apologies, Alex; you're getting this twice because I >

those people to > know what they need. > > /Daniel > On 2025-12-03 03:05, TAMURA, Kent wrote: > > LGTM1. > This looks a reasonable behavior change, and compatibility

t seem to have worried too much about this so them > not saying anything for so long I consider approval by default. But > you may want to let them know that Chromium now plans to ship

I seem to remember developers trying background fetch, but having issues with it due to implementation bugs. Also, "back in the day", Safari were more interested in adopting

> methods to Map and WeakMap. These methods either return the value > associated with a key, or insert a default value, and then return that > value, simplifying handling of

very excited to see this ship! IMHO PEPC opens up a new sweet spot in the tradeoff space here for a wide variety of use cases, I can't wait to see it deployed in other cases too. Agreed

- excited to see this ship! > > On Wed, Nov 19, 2025 at 12:05 PM 'Adam Argyle' via blink-dev < > blink-dev@chromium.org> wrote: > >> +1 positive developer