Re: [blink-dev] Intent to Ship: Back/forward cache NotRestoredReasons API

On Thu, Feb 22, 2024 at 4:20 PM Yuzu Saijo wrote: > Thanks Domenic for bringing up the concerns! > >- I found >performance-navigation-timing-navigation-failure.tentative.window.js > >

Re: [blink-dev] Intent to Ship: Back/forward cache NotRestoredReasons API

Thanks Domenic for bringing up the concerns! - I found performance-navigation-timing-navigation-failure.tentative.window.js

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

LGTM2 On Thu, Feb 22, 2024 at 5:20 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > Thanks for diving into the samples. Sounds like the breakage risk here is > indeed low. > > On Wed, Feb 21, 2024 at 8:15 PM Brad Triebwasser > wrote: > >> Sure, I checked 10 unique origins

Re: [blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

LGTM3!! On Thu, Feb 22, 2024 at 4:07 AM Chris Harrelson wrote: > Thanks! > > LGTM2 > > On Wed, Feb 21, 2024 at 11:03 AM Mattias Buelens < > mattias.buel...@gmail.com> wrote: > >> Thanks Chris, they're all blue now. >> >> Op woensdag 21 februari 2024 om 18:09:55 UTC+1 schreef chri...@google.com

Re: [blink-dev] Intent to Ship: Shadow root clonable attribute

Thank you all! On Tue, Feb 20, 2024 at 10:43 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM3 > > On Monday, February 19, 2024 at 1:27:26 PM UTC+1 Manuel Rego wrote: > >> LGTM2. >> >> On 17/02/2024 02:40, Mason Freed wrote: >> > On Fri, Feb 16, 2024 at 6:30 AM Mike Taylor > >

[blink-dev] Re: Intent to Prototype: Used color scheme root scrollbars

*"Therefore, it seems like this feature doesn't have to go through the Blink process."* Yoav, thank you for the feedback! Yeah, I am trying to clarify the process and get consensus for the next steps. *"This is fantastic! Is there a flag for this?"* Yes! William, you can enable the feature

[blink-dev] Intent to Experiment: FedCM multi IDP in single get() call

Contact emails n...@chromium.org Explainer The Federated Credential Management (FedCM) API currently only allows one identity provider (IDP) to be used when performing federated login in a website. We would like to experiment with allowing multiple providers to be specified in a single

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

LGTM1 Thanks for diving into the samples. Sounds like the breakage risk here is indeed low. On Wed, Feb 21, 2024 at 8:15 PM Brad Triebwasser wrote: > Sure, I checked 10 unique origins (skipping duplicate pu707ev.com > subdomains which make up half of the sampled domains) listed in >

Re: [blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

Thanks Chris, they're all blue now. Op woensdag 21 februari 2024 om 18:09:55 UTC+1 schreef chri...@google.com: > Hi, > > Please start the reviews for the 5 other areas shown below in your > chromestatus entry (once you've done show they should turn blue, not gray): > > [image: Screenshot

Re: [blink-dev] Intent to Ship: Remove "window-placement" alias for permission and permission policy "window-management"

Sure, I checked 10 unique origins (skipping duplicate pu707ev.com subdomains which make up half of the sampled domains) listed in https://chromestatus.com/metrics/feature/timeline/popularity/4448. 4 of them reference: https://cdn.jsdelivr.net/gh/cffgnu/qhdd/asset/responsive.min.js. I won't post

Re: [blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

Thanks! LGTM2 On Wed, Feb 21, 2024 at 11:03 AM Mattias Buelens wrote: > Thanks Chris, they're all blue now. > > Op woensdag 21 februari 2024 om 18:09:55 UTC+1 schreef chri...@google.com: > >> Hi, >> >> Please start the reviews for the 5 other areas shown below in your >> chromestatus entry

Re: [blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

Hi, Please start the reviews for the 5 other areas shown below in your chromestatus entry (once you've done show they should turn blue, not gray): [image: Screenshot 2024-02-21 9.08.57 AM.png] On Wed, Feb 21, 2024 at 8:03 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > >

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

Never mind. My mail was backed up and I hadn't seen that it was already approved, thus no longer on the list. All is well, and my LGTM1 is actually a bonus LGTM4 /Daniel On 2024-02-21 17:23, Daniel Bratell wrote: This doesn't show up in the shipping status in chromestatus so it's not on

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

On Wed, Feb 21, 2024 at 11:25 AM Dustin Mitchell wrote: > Thanks for the comments! > > On Tue, Feb 20, 2024 at 11:10 AM Vladimir Levin > wrote: > >> >> >> On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Contact

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

LGTM1 On Wed, Feb 21, 2024 at 8:25 AM 'Dustin Mitchell' via blink-dev < blink-dev@chromium.org> wrote: > Thanks for the comments! > > On Tue, Feb 20, 2024 at 11:10 AM Vladimir Levin > wrote: > >> >> >> On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev < >> blink-dev@chromium.org>

Re: [blink-dev] Intent to Ship: 'priority' HTTP request header

LGTM3 On Wednesday, February 21, 2024 at 8:58:42 AM UTC-8 Chris Harrelson wrote: > LGTM2 > > On Tue, Feb 20, 2024 at 4:12 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> LGTM1 >> >> Thanks for catching us up here! >> >> On Fri, Feb 16, 2024 at 4:15 PM Patrick Meenan >> wrote:

Re: [blink-dev] Intent to Ship: 'priority' HTTP request header

LGTM2 On Tue, Feb 20, 2024 at 4:12 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > Thanks for catching us up here! > > On Fri, Feb 16, 2024 at 4:15 PM Patrick Meenan > wrote: > >> Contact emailspmee...@google.com >> >> ExplainerNone >> >>

[blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

Hey folks, I also appreciate the quality of the design work here, but we need developer interest to be able to launch features out ahead of other engines. Was an OT done? What other signals do we have to go on? Best, Alex On Tuesday, February 20, 2024 at 10:56:21 PM UTC-8 Yoav Weiss wrote:

Re: [blink-dev] Re: Intent to Ship: WebSocketStream

Hey Adam, Sorry for the slow follow up. Were there folks beyond the Deno ecosystem that expressed interest and/or satisfaction with the design? We're need to make a case in API OWNERS that there's enough developer interest to surmount the lack of other vendor interest. Are you able to share

Re: [blink-dev] Intent to Ship: Private Network Access permission to relax mixed content

LGTM3 On Thursday, February 15, 2024 at 7:57:00 AM UTC-8 Mike Taylor wrote: > LGTM2 > On 2/15/24 4:55 AM, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > On Thu, Feb 15, 2024 at 9:51 AM 'Yifan Luo' via blink-dev < > blink-dev@chromium.org> wrote: > >> OT findings: >> >>

Re: [blink-dev] Intent to Ship: Private Network Access permission to relax mixed content

LGTM3 On Thu, Feb 15, 2024 at 7:56 AM Mike Taylor wrote: > LGTM2 > On 2/15/24 4:55 AM, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > On Thu, Feb 15, 2024 at 9:51 AM 'Yifan Luo' via blink-dev < > blink-dev@chromium.org> wrote: > >> OT findings: >> >>

Re: [blink-dev] Intent to Ship: Sec-CH-UA-Form-Factor client hint

Thanks for the comments! On Tue, Feb 20, 2024 at 11:10 AM Vladimir Levin wrote: > > > On Tue, Feb 20, 2024 at 7:06 AM 'Dustin Mitchell' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emailsdjmit...@chromium.org >> >> Explainer >>

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

This doesn't show up in the shipping status in chromestatus so it's not on our radar. My LGTM1 still stands, but it can easily be forgotten, and we might miss some important review step, if it's not there. /Daniel On 2024-02-16 18:14, Joey Arhar wrote: > Is this the relevant explainer

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

LGTM1 /Daniel On 2024-02-16 18:14, Joey Arhar wrote: > Is this the relevant explainer (referenced from the PR below): https://github.com/WICG/sanitizer-api/blob/main/explainer.md Yes, as far as I know. > This seems positive, right? Whoops, meant to put positive. I updated the chromestatus.

Re: [blink-dev] Intent to Ethe xperiment: Document Subtitle (Fix PWA app titles)

Hola Manuel, Thanks for the heads up. In order for this to be an HTML PR, it requires interest from another vendor . I'll submit the updated explainer for cross-vendor position requests and follow-up on their new positions which may mean I could

Re: [blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

LGTM1 Thanks for catching us up here!! On Wed, Feb 21, 2024 at 4:57 PM Mattias Buelens wrote: > Contact emails > > mattias.buel...@gmail.com > > Explainer > > > https://github.com/whatwg/streams/blob/main/readable-stream-async-iteration-explainer.md > > Specification > >

[blink-dev] Intent to Prototype and Ship: Streams API: ReadableStream async iteration

Contact emails mattias.buel...@gmail.com Explainer https://github.com/whatwg/streams/blob/main/readable-stream-async-iteration-explainer.md Specification https://streams.spec.whatwg.org/#rs-asynciterator Summary The streams APIs provide ubiquitous, interoperable primitives for creating,

Re: [blink-dev] Intent to Experiment: Document Subtitle (Fix PWA app titles)

On 20/02/2024 18:47, 'Diego Gonzalez' via blink-dev wrote: Specification https://github.com/whatwg/html/compare/main...diekus:html:main Should this be an actual HTML PR so discussion with third parties can happen

Re: [blink-dev] Re: Intent to Ship: setHTMLUnsafe and parseHTMLUnsafe

LGTM3 On 21/02/2024 07:48, Yoav Weiss (@Shopify) wrote: LGTM2 On Wednesday, February 21, 2024 at 6:19:50 AM UTC+1 Domenic Denicola wrote: LGTM1. I recall these methods getting lots of good design review and discussion in the PR, from multiple parties. I'm excited to see them ship.