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

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 can see that the ar_debug cookie is being set on these sites. Additionally, we are

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

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, Could you please request reviews for all the other review gates in your chromestatus entry? Yes, done. Sorry I overlooked that. thanks,

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

LGTM1 On 11/1/23 9:55 AM, Liviu Tinta wrote: Contact emails dome...@chromium.org, jbro...@chromium.org, liviuti...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main/triggers.md#no-vary-search-hint Specification

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

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 draft WICG spec (or something similar). (Also, kudos to all

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

Thanks Mike. On Mon, Nov 6, 2023 at 10:22 AM Mike Taylor wrote: > Hi Stephen, > > Could you please request reviews for all the other review gates in your > chromestatus entry? > Yes, done. Sorry I overlooked that. > thanks, > Mike > > On 10/30/23 8:37 PM, Stephen Chenney wrote: > > The CSS

[blink-dev] Intent to Prototype: NavigationActivation

Contact emailsjap...@chromium.org, nrosent...@chromium.org Explainerhttps://github.com/whatwg/html/issues/9760 Specificationhttps://github.com/whatwg/html/pull/9856 Summary navigation.activation stores state about when the current Document was activated (e.g., when it was initialized, or

Re: [blink-dev] Intent to Deprecate: KeyboardEvent.keyIdentifier

This is the kind of issue that KeyboardMap ( https://wicg.github.io/keyboard-map/) is meant to address. `keyCode` is not well defined, so once you get outside the common keys you see implementation differences between browsers and OSs. So there is no real path to creating a specification for it.

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

> Are there any open issues that would result in breaking changes, after we ship? There are 2 open issues related to No-Vary-Search: https://github.com/WICG/nav-speculation/labels/no-vary-search. None of the open issues requires modifying No-Vary-Search header. We are not expecting breaking

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

Hi Mike, I've spot checked some popular publisher sites, and can see that the ar_debug cookie is being set on these sites. Additionally, we are planning on sending out an email to the attribution-reporting-api-...@chromium.org email group later this week, to notify them of the upcoming change.

Re: [blink-dev] Intent to Deprecate: KeyboardEvent.keyIdentifier

Hi All, Despite the fact that the given thread is from 2016 I think there's still a scenario which can be resolved only using deprecated properties ( KeyboardEvent.keyCode or UIEvent.which). Consider the following scenario: - there is a given shortcut in a web app mapped for Control+Alt+Z

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

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 ( https://drafts.csswg.org/cssom-view/#dom-element-checkvisibility) dictionary members: *

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

On 11/1/23 9:59 AM, Liviu Tinta wrote: Contact emails dome...@chromium.org, jbro...@chromium.org, liviuti...@chromium.org Explainer https://github.com/WICG/nav-speculation/blob/main/no-vary-search.md Specification

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

On 11/3/23 6:12 PM, 'Akash Nadan' via blink-dev wrote: Contact emails lin...@chromium.org , johni...@chromium.org Explainer Attribution Reporting with event-level reports

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

Thanks for the detailed explanation of compat and for filing a TAG review. The risk of breakage seems low (and I suppose we'll learn how true that is as the change rides the trains), and breakage in this case would just be cosmetic (unless someone is doing something really clever). LGTM1 to

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

Hi Stephen, Could you please request reviews for all the other review gates in your chromestatus entry? thanks, Mike On 10/30/23 8:37 PM, Stephen Chenney wrote: The CSS Spelling and Grammar feature has been active behind experimental web platform features since M89! There

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

Hi Eugene, Could you please request reviews for all the other review gates in your chromestatus entry? thanks, Mike On 11/1/23 6:32 PM, 'Eugene Zemtsov' via blink-dev wrote: Contact emails ezemt...@google.com Specification