Re: [blink-dev] Intent to Ship: EditContext API

Changing the event order seems like something you'd be opting into since this API has not shipped yet. Don't use the API, get the existing order, Do use the API, get the more useful order. I'm skeptical this API actually fixes the real issues. The examples are incomplete and therefore

Re: [blink-dev] Intent to Ship: No-Vary-Search support in navigation prefetch cache

On Thu, Nov 9, 2023 at 12:44 AM Yoav Weiss wrote: > Thanks for working on this, as I'm enthusiastically supportive of tackling > this use case! > > One thing I wish y'all have done, and that I haven't seen any evidence of > (but please correct me if I'm wrong) is discuss this design with the

[blink-dev] Intent to Ship: View Transitions: transition types

Contact emailsvmp...@chromium.org, nrosent...@chromium.org Explainer https://github.com/vmpstr/web-proposals/blob/main/explainers/view-transition-types.md Specification https://drafts.csswg.org/css-view-transitions-2/#the-active-view-transition-pseudo Summary This feature allows View

[blink-dev] Intent to Prototype: Allow for WebAuthn credential creation in a cross-origin iframe

Contact emailssmcgr...@chromium.org ExplainerNone Specification https://w3c.github.io/webauthn/#publickey-credentials-create-feature Summary This feature allows web developers to create WebAuthn[0] credentials (that is, "publickey" credentials, aka passkeys) in cross-origin iframes. Two

Re: [blink-dev] Intent to Ship: EditContext API

