Providing inputs to your comments below: > Thanks for the links, I think that the "meaning" in "allowed values and meaning" is supposed to imply that the same

> went to plenary. >> >> >> https://github.com/tc39/ecma402/blob/main/meetings/notes-2025-05-08.md#normative-add-localeprototypegetvariants

It looks to me like the discussion has converged on the >> core aspects of the design. So I'm OK shipping before the PR lands. LGTM1 >> >> However if the WG converges

Functionality added to the WebGPU spec after its first shipment in a browser. The `subgroup_id` and `num_subgroups` built-in values are now available when the subgroups extension

suggest is to test the current behavior and make any changes > you think are necessary for a good user experience, to report that on the > issue and then ship. > > FWIW, I tested

right-to-left mode. When using RTL mode some operators >>> can be mirrored by changing them to another code point (eg a right >>> parentheses becomes a left parentheses

old entry to the new > one. > On 11/5/25 9:07 am, Minseong Kim wrote: > > Oh, I've created a new chromestatus entry and sent an Intent to Ship mail. > He doesn't

as opposed to having the field with some undefined value. Can >>> you comment on this? >>> >>> I'm not sure if that's a common pattern in this space

position relative to one of its edges. >> This syntax gives web authors a more flexible and responsive mechanisms to >> define the background image position, instead

this ought to ship in Chrome 144 (branch date Dec 1). On Wed, Oct 1, 2025 at 8:34 AM Manish Goregaokar wrote: > > What is the API for formatting a Temporal object in a specific locale

have decided to delay our launch by one milestone due >> to a bug that could break certain captive portals on Android ( >> crbug.com/448107420). We are now targeting M142

I wanted to provide an update on the proposed change. > > A single site/bug was brought to my attention, and after reaching out to > the site's team, the issue has been addressed

right place to raise this issue, but I will try to pass this along to the right folks at Cloudflare. On 10/31/25 5:21 am, koitsu wrote: > https://github.com/brave/brave-browser

Reaching out to site owners was mostly for a sanity check that the resource is not expecting to be partitioned for some reason (even though the payloads are known to be identical). If

exposed just to `Window`, despite the spec mentioning exposing it also to dedicated and shared workers. I want to bridge this and make it available to workers as well (without changing

Functionality added to the WebGPU spec after its first shipment in a > browser. Uniform buffers declared in WGSL shaders are no longer required to > have 16-byte alignment on

target milestone to 144) >>> >>> On Wed, Oct 22, 2025 at 5:41 PM Chromestatus < >>> admin@cr-status.appspotmail.com> wrote: >>> >

element tree to >> display and animate participating elements in the transition. Per spec, >> this subtree is constructed when the view transition starts animating

that's up to > the WG and spec editor to solve, not me. :) > > LGTM2 > On 10/24/25 4:49 pm, Nicolás Peña Moreno wrote: > > Yes, the extension is meant to specify optional

LGTM3 to ship and deprecate (but not yet remove). On Fri, Oct 24, 2025 at 8:36 AM Mike Taylor wrote: > LGTM2 > On 10/23/25 3:43 pm, Vladimir Levin wrote: > > Hey, yes you will

Just to be clear: anchored elements *will* respond to transform changes on the anchor, and be re-laid out if necessary, but during animations, layout may "lag behind",

and had to create a Uint8Array view, and some APIs returned different types >> which leading to inconsistency. To improve this, design principles have >> changed[1]

now like to begin the first “Intent > to Ship” step, testing the feature locally. > > I've installed *Chrome Dev 143.x*, where the patch should already be > included

adding support to a new type of value, an Intent to Ship is a better fit than a PSA (see Implementation of existing standard ). Can you please resend? If that's confusing, feel free

would indeed to be nice to consider device mocking for testing. > I think something like this for Bluetooth might be a pattern to follow: > > https://github.com/web-platform

) implementation to include display-p3-linear. > > > On Thu, Oct 23, 2025 at 8:07 AM Philip Jägenstedt > wrote: > > Good catch, gradients in linear color space is

existing mode to JS. Regards, Sergey On Wednesday, October 22, 2025 at 5:11:56 PM UTC+2 Alex Russell wrote: > Heya Sergey, > > This seems like a great addition, but I'm

using the Intent to ship template and posted it to > blink-dev and cc'ed you. > Thanks a bunch for your help and guidance. > > Thanks > Ananta > > ----------

an extension to an existing IWA-only feature. Multicast >> introduces additional privacy concerns because since content is intended >> for consumption by multiple

have responded to > your other comment inline. > > Thanks, > Ashish > > > ------------------------------ > *From:* Rick Byers > *Sent:* Wednesday, October