Re: [blink-dev] Re: Intent to Ship: Stricter *+json MIME token validation for JSON modules

LGTM2 On 9/22/25 2:41 p.m., Alex Russell wrote: LGTM1 On Monday, September 22, 2025 at 9:00:30 AM UTC-7 Chromestatus wrote: *Contact emails* issackj...@microsoft.com, dan...@microsoft.com *Explainer* None *Specification* https://mimesniff.spec.whatwg.org/#parse-a-mime

Re: [blink-dev] Intent to Ship: WebGPU: Texture formats tier1 and tier2

As someone less familiar with this area I'm having a hard time understanding what this is for. Could you share more context about this addition and the use cases motivating it, or even better, put together a short explainer doc that does so? -- Dan On Friday, September 19, 2025 at 7:59:01 AM UT

Re: [blink-dev] Intent to Ship: FedCM—Support showing third-party iframe origins in the UI

LGTM1 On Thursday, September 18, 2025 at 6:08:13 AM UTC-7 Yi Gu wrote: > Hi Yoav, > > Yes, this is controlled by developers. > > Currently, when fetching the client metadata endpoint, the browser sends > the API caller's origin and client ID to the IdP. With this proposal, if > the API is calle

[blink-dev] Re: Intent to Ship: WebTransport Application Protocol Negotiation

Hey Victor, As there's no explainer, can you outline what the use-cases for protocol negotiation are? The linked part of the spec does not provide clarity as to why this is valuable, who it's valuable to, or why we should support it. That is, we are always trying to understand "*does this featu

Re: [blink-dev] Intent to Ship: FedCM—Support Structured JSON Responses from IdPs

Thanks for breaking this out. Generally, explainers are meant to foreground the code that users of APIs will encounter, and explain how changes in API surface solve the problems we are trying to handle. This explainer has WebIDL instead, which isn't how we normally do things. I also don't see a

Re: [blink-dev] Intent to Ship: Mobile and desktop parity for select element rendering modes

LGTM3 On Wednesday, September 17, 2025 at 8:38:36 AM UTC-7 Daniel Bratell wrote: > LGTM2 conditional on the the spec landing and known accessibility issues > taken care of. > > /Daniel > On 2025-09-17 00:57, Joey Arhar wrote: > > I did some testing with TalkBack on android, and I am fixing two i

Re: [blink-dev] Intent to Ship: FedCM—Support Structured JSON Responses from IdPs

explainer updated : FedCM/explorations/structured_data_support.md at main · w3c-fedid/FedCM On Wednesday, September 10, 2025 at 8:43:46 PM UTC+5:30 Alex Russell wrote: > I like the change, but the linked "exp

Re: [blink-dev] Intent to Ship: FedCM—Support Structured JSON Responses from IdPs

Explainer updated and answered queries : FedCM/explorations/structured_data_support.md at main · w3c-fedid/FedCM On Wednesday, September 10, 2025 at 8:43:46 PM UTC+5:30 Alex Russell wrote: > I like the chang

[blink-dev] Intent to Ship: Stricter *+json MIME token validation for JSON modules

Contact emails issackj...@microsoft.com, dan...@microsoft.com Explainer None Specification https://mimesniff.spec.whatwg.org/#parse-a-mime-type Summary Reject JSON module script responses whose MIME type's type or subtype contains non‑HTTP token code points (eg spaces) when matched via *+jso

Re: [blink-dev] Re: Intent to Ship: ICU 77 (supporting Unicode 16)

On Thu, Sep 18, 2025 at 3:29 PM Philip Jägenstedt wrote: > On Thu, Sep 18, 2025 at 2:51 PM Mike Taylor > wrote: > >> On 9/18/25 5:54 a.m., Philip Jägenstedt wrote: >> >> Some additional context. Upgrading ICU can break sites and it cannot be >> done with a flag because of the size of the library

[blink-dev] Intent to Prototype: side-relative syntax for background-position-x/y longhands

Contact emails jfernan...@igalia.com Explainer None Specification https://drafts.csswg.org/css-backgrounds-4/#background-position-longhands Summary Defines the background image's position relative to one of its edges. This syntax gives web authors a more flexible and responsive mechanisms to

[blink-dev] Intent to Ship: WebTransport Application Protocol Negotiation

Contact emails vasi...@chromium.org Explainer None Specification https://w3c.github.io/webtransport/#dom-webtransportoptions-protocols Summary WebTransport Application Protocol Negotiation allows negotiation of the protocol used by the web application within the WebTransport handshake. A web