LGTM4 (yes, a bonus LGTM since I felt ninja'd by Mike and I think this will be a nice addition to the web platform) /Daniel On 2023-11-08 20:42, Mike Taylor wrote: LGTM3 On 11/8/23 12:13 PM, Alex Russell wrote: +1 to the evidence from OT being persuasive. LGTM2 On Wednesday, November 8,

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

If you want to batch it together that sounds fine to me. Can you: * Update the chromestatus entry accordingly (including shipping milestones, updated description, and potentially re-review of privacy security etc) * Land those two PRs for the

Re: [blink-dev] Intent to Ship: Remote Playback API

Hi all, the specification contains numerous (9) references to "user permission", yet there is no section about Permissions API and Permissions Policy integration, as well as Permissions Policy feature/declaration and default allow list. Is this intentional? Of course, this could be accidental

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

Hi Chris, Thanks so much for the quick response. We have not yet shipped the negative targeting work. The absence of these additional changes means that some of the potential adopters of negative targeting can't do so, and so I was indeed proposing to batch these additional changes together

Re: [blink-dev] Intent to Ship: EditContext API

LGTM3 On 11/8/23 12:13 PM, Alex Russell wrote: +1 to the evidence from OT being persuasive. LGTM2 On Wednesday, November 8, 2023 at 8:56:24 AM UTC-8 Rick Byers wrote: It certainly sounds to me that there's additional work to be done here, but I agree with Daniel that changing event

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

Hi Orr, Have you already shipped the negative targeting work? Or are you proposing to batch these additional changes together with that, and consider these new changes thematically related? If not, I think it would be more clear to make a new I2S and chromestatus entry. On Wed, Nov 8, 2023 at

Re: [blink-dev] Intent to Ship: Protected Audiences Negative Targeting

Hi all, We have a small delta to this feature we'd like to implement. In our current design, ad techs need to provide a flag, `adAuctionHeaders` on their `fetch()` request. ( https://github.com/WICG/turtledove/blob/main/FLEDGE.md#63-http-response-headers) However, we received feedback that

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

Thank you, all! On Wed, Nov 8, 2023 at 11:48 AM Chris Harrelson wrote: > LGTM3 > > On Wed, Nov 8, 2023 at 8:35 AM Mike Taylor wrote: > >> LGTM2 >> On 11/8/23 11:33 AM, Yoav Weiss wrote: >> >> LGTM1 >> >> On Wednesday, November 1, 2023 at 8:11:02 PM UTC+1 or...@google.com >> wrote: >> >>> Sorry

Re: [blink-dev] Intent to Ship: EditContext API

+1 to the evidence from OT being persuasive. LGTM2 On Wednesday, November 8, 2023 at 8:56:24 AM UTC-8 Rick Byers wrote: > It certainly sounds to me that there's additional work to be done here, > but I agree with Daniel that changing event order is not something we can > do lightly. Gregg,

Re: [blink-dev] How to Handle Hex values inside style text content.

Hi, This doesn't seem to work. Can I try anything else. and how does then blink process any external stylesheet which is having such Hex values and show them correctly in ParseStylesheet. and if I take rules from same point and add them to new style node, the text is getting converted to

Re: [blink-dev] Re: Intent to Ship: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

LGTM3 On Wed, Nov 8, 2023 at 9:01 AM Mike Taylor wrote: > LGTM2 > On 11/8/23 11:58 AM, Yoav Weiss wrote: > > LGTM1 > > On Monday, November 6, 2023 at 9:21:34 PM UTC+1 Vladimir Levin wrote: > >> Contact emails vmp...@chromium.org >> >> Explainer None >> >> Specification >>

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (further gating for trigger verbose debug reports)

LGTM3 On Wed, Nov 8, 2023 at 1:04 AM Yoav Weiss wrote: > LGTM2 > > On Tuesday, November 7, 2023 at 2:44:47 AM UTC+1 Mike Taylor wrote: > >> Thanks Akash. >> >> LGTM1 % sending out an email to the >> attribution-reporting-api-...@chromium.org group. >> On 11/6/23 4:52 PM, Akash Nadan wrote: >>

Re: [blink-dev] Re: Intent to Ship: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

LGTM2 On 11/8/23 11:58 AM, Yoav Weiss wrote: LGTM1 On Monday, November 6, 2023 at 9:21:34 PM UTC+1 Vladimir Levin wrote: Contact emails vmp...@chromium.org Explainer None Specification

[blink-dev] Re: Intent to Ship: checkVisibility: contentVisibilityAuto, opacityProperty, and visibilityProperty

LGTM1 On Monday, November 6, 2023 at 9:21:34 PM UTC+1 Vladimir Levin wrote: > Contact emailsvmp...@chromium.org > > ExplainerNone > > Specification > https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility > > Summary > > This feature adds three more values to the checkVisibility ( >

Re: [blink-dev] Intent to Ship: EditContext API

It certainly sounds to me that there's additional work to be done here, but I agree with Daniel that changing event order is not something we can do lightly. Gregg, could you please file an issue on the spec so the discussion can continue there? Given

Re: [blink-dev] Intent to Ship: No-Vary-Search Hint for Prefetch Speculation Rules

LGTM3 (but I don't think it makes sense to ship this without the other intent related to it?) On Wed, Nov 8, 2023 at 7:21 AM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2023-11-07 01:57, Mike Taylor wrote: > > LGTM1 > On 11/1/23 9:55 AM, Liviu Tinta wrote: > > Contact emails

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

LGTM3 On Wed, Nov 8, 2023 at 8:35 AM Mike Taylor wrote: > LGTM2 > On 11/8/23 11:33 AM, Yoav Weiss wrote: > > LGTM1 > > On Wednesday, November 1, 2023 at 8:11:02 PM UTC+1 or...@google.com wrote: > >> Sorry for the delay in response. All of the PRs have since landed. >> >> Regarding your question

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

LGTM2 On 11/8/23 11:33 AM, Yoav Weiss wrote: LGTM1 On Wednesday, November 1, 2023 at 8:11:02 PM UTC+1 or...@google.com wrote: Sorry for the delay in response. All of the PRs have since landed. Regarding your question on the interest group limit changes, these limits are intended

Re: [blink-dev] Intent to Ship: WebGPU timestamp queries

LGTM3 On Wed, Nov 8, 2023 at 7:38 AM Daniel Bratell wrote: > LGTM2 > > 100 microseconds sound very coarse for this, but I guess that just means > they have to average data over many frames. And if they are happy, I'm > happy. > > /Daniel > On 2023-11-08 09:41, Yoav Weiss wrote: > > LGTM1 > >

Re: [blink-dev] Intent to Ship: Protected Audience clearOriginJoinedAdInterestGroups() & interest group limit changes & kAnonStatus

LGTM1 On Wednesday, November 1, 2023 at 8:11:02 PM UTC+1 or...@google.com wrote: > Sorry for the delay in response. All of the PRs have since landed. > > Regarding your question on the interest group limit changes, these limits > are intended to be guardrails against exceptional behavior, and

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

LGTM3 On Wed, Nov 8, 2023 at 7:30 AM Mike Taylor wrote: > LGTM2 > On 11/8/23 5:16 AM, Yoav Weiss wrote: > > LGTM1 - seems like a simple and useful addition to the API surface. > > On Wednesday, November 1, 2023 at 3:07:22 PM UTC+1 > philipp...@googlemail.com wrote: > >> Am Mi., 25. Okt. 2023 um

Re: [blink-dev] Intent to Ship: CSS font-palette property animation

Hi, could you please request signals from the other vendors? https://bit.ly/blink-signals will tell you how they work. Also, you may want to file a TAG review, or give them a FYI or let us know why that is not necessary. /Daniel On 2023-11-08 13:56, 'Munira Tursunova' via blink-dev wrote:

Re: [blink-dev] Intent to Ship: No-Vary-Search support in navigation prefetch cache

Thanks for working on this, as I'm enthusiastically supportive of tackling this use case! One thing I wish y'all have done, and that I haven't seen any evidence of (but please correct me if I'm wrong) is discuss this design with the HTTPWG at the IETF. That is feedback that I believe you got at

Re: [blink-dev] Intent to Ship: WebGPU timestamp queries

LGTM2 100 microseconds sound very coarse for this, but I guess that just means they have to average data over many frames. And if they are happy, I'm happy. /Daniel On 2023-11-08 09:41, Yoav Weiss wrote: LGTM1 Thanks for working through this issue!! On Wed, Nov 8, 2023 at 2:34 AM Domenic

Re: [blink-dev] Intent to Ship: CSS Highlight Inheritance

LGTM3 On Wednesday, November 8, 2023 at 4:18:59 PM UTC+1 Daniel Bratell wrote: > LGTM2 > > You may want to ping the Mozilla standards position issue and let them > know that we are close to shipping. It looks like they forgotten it. > > /Daniel > On 2023-11-06 16:43, Mike Taylor wrote: > >

Re: [blink-dev] Intent to Implement and Ship: VideoEncoderConfig.contentHint

They seem to be in state "preparing" which is the stage before they are actually requested. The system is a bit new so maybe there is some confusing UI or bug, but they are not yet requested. jrobbins, do you know what might have gone awry? /Daniel On 2023-11-08 05:04, 'Eugene Zemtsov' via

Re: [blink-dev] Intent to Ship: CSS spelling and grammar features

LGTM3 On Wed, Nov 8, 2023 at 4:24 PM Daniel Bratell wrote: > LGTM2 > > This one could use a ping in the mozilla standards position issue like > that other one. > > /Daniel > On 2023-11-07 01:58, Mike Taylor wrote: > > Thanks - LGTM1 > On 11/6/23 7:27 PM, Stephen Chenney wrote: > > Thanks Mike.

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

LGTM2 On 11/8/23 5:16 AM, Yoav Weiss wrote: LGTM1 - seems like a simple and useful addition to the API surface. On Wednesday, November 1, 2023 at 3:07:22 PM UTC+1 philipp...@googlemail.com wrote: Am Mi., 25. Okt. 2023 um 18:40 Uhr schrieb Mike Taylor : On 10/20/23 2:27 PM,

Re: [blink-dev] Intent to Ship: CSS spelling and grammar features

LGTM2 This one could use a ping in the mozilla standards position issue like that other one. /Daniel On 2023-11-07 01:58, Mike Taylor wrote: Thanks - LGTM1 On 11/6/23 7:27 PM, Stephen Chenney wrote: Thanks Mike. On Mon, Nov 6, 2023 at 10:22 AM Mike Taylor wrote: Hi Stephen,

Re: [blink-dev] Intent to Ship: No-Vary-Search Hint for Prefetch Speculation Rules

LGTM2 /Daniel On 2023-11-07 01:57, Mike Taylor wrote: LGTM1 On 11/1/23 9:55 AM, Liviu Tinta wrote: Contact emails dome...@chromium.org, jbro...@chromium.org, liviuti...@chromium.org Explainer

Re: [blink-dev] Intent to Ship: No-Vary-Search support in navigation prefetch cache

LGTM2 /Daniel On 2023-11-07 01:57, Mike Taylor wrote: Thanks Liviu. I've spent some time today reviewing the explainer and spec, and find the use cases compelling. LGTM1 to ship. A non-blocking request would be to add the security & privacy considerations from the explainer into the

Re: [blink-dev] Intent to Ship: CSS Highlight Inheritance

LGTM2 You may want to ping the Mozilla standards position issue and let them know that we are close to shipping. It looks like they forgotten it. /Daniel On 2023-11-06 16:43, Mike Taylor wrote: Thanks for the detailed explanation of compat and for filing a TAG review. The risk of breakage

[blink-dev] Intent to Ship: CSS font-palette property animation

Contact emailsmoon...@google.com, dr...@google.com Explainer https://docs.google.com/document/d/1XMTrKH003KBOes6hxzI-3E7LTwp5YwFC-rnzoFpFrfw/edit?usp=sharing Specificationhttps://drafts.csswg.org/css-fonts-4/#font-palette-prop Summary The CSS font-palette property allows selection of a

[blink-dev] Re: [Call for feedback] Proposal to gradually skip unload events: already unreliable, top back/forward cache blocker, better alternatives available!

On Thu, 26 Oct 2023 at 01:11, Kevin D. wrote: > Understood. > > >1. *Is there any action required from us until general rollout (when >`unload` isn’t fired anymore)?* > > No. > >1. *Is there a list of this restricted set domains with which you’re >experimenting?* Want to know if

Re: [blink-dev] Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools

LGTM1 - seems like a simple and useful addition to the API surface. On Wednesday, November 1, 2023 at 3:07:22 PM UTC+1 philipp...@googlemail.com wrote: > Am Mi., 25. Okt. 2023 um 18:40 Uhr schrieb Mike Taylor < > miketa...@chromium.org>: > >> On 10/20/23 2:27 PM, 'Philipp Hancke' via blink-dev

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (further gating for trigger verbose debug reports)

LGTM2 On Tuesday, November 7, 2023 at 2:44:47 AM UTC+1 Mike Taylor wrote: > Thanks Akash. > > LGTM1 % sending out an email to the > attribution-reporting-api-...@chromium.org group. > On 11/6/23 4:52 PM, Akash Nadan wrote: > > Hi Mike, > > I've spot checked some popular publisher sites, and

Re: [blink-dev] Intent to Ship: WebGPU timestamp queries

LGTM1 Thanks for working through this issue!! On Wed, Nov 8, 2023 at 2:34 AM Domenic Denicola wrote: > > > On Tue, Nov 7, 2023 at 5:42 PM François Beaufort > wrote: > >> >> >> On Mon, Oct 30, 2023 at 7:39 PM Mike Taylor >> wrote: >> >>> On 10/30/23 12:59 PM, Corentin Wallez wrote: >>> >>> On