Re: [blink-dev] Re: Intent to Implement and Ship: ReadableStreamBYOBReader Min Option

Hi Daniel, I’ve updated the MDN Doc . – specifically, in the *Browser compatibility* section, the options.min parameter is now marked as supported starting in Chrome 140. Please let me know if the

Re: [blink-dev] Re: [EXTERNAL] Re: Intent to Ship: Support font-feature-settings descriptor in @font-face rule

Hi Philip, Daniel, I have initiated the API owner review along with other reviews, which should now be visible. A separate email has been sent for the review. Please take a moment to look over it. Thank you for your time. Thank you, Sejal From: Philip Jägens

Re: [blink-dev] Re: Intent to Ship: Secure Payment Confirmation: Browser Bound Keys

LGTM3 On Thursday, June 26, 2025 at 4:44:15 PM UTC+2 Stephen McGruer wrote: > Thanks Daniel! > > > I'm not sure who "we" are in all that, > > Very fair, apologies about the ambiguous communication 😅. In general I > meant 'we the Chromium community, who were/are happy to ship WebAuthn with > a

Re: [blink-dev] Intent to Ship: Uint8Array to/from base64 and hex

LGTM1 /Daniel On 2025-06-27 00:27, Rezvan Mahdavi Hezaveh wrote: Contact emails rez...@chromium.org, s...@chromium.org Explainer None Specification https://tc39.es/proposal-arraybuffer-base64/spec Summary base64 is

[blink-dev] Re: Intent to Experiment: Extended lifetime shared workers

LGTM to experiment 139-142 inclusive On Monday, June 30, 2025 at 12:34:52 PM UTC+2 Chromestatus wrote: > Contact emails dome...@chromium.org, yyanagis...@chromium.org > > Explainer > https://gist.github.com/domenic/c5bd38339f33b49120ae11b3b4af5b9b#file-1-explainer-md > > > Specification None

Re: [blink-dev] Re: Intent to Ship: CSS scroll-target-group property

LGTM3 On Thu, Jun 26, 2025 at 10:03 AM Jeffrey Yasskin wrote: > +Lola Odelola and +Florian Scholz > as the chairs of the Docs CG, who'll have a > better sense of the right answer here. > > My guess is that it'll work better in the long run to start with putting > your explanation into the spec

Re: [blink-dev] Re: Intent to Ship: CSS counter() and counters() in alt text of 'content' property

LGTM1 On Wed, Jun 25, 2025 at 12:46 AM Daniil Sakhapov wrote: > For Blink there are no performance issues as counter value calculation is > performed at the same time as for other counters, so it's not really any > different from just using counter(). > > As the real use case for this feature ap

Re: [blink-dev] Intent to Ship: Uint8Array to/from base64 and hex

LGTM3 On Wed, Jul 2, 2025 at 4:51 PM Yoav Weiss (@Shopify) wrote: > LGTM2 > > On Wed, Jul 2, 2025 at 4:38 PM Daniel Bratell wrote: > >> LGTM1 >> >> /Daniel >> On 2025-06-27 00:27, Rezvan Mahdavi Hezaveh wrote: >> >> Contact emails rez...@chromium.org, s...@chromium.org >> >> Explainer None >> >

Re: [blink-dev] Re: Intent to Ship: Stop sending Purpose: prefetch header from prefetches and prerenders

LGTM2 /Daniel On 2025-07-01 09:36, Yoav Weiss (@Shopify) wrote: LGTM1 for a slow roll-out, given the fact that "breakage" may most likely present itself as extra server load. On Tue, Jul 1, 2025 at 5:42 AM Domenic Denicola wrote: We're optimistic that this will result in no "breakage"

Re: [blink-dev] Re: Intent to Ship: Insert CJK inter-script spacing: the CSS `text-autospace` property

LGTM1 /Daniel On 2025-06-17 04:35, Domenic Denicola wrote: Thanks for these updates. Do you have any ideas on when the WebKit difference might be resolved? We shouldn't block shipping on them, but if there's a chance that the initial value might change due to ongoing discussions, it would be

Re: [blink-dev] Re: Intent to Ship: CSS counter() and counters() in alt text of 'content' property

