[blink-dev] Intent to Experiment: WebAuthn attestationFormats

Contact emails...@chromium.org Specification https://w3c.github.io/webauthn/#dom-publickeycredentialcreationoptions-attestationformats Summary Support the attestationFormats field from WebAuthn L3. WebAuthn L3 supports a site expressing an ordered preference for credential attestation formats in

Re: [blink-dev] Intent to Ship: Compression dictionary transport with Shared Brotli and Shared Zstandard

LGTM3 On 8/28/24 4:25 PM, Chris Harrelson wrote: LGTM2 On Wed, Aug 28, 2024 at 11:10 AM Alex Russell wrote: LGTM1. Congrats, all. This is a big deal! On Tuesday, August 27, 2024 at 10:06:16 AM UTC-7 Patrick Meenan wrote: It's probably worth mentioning that, even though the

Re: [blink-dev] Intent to Ship: Compression dictionary transport with Shared Brotli and Shared Zstandard

LGTM2 On Wed, Aug 28, 2024 at 11:10 AM Alex Russell wrote: > LGTM1. Congrats, all. This is a big deal! > > On Tuesday, August 27, 2024 at 10:06:16 AM UTC-7 Patrick Meenan wrote: > >> It's probably worth mentioning that, even though the spec is in the IETF >> process, there was heavy involvement

Re: [blink-dev] Intent to Ship: relaunch Intl Locale Info feature in newly added functions

Does this feature change the behavior of existing web-exposed APIs for Locale? If so, what is the compat risk of breaking existing sites? On Thu, Aug 22, 2024 at 4:11 PM Chromestatus < ad...@cr-status.appspotmail.com> wrote: > Contact emails ft...@google.com > > Explainer None > > Specification h

Re: [blink-dev] Intent to Ship: Private Aggregation API: client-side contribution merging

LGTM3 On Wed, Aug 28, 2024 at 3:25 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM2 > > On Tue, Aug 27, 2024 at 6:32 PM Vladimir Levin > wrote: > >> This looks like a fairly minor improvement to the API. It seems like the >> change would allow more contributions without increasi

Re: [blink-dev] Re: Intent to Ship: Web Serial: connected attribute and RFCOMM connection events

On Wed, Aug 28, 2024 at 2:38 PM Reilly Grant wrote: > On Wed, Aug 28, 2024 at 11:22 AM Vladimir Levin > wrote: > >> >> On Wed, Aug 28, 2024 at 12:34 PM 'Ajay Rahatekar' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Ty, Will do. >>> >>> On Wednesday, August 28, 2024 at 9:02:31 AM UTC-7

[blink-dev] Intent to Ship: Add bugfix version number to User-Agent string on Bling

Contact emails janice...@chromium.org, miketa...@chromium.org Explainer None. This is a minor change. Specification https://www.rfc-editor.org/rfc/rfc9110#field.user-agent Summary User Agent (UA) strings in Chromium have been moving towards reducing or freezing information - but until WebKi

[blink-dev] Intent to Ship: Shared Storage: Allowing Cross-Origin Script in addModule & Aligning createWorklet

Intent to Ship: Shared Storage: Allowing Cross-Origin Script in addModule & Aligning createWorklet Contact emailscam...@chromium.org, jkar...@chromium.org, yao...@chromium.org, ashame...@google.com Explainerhttps://github.com/WICG/shared-storage/blob/main/README.md Specificationhttps://github.com/

Re: [blink-dev] Re: Intent to Ship: Web Serial: connected attribute and RFCOMM connection events

On Wed, Aug 28, 2024 at 11:22 AM Vladimir Levin wrote: > > On Wed, Aug 28, 2024 at 12:34 PM 'Ajay Rahatekar' via blink-dev < > blink-dev@chromium.org> wrote: > >> Ty, Will do. >> >> On Wednesday, August 28, 2024 at 9:02:31 AM UTC-7 sligh...@chromium.org >> wrote: >> >>> Please send this as an FYI

