changes indentation to "hanging", that is, all lines except the first > line will be indented. The `each-line` keyword makes indentation to > affect not only the

TC39 proposal to create iterators by sequencing existing iterators. > Introduces Iterator.concat ( ...items ). > > *Blink component* > Blink>JavaScript>Language

with the intent from me, LGTM1. Sorry we didn't have any way in our 'webexposed' tests to double-check for approvals for this sort of new feature (JSON-schema only change

in proportion to both the operating system's and browser's text scale setting. This allows pages that follow best practices around font-relative units (ie use rem and em

minor extension to the scroll-driven animations API. I've written an explainer and updated the chromestatus page with it. Happy to provide further info. On Wed, Jan 14, 2026 at

reviewing this intent. Without the dropEffect fix, the https://wpt.live/html/editing/dnd/drop/025.html WPT prints: "FAIL: drag dropEffect move instead of none dragenter

you can ship on more devices", which developers certainly want, but of course WebGPU must still be usable with the restrictions. We *do* have positive feedback on that, which

my weakness to light :) for sure, others are shipping: https://wpt.fyi/results/fetch/data-urls/processing.any.sharedworker.html?label=experimental&label=master&aligned

shader, to take a texture/sampler variable and assign it into a `let`. Basically provides an alternate name at the moment. In the future, the bindless work will have methods which can

Functionality added to the WebGPU spec after its first shipment in a >> browser. A new TRANSIENT_ATTACHMENT GPUTextureUsage lets developers create >> attachments

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

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

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* >>>

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