LGTM3 (per Yoav's description) /Daniel On 2025-07-02 17:40, Yoav Weiss (@Shopify) wrote: LGTM2 conditional on two things: 1) Removing the "at risk" label from the spec 2) Including an example in the spec and relevant documentation about *how* developers are supposed to use this. Specifically

Re: [blink-dev] Intent to Ship: Uint8Array to/from base64 and hex

LGTM2 On Wed, Jul 2, 2025 at 4:38 PM Daniel Bratell wrote: > LGTM1 > > /Daniel > On 2025-06-27 00:27, Rezvan Mahdavi Hezaveh wrote: > > Contact emails rez...@chromium.org, s...@chromium.org > > Explainer None > > Specification https://tc39.es/proposal-arraybuffer-base64/spec > > Summary > > base

Re: [blink-dev] Re: [EXTERNAL] Re: Intent to Ship: Support font-feature-settings descriptor in @font-face rule

This does not show up on the API Owner dashboard in Chromestatus so maybe you have missed pushing it there? There are some other reviews that should be started there at the same time. /Daniel On 2025-07-02 07:04, 'Sejal Anand' via blink-dev wrote: The review for the font-variation-setting

[blink-dev] Re: Intent to Ship: ScrollIntoView container option

LGTM1 On Wednesday, June 25, 2025 at 10:20:00 PM UTC+2 Robert Flack wrote: > I've updated the chromestatus motivation to include a rough example of > what developers do today compared to what this API enables. In particular, > without this API developers building carousel components need to cal

Re: [blink-dev] Re: Intent to Ship: ScrollIntoView container option

LGTM3 (there are two LGTM1 so next is 3). Note Alex' request. /Daniel On 2025-07-02 17:26, Alex Russell wrote: Per conversation at today's API OWNERS, LGTM1 contingent on there being a stand-alone explainer and example code. Bonus points for getting motivating example code into the spec too.

Re: [blink-dev] Re: Intent to Ship: Insert CJK inter-script spacing: the CSS `text-autospace` property

LGTM2 We discussed this in the API owners meeting today (present: Chris, Yoav, Vlad, Jeffrey, Daniel, Alex, me) and think it makes sense to ship matching the initial value that Safari already shipped. At that point we expect https://github.com/w3c/csswg-drafts/issues/12386 to be resolved to match

[blink-dev] Re: Intent to Ship: ScrollIntoView container option

Per conversation at today's API OWNERS, LGTM1 contingent on there being a stand-alone explainer and example code. Bonus points for getting motivating example code into the spec too. Best, Alex On Wednesday, June 25, 2025 at 1:20:00 PM UTC-7 Robert Flack wrote: > I've updated the chromestatus

Re: [blink-dev] Re: Intent to Ship: Stop sending Purpose: prefetch header from prefetches and prerenders

LGTM3 On Wed, Jul 2, 2025 at 7:26 AM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2025-07-01 09:36, Yoav Weiss (@Shopify) wrote: > > LGTM1 for a slow roll-out, given the fact that "breakage" may most likely > present itself as extra server load. > > On Tue, Jul 1, 2025 at 5:42 AM Domenic Denic

Re: [blink-dev] Re: Intent to Ship: Insert CJK inter-script spacing: the CSS `text-autospace` property

LGTM3 On Wednesday, July 2, 2025 at 8:24:18 AM UTC-7 Philip Jägenstedt wrote: > LGTM2 > > We discussed this in the API owners meeting today (present: Chris, Yoav, > Vlad, Jeffrey, Daniel, Alex, me) and think it makes sense to ship matching > the initial value that Safari already shipped. At tha

Re: [blink-dev] Re: [EXTERNAL] Re: Intent to Ship: Support font-feature-settings descriptor in @font-face rule

Hi Sejal, It's great to the progress on this, I believe it's one of the most highly upvoted font-related features. https://chromestatus.com/feature/5102801981800448 still doesn't show up in the list of features to review/approve, please feel free to reach out off list if you can't find the right

Re: [blink-dev] Re: Intent to Ship: CSS counter() and counters() in alt text of 'content' property

LGTM2 conditional on two things: 1) Removing the "at risk" label from the spec 2) Including an example in the spec and relevant documentation about *how* developers are supposed to use this. Specifically for (2), since the presence of `counter()` breaks the "content:" property (as it's invalid s

Re: [EXTERNAL] Re: [blink-dev] Intent to [Experiment] Origin Trial: Incoming Call Notifications

Thanks a lot Domenic! Regards, Diego González (PWA PM @ Edge) From: Domenic Denicola Sent: 02 July 2025 02:27 To: Domenic Denicola Cc: Diego Gonzalez ; blink-dev ; Stanley Hon ; Rob Paveza ; Limin Zhu (Edge) ; Ajay Rahatekar Subject: Re: [EXTERNAL] Re:

[blink-dev] Intent to Ship: Support font-feature-settings descriptor in @font-face rule

Contact emails sejalan...@microsoft.com Explainer None Specification https://www.w3.org/TR/css-fonts-4/#font-rend-desc Summary As CSS allows fine control over font features using 'font-feature-settings' at the element level, Chromium-based browsers currently lack support for these properti