Re: [blink-dev] Re: Intent to Ship: Web Serial: connected attribute and RFCOMM connection events

On Wed, Aug 28, 2024 at 12:34 PM 'Ajay Rahatekar' via blink-dev < blink-dev@chromium.org> wrote: > Ty, Will do. > > On Wednesday, August 28, 2024 at 9:02:31 AM UTC-7 sligh...@chromium.org > wrote: > >> Please send this as an FYI to the TAG. >> >> LGTM1 >> >> On Friday, August 23, 2024 at 10:05:35 

Re: [blink-dev] Intent to Ship: Compression dictionary transport with Shared Brotli and Shared Zstandard

LGTM1. Congrats, all. This is a big deal! On Tuesday, August 27, 2024 at 10:06:16 AM UTC-7 Patrick Meenan wrote: > It's probably worth mentioning that, even though the spec is in the IETF > process, there was heavy involvement with w3c and whatwg as well. The w3c > TAG performed several review

Re: [blink-dev] Intent to Ship: Direct Sockets API

The Promise returned by the "opened" attribute serves that purpose. We used this pattern because it aligns with the WebSocketStream and WebTransport constructors. Reilly Grant | Software Engineer | reil...@chromium.org | Google Chrome On Wed, Aug 28, 2024 at 8:55 A

Re: [blink-dev] Intent to Ship: Direct Sockets API

On Mon, Aug 19, 2024 at 6:46 AM 'Randell Jesup' via blink-dev < blink-dev@chromium.org> wrote: > This was not closed by Mozilla with no opinion, it was closed as Harmful. > Hi Randell! I suspect this is marked as Closed by the tool because the issue

[blink-dev] Re: Intent to Prototype: Realms Initialization Control

Correction: "Requires code in //chrome?" is False, not True (my mistake) On Wednesday 28 August 2024 at 12:49:53 UTC+3 Chromestatus wrote: Contact emails weizm...@gmail.com, yoav@shopify.com Explainer https://github.com/WICG/Realms-Initialization-Control Specification https://github.com/W

[blink-dev] Re: Intent to Ship: Web Serial: connected attribute and RFCOMM connection events

Ty, Will do. On Wednesday, August 28, 2024 at 9:02:31 AM UTC-7 sligh...@chromium.org wrote: > Please send this as an FYI to the TAG. > > LGTM1 > > On Friday, August 23, 2024 at 10:05:35 AM UTC-7 ajayra...@google.com > wrote: > >> >> Contact emails >> >> mattre...@google.com >> >> Explainer >> >

Re: [blink-dev] Intent to ship: WebGPU: Dual source blending

LGTM3 (after two LGTM1s from Alex and Yoav). The finch flag is just a followup on Domenic's question. It seems the issue is that the documented flag doesn't actually correspond to the on-off switch for this feature so please update the finch flag documentation to reflect the correct switch. Ju

[blink-dev] Re: Intent to Ship: Web Serial: connected attribute and RFCOMM connection events

Please send this as an FYI to the TAG. LGTM1 On Friday, August 23, 2024 at 10:05:35 AM UTC-7 ajayra...@google.com wrote: > > Contact emails > > mattreyno...@google.com > > Explainer > > https://github.com/WICG/serial/blob/main/EXPLAINER_BLUETOOTH.md > > Specification > > https://wicg.github.io/s

Re: [blink-dev] Intent to ship: WebGPU: Dual source blending

Hey folks, LGTM1 with nits. First, it would be good for y'all to FYI this to the TAG, even if you don't block on review. I agree it's small and would wave it through. I know Daniel has questions about the Finch flag name, so would be good to have those sorted before this goes out too. Thanks,

Re: [blink-dev] Intent to Ship: Direct Sockets API

In today's API OWNERS meeting, Jeff raised the concern that this API design doesn't follow our general guidance for having a Promise-returning `request*()` method that integrates with the Permissions API and allows the UA to inject controls (including, potentially, user prompts). This is our lo

[blink-dev] Intent to Ship: allow more pseudo-elements and pseudo-classes after ::part()

