Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

On Thu, May 16, 2024 at 10:05 PM Robert Flack wrote: > I believe the reason for waiting is that the intention is to switch to a > different publishing model after level 3 is published? @Patrick H. Lauke > to confirm. > Other than publishing mechanics, was the PR reviewed and good to go? > > O

[blink-dev] Intent to Prototype: No-Vary-Search Hint for Prerender Speculation Rules

Contact emailsdome...@chromium.org, jbro...@chromium.org, liviuti...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main/triggers.md#no-vary-search-hint Specificationhttps://wicg.github.io/nav-speculation/prerendering

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

I believe the reason for waiting is that the intention is to switch to a different publishing model after level 3 is published? @Patrick H. Lauke to confirm. On Thu, May 16, 2024 at 3:41 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Wed, May 15, 2024 at 6:40 PM 'Sahir Vellan

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

On Thu, May 16, 2024 at 11:56 AM Mason Freed wrote: > > On Wed, May 15, 2024 at 9:36 PM Vladimir Levin > wrote: > >> I recall that some of this usage was feature detected: if mutation events >> are supported, use them; otherwise, use something else. Unfortunately, that >> makes it difficult to e

Re: [blink-dev] Intent to Experiment: Page Embedded Permission Control

Sorry - got too excited. LGTM to experiment % requesting the Security, Privacy, Debuggability bits. On 5/16/24 1:28 PM, Mike Taylor wrote: Thanks - LGTM to experiment from M126 to M131 inclusive. On 5/16/24 1:26 PM, Penelope McLachlan wrote: Sorry for not including that! Origin trial deskto

Re: [blink-dev] Intent to Experiment: Page Embedded Permission Control

Thanks - LGTM to experiment from M126 to M131 inclusive. On 5/16/24 1:26 PM, Penelope McLachlan wrote: Sorry for not including that! Origin trial desktop last: 131 On Thu, May 16, 2024 at 10:23 AM Mike Taylor wrote: Hi! I see a start milestone of 126 - do you have a desired milest

Re: [blink-dev] Intent to Experiment: Page Embedded Permission Control

Sorry for not including that! Origin trial desktop last: 131 On Thu, May 16, 2024 at 10:23 AM Mike Taylor wrote: > Hi! > > I see a start milestone of 126 - do you have a desired milestone end date? > On 5/16/24 1:20 PM, 'Penelope McLachlan' via blink-dev wrote: > > Contact emails > > andypa...@

Re: [blink-dev] Intent to Experiment: Page Embedded Permission Control

Hi! I see a start milestone of 126 - do you have a desired milestone end date? On 5/16/24 1:20 PM, 'Penelope McLachlan' via blink-dev wrote: Contact emails andypa...@google.com , pjmclach...@google.com , eng...@google.com

[blink-dev] Intent to Experiment: Page Embedded Permission Control

Contact emails andypa...@google.com, pjmclach...@google.com, eng...@google.com Explainer https://github.com/WICG/PEPC/blob/main/explainer.md Specification none Summary Provide a new HTML element that interacts with the permission flow. The permission prompt is currently triggered directly fr

Re: [blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

> Each grace period entry has its own expiration date, depending on when the site applied for the deprecation trial. To clarify, the currently published expiration date is June 30, but we are assessing how grace periods will be used after that date. This feature, though, is intended to help sit

[blink-dev] Intent to Prototype: AudioContext.onerror

Contact emails hongc...@chromium.org, mjwil...@chromium.org, sinafir...@chromium.org Explainer None Specification https://github.com/WebAudio/web-audio-api/pull/2580 Summary Introduces an event listener on AudioContext to notify developers of audio device or rendering system failures. Blink

Re: [blink-dev] Intent to Ship: Deprecate Mutation Events

On Wed, May 15, 2024 at 9:36 PM Vladimir Levin wrote: > I recall that some of this usage was feature detected: if mutation events > are supported, use them; otherwise, use something else. Unfortunately, that > makes it difficult to estimate the expected number of breakages. I agree > though that

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

Sounds good - no concerns with shifting the milestones. On 5/16/24 11:53 AM, Nicolás Peña Moreno wrote: We decided to further delay the start of the OT since our partner needs more time before they can put it in front of real users, so the current plan it to do the experiment on milestones 128

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

We decided to further delay the start of the OT since our partner needs more time before they can put it in front of real users, so the current plan it to do the experiment on milestones 128 - 132. On Tuesday, April 23, 2024 at 4:01:15 PM UTC-4 Nicolás Peña Moreno wrote: > I sent this intent b

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

LGTM2 On Thu, May 16, 2024 at 11:16 AM Mike Taylor wrote: > LGTM1, with the commitment to follow up on Permissions API integration > (thanks!). > On 5/15/24 6:34 PM, Reilly Grant wrote: > > LGTM as an IWA OWNER (3x LGTM from Blink API OWNERS are still required > according to the IWA-specific API

Re: [blink-dev] Intent to Ship: Automatic Fullscreen Content Setting

LGTM1, with the commitment to follow up on Permissions API integration (thanks!). On 5/15/24 6:34 PM, Reilly Grant wrote: LGTM as an IWA OWNER (3x LGTM from Blink API OWNERS are still required according to the IWA-specific API launch process

Re: [blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

On Thu, May 16, 2024 at 10:02 AM ChangSeok Oh wrote: > Contact emails > changseok...@bytedance.com, changs...@chromium.org > > Explainer > None > > Specification > https://www.w3.org/TR/css-fonts-5/#font-size-adjust-prop > > Summary > > The font-size-adjust CSS property enhances readability consi

Re: [blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

> Will developers have a way of knowing if the current site (where they may see breakage metrics) is opted-out of the grace period? Google is planning to build a site dashboard where developers can check on the status of their grace period and opt-out values. In the interim, Chrome DevTools sho

[blink-dev] Intent to Ship: CSS font-size-adjust with the two-value syntax

Contact emails changseok...@bytedance.com, changs...@chromium.org Explainer None Specification https://www.w3.org/TR/css-fonts-5/#font-size-adjust-prop Summary The font-size-adjust CSS property enhances readability consistency by adjusting font size based on lowercase letter height rather than

Re: [blink-dev] Intent to Ship: Third-party Cookie Grace Period Opt-Out

This is an odd one, but I agree that it's a web exposed feature and hence should go through the blink process. Thanks for sending this! On Tue, May 14, 2024 at 11:15 PM Anton Maliev wrote: > Contact emails > > amal...@chromium.org > > njeu...@chromium.org > > wanderv...@chromium.org > > Explain

Re: [blink-dev] Intent to Ship: PointerEvent.deviceId for Mult-Pen Inking

On Wed, May 15, 2024 at 6:40 PM 'Sahir Vellani' via blink-dev < blink-dev@chromium.org> wrote: > From my understanding, we need to wait for the PointerEvents spec V3 to be > published before the PR can be merged; this change is slated for the 4th > iteration of the spec. > That's an odd work mode