Contact emailsdba...@chromium.org ExplainerNone Specificationhttps://drafts.csswg.org/css-shadow-parts-1/#part Summary CSS selectors that use the ::part() pseudo-element are allowed to have other CSS pseudo-elements (except ::part()) and many types of other CSS pseudo-classes after them. (Combi

[blink-dev] Ready for Developer Testing: Escape "<" and ">" in attributes on serialization

Contact emails securit...@google.com Specification https://github.com/whatwg/html/issues/6235 Summary Escape "<" and ">" in values of attributes on serialization. This mitigates the risk of mutation XSS attacks, which occur when value of an attribute is interpreted as a start tag token after

Re: [blink-dev] Intent to Ship: Direct Sockets API

LGTM2 On 8/28/24 8:03 AM, Yoav Weiss (@Shopify) wrote: LGTM1 - the use case is clear, as well as the dangers of enabling this over the open web. Confining this API to IWAs seems to strike a reasonable balance. On Mon, Aug 19, 2024 at 3:46 PM 'Randell Jesup' via blink-dev wrote: This w

Re: [blink-dev] Intent to Ship: Direct Sockets API

LGTM1 - the use case is clear, as well as the dangers of enabling this over the open web. Confining this API to IWAs seems to strike a reasonable balance. On Mon, Aug 19, 2024 at 3:46 PM 'Randell Jesup' via blink-dev < blink-dev@chromium.org> wrote: > This was not closed by Mozilla with no opinio

Re: [blink-dev] Intent to ship: WebGPU: Dual source blending

On Wed, Aug 28, 2024 at 12:36 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > On Fri, Aug 23, 2024 at 2:46 PM 'François Beaufort' via blink-dev < > blink-dev@chromium.org> wrote: > >> Adding +Corentin Wallez to the thread >> >> On Fri, Aug 23, 2024 at 2:29 PM François Beaufo

Re: [blink-dev] Intent to ship: WebGPU: Dual source blending

LGTM1 On Fri, Aug 23, 2024 at 2:46 PM 'François Beaufort' via blink-dev < blink-dev@chromium.org> wrote: > Adding +Corentin Wallez to the thread > > On Fri, Aug 23, 2024 at 2:29 PM François Beaufort > wrote: > >> >> >> On Fri, Aug 23, 2024 at 7:01 AM Domenic Denicola >> wrote: >> >>> >>> >>> O

Re: [blink-dev] Intent to Ship: scheduler.yield()

I was out while this thread happened, but just wanted to chime in and say I'm super excited for this shipping!! On Sat, Aug 24, 2024 at 12:22 AM Scott Haseley wrote: > Thanks all! > > This will be enabled in M129. (Note: this just missed the M129 branch, so > it wasn't in the initial Chrome Beta

Re: [blink-dev] Intent to Ship: Private Aggregation API: client-side contribution merging

LGTM2 On Tue, Aug 27, 2024 at 6:32 PM Vladimir Levin wrote: > This looks like a fairly minor improvement to the API. It seems like the > change would allow more contributions without increasing performance > concerns. Please let me know if there are any subtleties that I may have > missed. > > L

[blink-dev] Intent to Prototype: Realms Initialization Control

Contact emails weizman...@gmail.com, yoav.we...@shopify.com Explainer https://github.com/WICG/Realms-Initialization-Control Specification https://github.com/WICG/Realms-Initialization-Control Summary Support a new CSP directive which points to a remote (first party) script file to be loaded

Re: [blink-dev] Intent to Deprecate and Remove: Remove expectedImprovement in DelegatedInkTrailPresenter

LGTM2 On Monday, August 26, 2024 at 6:50:16 PM UTC+2 sahir@microsoft.com wrote: > Done! Thank you. > > On Monday, August 26, 2024 at 9:41:45 AM UTC-7 mike...@chromium.org wrote: > >> Also, would you remind requesting reviews for Enteprise, Debuggability, >> and Testing in the chromestatus e