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

LGTM2 On Fri, May 24, 2024 at 5:53 PM Anton Maliev wrote: > I see the concern. The 3P can use document.hasStorageAccess() > > to > check for cookie support, which accounts for the grace period and opt-out. > (It would

Re: [blink-dev] Intent to Ship: Dispatch selectionchange event per element

Given Olli's comments on this change being backwards-incompatible, do we have any data on how many sites would be impacted? Any usecounters to that effect? On Mon, May 27, 2024 at 2:19 AM Shuangshuang Zhou < shuangshuang.z...@intel.com> wrote: > Thanks Olli for the implement in Gecko side, and

[blink-dev] Re: Intent to Ship: Importmap integrity

On Fri, May 24, 2024 at 7:12 PM Panos Astithas wrote: > > > On Wed, May 22, 2024 at 2:16 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Wed, May 22, 2024 at 10:29 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org>

Re: [blink-dev] Re: Intent to Ship: Importmap integrity

case. > On Wed, May 22, 2024, 6:39 PM Mike Taylor wrote: > >> I'm inclined to LGTM this now - but don't see a lot of harm waiting for 1 >> additional week (per Mozilla's request in the not-public minutes). Happy to >> do so before, so long as the HTML PR lands. >> O

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

On Thu, May 16, 2024 at 4:15 PM Anton Maliev wrote: > > 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

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

OK, thanks for outlining the spec mechanics :) Regardless of whether the PR actually lands in the spec, for the purpose of risk-assessment, it's even more interesting to know if the PR is *ready* to land in the spec. Can y'all clarify its review status? If it's ready to land, can a spec editor

Re: [blink-dev] Intent to Extend Deprecation Trial: Partitioning Storage, Service Workers, and Communication APIs

LGTM to extend the deprecation trial M127-M132 inclusive On Wed, May 22, 2024 at 4:44 PM Mike Taylor wrote: > On 5/22/24 8:11 AM, Yoav Weiss (@Shopify) wrote: > > > > On Tue, May 21, 2024 at 8:55 PM Mike Taylor > wrote: > >> *Contact emails* >> >> >

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

LGTM2 On Tuesday, May 21, 2024 at 2:11:37 PM UTC+2 Mike Taylor wrote: > Thanks Liam! > > LGTM1 to ship. > On 5/20/24 3:51 PM, Liam Brady wrote: > > Thanks for your feedback on this intent! We plan on modifying the > "Allow-Cross-Origin-Event-Reporting" response header to accept a boolean >

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

hout your prompting. > > I've reached out to some engineers at Paypal and hopefully they'll get > back to me sometime next week. > > On Fri, May 3, 2024 at 8:50 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Thanks for diving into this!! >&g

Re: [blink-dev] Intent to Extend Deprecation Trial: Partitioning Storage, Service Workers, and Communication APIs

On Tue, May 21, 2024 at 8:55 PM Mike Taylor wrote: > *Contact emails* > > > > > > > > * miketa...@chromium.org Explainer > https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md > >

[blink-dev] Re: Intent to Ship: Importmap integrity

On Wed, May 22, 2024 at 10:29 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Tuesday, May 21, 2024 at 1:04:44 PM UTC+2 Yoav Weiss wrote: > > Contact emailsyoavwe...@chromium.org > > Explainerhttps://github.com/guybedford/import-maps-extensions#integ

[blink-dev] Re: Intent to Ship: Importmap integrity

On Tuesday, May 21, 2024 at 1:04:44 PM UTC+2 Yoav Weiss wrote: Contact emailsyoavwe...@chromium.org Explainerhttps://github.com/guybedford/import-maps-extensions#integrity Specificationhttps://github.com/whatwg/html/pull/10269 The PR is ready to land, but we're holding off on that for 2

[blink-dev] Intent to Ship: Importmap integrity

Contact emailsyoavwe...@chromium.org Explainerhttps://github.com/guybedford/import-maps-extensions#integrity Specificationhttps://github.com/whatwg/html/pull/10269 The PR is ready to land, but we're holding off on that for 2 weeks at Mozilla's request. See below. Summary Imported ES modules

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

d good to go? > > 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 Vellani' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> From my understandin

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 > >

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

Re: [blink-dev] New API owner: Vladimir Levin!

Congrats!! :) On Wed, May 15, 2024 at 9:46 PM Ken Russell wrote: > Congratulations Vlad! > > > On Wed, May 15, 2024 at 10:43 AM Mike Taylor > wrote: > >> Congrats Vlad! >> On 5/15/24 12:22 PM, danakj wrote: >> >> Congrats, Vlad :) >> >> On Wed, May 15, 2024 at 12:19 PM Chris Harrelson >>

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

On Wed, May 15, 2024 at 9:03 PM Mason Freed wrote: > Contact emailsmas...@chromium.org > > ExplainerNone > > Specificationhttps://w3c.github.io/uievents/#legacy-event-types > > Summary > > Mutation Events, including `DOMSubtreeModified`, `DOMNodeInserted`, > `DOMNodeRemoved`,

Re: [blink-dev] Intent to Implement and Ship: Conversion to RGB in VideoFrame.copyTo()

LGTM3 On Wed, May 15, 2024 at 6:02 PM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2024-05-15 07:13, Domenic Denicola wrote: > > LGTM1. > > I have a small non-blocking request: update your Chrome Status entry to > avoid using ClassName.staticMethod() syntax for what appears to be an >

Re: [blink-dev] Request for Deprecation Trial: Media Previews opt-out

Can you expand on how (if) this is different from the past intent with a similar title? On Monday, May 13, 2024 at 7:21:48 PM UTC+2 Mike Taylor wrote: > FWIW, a deprecation trial

[blink-dev] Re: Intent to Ship: Stop modifying author-defined selection colors

LGTM1 On Thursday, May 9, 2024 at 1:41:40 AM UTC+2 Stephen Chenney wrote: > Contact emailsschen...@chromium.org > > ExplainerNone > > Specificationhttps://www.w3.org/TR/css-pseudo-4/#highlight-selectors > > SummaryChromium currently checks all selection highlight colors against > the text color

Re: [blink-dev] Re: Intent to Experiment: Element Capture

LGTM3 On Tue, May 14, 2024 at 8:40 PM Chris Harrelson wrote: > LGTM2 > > On Tue, May 14, 2024 at 11:36 AM Mike Taylor > wrote: > >> OK - thanks for the clarification. I would ask that you get in touch with >> every registered origin - expiring the experiment early may be surprising. >> >>

[blink-dev] Re: Intent to Ship: Protected Audience: reporting timeouts & multiple-bids

On Monday, May 6, 2024 at 10:03:16 PM UTC+2 Paul Jensen wrote: Contact emails pauljen...@chromium.org Explainer Protected Audience reporting timeouts: https://github.com/WICG/ turtledove/pull/1101 Protected Audience multiple-bids: https://github.com/WICG/ turtledove/pull/1048

[blink-dev] Re: Intent to Ship: Document picture-in-picture: propagate user activation

LGTM1 On Tuesday, May 7, 2024 at 11:33:01 PM UTC+2 Tommy Steimel wrote: > Contact emailsstei...@chromium.org, liber...@chromium.org > > ExplainerNone > > Specificationhttps://github.com/WICG/document-picture-in-picture/pull/117 > > Design docs > >

Re: [blink-dev] Intent to Ship: Tabbed web apps

24 at 10:30:58 AM UTC-4 Brett Wilson wrote: >> >>> On Mon, May 6, 2024 at 3:02 AM Yoav Weiss (@Shopify) < >>> yoav...@chromium.org> wrote: >>> >>>> >>>> >>>> On Fri, May 3, 2024 at 7:28 PM Brett Wilson >>>>

Re: [blink-dev] Intent to Ship: Tabbed web apps

On Fri, May 3, 2024 at 7:28 PM Brett Wilson wrote: > Contact emailsbre...@chromium.org, alancut...@chromium.org, > mgi...@chromium.org, loubr...@google.com > > Explainer > https://github.com/WICG/manifest-incubations/blob/gh-pages/tabbed-mode-explainer.md > >

Re: [blink-dev] Intent to Extend Experiment: WebRTC encoded transform - Modify Metadata functions (setMetadata method)

e to have a shorter extension. This is, > of course, assuming the I2S for the final version of the API is approved. > That's fine! :) > > On Fri, May 3, 2024 at 2:39 PM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Do I understand correctly th

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

gt; It would also be helpful to discuss what breakage looks like in this >>> case. Would it be a one-time loss of state (i.e., have to log in again), or >>> something different? >>> On 3/19/24 5:08 AM, Yoav Weiss (@Shopify) wrote: >>> >>> OK, so j

Re: [blink-dev] Intent to Extend Experiment: WebRTC encoded transform - Modify Metadata functions (setMetadata method)

Do I understand correctly that you want to extend the OT for 3 more milestones, up to 129 (inclusive)? On Thu, May 2, 2024 at 2:45 PM Guido Urdaneta wrote: > Contact emails...@chromium.org, gui...@chromium.org, agpa...@chromium.org > > Explainer >

Re: [blink-dev] Intent to Prototype and Ship: Align navigator.cookieEnabled with spec

LGTM2 On Tue, Apr 30, 2024 at 6:10 PM Rick Byers wrote: > Ah good point, thanks. Thanks for your attention to web compat detail > here. Really any bug fix has the potential to be a significant breaking > change so the line is very context-dependent. > > Rick > > On Tue, Apr 30, 2024 at 11:36 AM

Re: [blink-dev] Intent to Ship: Support Cross-Origin Shared Storage Worklets

LGTM3 On Thu, Apr 25, 2024 at 5:57 PM Mike Taylor wrote: > LGTM2. > On 4/24/24 5:45 PM, Yao Xiao wrote: > > Hi Yao, > > I see that https://github.com/WICG/shared-storage/pull/152 is still open, >> can that be landed before we ship this? > > The PR landed just now. > > Also, can you point to the

Re: [blink-dev] Intent to Ship: FedCM: Credentialed requests will no longer send SameSite=Strict cookies

anning to ship aligns with my understanding of what we'd want to eventually specify here. > > with regards to the implementation: We do not send SameSite=Lax cookies > That makes sense. Thanks! > > Christian > > On Wed, Apr 24, 2024 at 11:04 AM Yoav Weiss (@Shopify) <

Re: [blink-dev] Intent to Ship: FedCM: Credentialed requests will no longer send SameSite=Strict cookies

fetch-accounts says that the origin for accounts requests is an opaque origin. What does that mean for `Same-Site: Lax` cookies? Will they be sent or not? On Tuesday, April 23, 2024 at 9:08:33 PM UTC+2 Johann Hofmann wrote: > I wanted to chime

Re: [blink-dev] Re: Intent to Ship: WebGLObject Web IDL superinterface

LGTM3 On Tue, Apr 23, 2024 at 6:45 PM Mike Taylor wrote: > LGTM2 > On 4/23/24 1:18 AM, Domenic Denicola wrote: > > LGTM1 > > On Tue, Apr 23, 2024 at 7:36 AM Ken Russell wrote: > >> Yes. N/As and explanations have been requested for all of these now. >> >> >> On Sun, Apr 21, 2024 at 7:37 PM

Re: [blink-dev] Intent to Ship: URL.parse()

LGTM1 Thanks for catching us up here! :) On Tue, Apr 23, 2024 at 10:20 AM Domenic Denicola wrote: > Thanks. One more thing: our process requires all features have a Finch > feature name (i.e., a base::Feature) so that we can turn off the feature > remotely. Can you ensure your implementation

Re: [blink-dev] Re: Intent to Ship: Remove Authorization header upon cross-origin redirect

On Mon, Apr 15, 2024 at 2:18 PM Tom Komarnicki wrote: > Hey, > > Sorry for necro'ing this thread, I'm aware that this has been on the > "done" pile for a while - and maybe it should've been brought up earlier, > but how do you "disable" this feature ? It's making the BE dev exhaustingly >

Re: [blink-dev] Intent to Extend Reverse Origin Trial: Trial for SharedArrayBuffers in non-isolated pages on Desktop platforms

LGTM to extend the deprecation trial till M131 (inclusive) On Thu, Apr 11, 2024 at 11:21 AM Camille Lamy wrote: > Contact emails > > v...@chromium.org cl...@chromium.org > > Explainer > > > https://docs.google.com/document/d/1zDlfvfTJ_9e8Jdc8ehuV4zMEu9ySMCiTGMS9y0GU92k > > Specification > >

Re: [blink-dev] Intent to Ship: Gamepad API Trigger-Rumble Extension

On Thu, Apr 11, 2024 at 1:02 AM 'Gabriel Brito' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > gabrielbr...@microsoft.com > > Explainer > > https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/GamepadHapticsActuatorTriggerRumble/explainer.md > > Specification >

Re: [blink-dev] Intent to Prototype: Importmap integrity

I somehow missed the fact that `require-sri-for` was removed. That doesn't change the value of this feature from my perspective. On Mon, Apr 15, 2024 at 9:39 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Mon, Apr 15, 2024 at 8:17 PM Jeffrey Yasskin > wrot

Re: [blink-dev] Intent to Prototype: Importmap integrity

ncentrating integrity information in the import map? > Indeed. > > Jeffrey > > On Mon, Apr 15, 2024 at 7:46 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Contact emailsyoavwe...@chromium.org >> >> Explainerhttps://github.com/guybedford/impo

[blink-dev] Intent to Prototype: Importmap integrity

Contact emailsyoavwe...@chromium.org Explainerhttps://github.com/guybedford/import-maps-extensions#integrity Specificationhttps://github.com/whatwg/html/pull/10269 Summary Imported ES modules can't currently have their integrity checked, and hence cannot run in environments that require

Re: [blink-dev] Intent to Experiment: FedCM Button Mode API and Use Other Account API

; Please let us know if we could make it more clear for developers. > > Yi > > On Fri, Apr 5, 2024 at 9:36 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Tuesday, February 27, 2024 at 1:43:01 AM UTC+1 Mike Taylor wrote: >> &

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

servers were in general badly equipped to handle. >> Could reordering happen here? >> >> Either way, I worry that this could become a source of random problems >> that would be hard to understand or debug. Is there any third or fourth >> option to consider? >> >

Re: [blink-dev] Intent to Ship: CSS Stepped Value Functions

Can you please flip on the "debuggability" review bit in chromestatus? (feel free to mark it as "N/A" if you think that's the case) On Mon, Apr 8, 2024 at 4:40 PM Yoav Weiss (@Shopify) wrote: > LGTM1 > > Thanks for catching us up here! > > On Fri, Apr 5, 2024

Re: [blink-dev] Intent to Ship: CSS Stepped Value Functions

LGTM1 Thanks for catching us up here! On Fri, Apr 5, 2024 at 3:53 PM Daniil Sakhapov wrote: > Contact emailssakha...@chromium.org > > ExplainerNone > > Specificationhttps://drafts.csswg.org/css-values/#round-func > > Summary > > The stepped-value functions, round(), mod(), and rem(), all

Re: [blink-dev] Intent to Prototype: Document-Isolation-Policy

This is very interesting! Do I understand correctly and the main reason this would be easier to deploy is because embedded iframes and popups won't need to deploy COEP in this model? On Fri, Apr 5, 2024 at 12:14 PM Camille Lamy wrote: > Yes the user agent keying is deterministic, and we're

Re: [blink-dev] Web-Facing Change PSA: Support "color-interpolation: linearrgb" on SVG gradients

+1 to sending an intent here. Thanks!! :) On Sun, Apr 7, 2024 at 1:12 AM Mike Taylor wrote: > > On 4/4/24 4:29 AM, Fredrik Söderquist wrote: > > On Thu, Apr 4, 2024 at 1:22 AM Mike Taylor wrote: > >> Hi Fredrik, >> >> Just to confim - this is adding support for a new `color-interpolation` >>

Re: [blink-dev] Intent to Experiment: FedCM Button Mode API and Use Other Account API

On Tuesday, February 27, 2024 at 1:43:01 AM UTC+1 Mike Taylor wrote: That said, please request approvals from the various review gates in your chromestatus entry before experimenting. On 2/26/24 7:41 PM, Mike Taylor wrote: LGTM to experiment from M124 to M127 inclusive. On 2/26/24 5:45 PM, Yi

Re: [blink-dev] Intent to Extend Deprecation Trial: Removal of X-Requested-With in WebView

g with the remaining OT participants to determine what, if > any, further solutions are needed for their use cases of the header. > > Sincerely, > [image: Google Logo] > Peter Birk Pakkenberg > Software Engineer > pb...@chromium.org > > > On Wed, 3 Apr 2024 at 11:06, Yoav Weiss

Re: [blink-dev] Intent for Reverse Origin Trial: Media Previews opt-out

b APIs (navigator.mediaDevices.getUserMedia / > navigator.mediaDevices.enumerateDevices). > > > On Wed, Apr 3, 2024 at 3:02 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Do I understand correctly that this intent only concerns the permission >> U

Re: [blink-dev] Intent to Ship: RegExp modifiers

LGTM3 On Thu, Mar 28, 2024 at 3:38 AM Domenic Denicola wrote: > LGTM2 > > On Thu, Mar 28, 2024 at 3:11 AM Mike Taylor > wrote: > >> LGTM1 - looks like a useful addition already supported in a number of >> other RegExp engines. >> On 3/27/24 11:38 AM, 'Shu-yu Guo' via blink-dev wrote: >> >>

Re: [blink-dev] Re: Intent to Ship: visualViewport.onscrollend Support

LGTM3 as a test was added! On Wednesday, March 27, 2024 at 4:21:49 PM UTC+1 Mike Taylor wrote: > LGTM2 > On 3/26/24 10:50 PM, Domenic Denicola wrote: > > LGTM1, this is a very small change that IMO does not require any signals > or TAG review. It's just bringing this event in line with all

Re: [blink-dev] Intent to Extend Deprecation Trial: Removal of X-Requested-With in WebView

: Google Logo]Peter Birk PakkenbergSoftware engineerpb...@chromium.org On Thu, 28 Mar 2024 at 08:40, Yoav Weiss (@Shopify) wrote: Of the 100+ origins that signed up for the trial, do you know if any made progress towards reducing their dependence on this header? Any that no longer need the trial

Re: [blink-dev] Intent for Reverse Origin Trial: Media Previews opt-out

ing >> with him on a GitHub issue about it. >> >> On Wed, Mar 27, 2024 at 8:28 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> As a heads up, this wasn't caught in the API owner tooling, probably due >>> to the unconvention

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

i, Mar 29, 2024 at 4:33 AM Noam Rosenthal > wrote: > >> >> >> On Fri, Mar 29, 2024 at 6:33 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> On top of Domenic's questions, have we tried to estimate the risk here? >>> Even i

Re: [blink-dev] Intent to deprecate and remove: Stop sending blur events on element removal

On top of Domenic's questions, have we tried to estimate the risk here? Even if it's Chromium-only, there could be Enterprise or embedded scenarios that somehow rely on it. Do we know how often this blur event actually fires? On Fri, Mar 29, 2024 at 5:28 AM Domenic Denicola wrote: > > > On Fri,

Re: [blink-dev] Intent to Extend Deprecation Trial: Removal of X-Requested-With in WebView

Of the 100+ origins that signed up for the trial, do you know if any made progress towards reducing their dependence on this header? Any that no longer need the trial? On Wed, Mar 27, 2024 at 5:03 PM Daniel Bratell wrote: > This being beyond the normal scope of an extension will require three >

[blink-dev] Re: Intent to Implement and Ship: OpusEncoderConfig `signal` and `application` parameters

Thanks! On Wed, Mar 27, 2024 at 10:41 PM Thomas Guilbert wrote: > I've flipped all the reviews and will update this thread when they are all > completed. > > Thanks! > > On Wed, Mar 27, 2024 at 8:25 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wr

Re: [blink-dev] Intent for Reverse Origin Trial: Media Previews opt-out

As a heads up, this wasn't caught in the API owner tooling, probably due to the unconventional title. +Jason Robbins - FYI On Tue, Mar 26, 2024 at 9:33 PM mark a. foltz wrote: > Contact emailsmfo...@chromium.org, bryantchand...@chromium.org > > ExplainerNone > > Specification >

[blink-dev] Re: Intent to Implement and Ship: OpusEncoderConfig `signal` and `application` parameters

Hey! Can you flip on the various reviews (privacy, enterprise, etc) in the chromestatus entry? On Tuesday, March 26, 2024 at 11:29:53 PM UTC+1 Thomas Guilbert wrote: > Contact emailstguilb...@chromium.org > > ExplainerNone > > Specification >

Re: [blink-dev] Re: Intent to Ship: Allow top layer elements to be nested within popovers

LGTM3 On Wednesday, March 27, 2024 at 3:29:57 PM UTC+1 Mike Taylor wrote: > LGTM2 > On 3/26/24 10:53 PM, Domenic Denicola wrote: > > LGTM1. I think there is a small compat risk here but it should be > manageable via the combination of: low popover + dialog usage so far, > presumably by

[blink-dev] Re: Intent to Ship: visualViewport.onscrollend Support

On Wednesday, March 27, 2024 at 3:50:08 AM UTC+1 Domenic Denicola wrote: LGTM1, this is a very small change that IMO does not require any signals or TAG review. It's just bringing this event in line with all other events on the platform. (It would be cool if there were some automated way of

[blink-dev] Re: Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

, it may not cause any issues or change in comparison. Let me know if you have any other questions. Thanks for the explanation. I'd consider this a (barely) web-exposed bug fix. Thanks, Akash On Tuesday, March 26, 2024 at 10:54:02 AM UTC-7 Yoav Weiss (@Shopify) wrote: On Tuesday, March 19, 2024

Re: [blink-dev] Intent to Ship: CSS view-transition-class and class VT argument syntax

LGTM3 On Friday, March 22, 2024 at 8:01:46 PM UTC+1 Chris Harrelson wrote: > LGTM2 > > On Fri, Mar 22, 2024 at 11:46 AM Mike Taylor > wrote: > >> LGTM1 >> On 3/20/24 2:27 PM, Vladimir Levin wrote: >> >> Contact emails vmp...@chromium.org, nrosent...@chromium.org >> >> Explainer >>

[blink-dev] Re: Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

On Tuesday, March 19, 2024 at 12:18:00 AM UTC+1 Akash Nadan wrote: Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution

Re: [blink-dev] Intent to Ship: SVG context-fill and context-stroke

LGTM3 assuming that the gradients bug mentioned upthread is resolved in https://issues.chromium.org/issues/40362923#comment36 On Friday, March 22, 2024 at 8:00:56 PM UTC+1 Chris Harrelson wrote: > LGTM2 > > On Fri, Mar 22, 2024 at 11:47 AM Mike Taylor > wrote: > >> LGTM1 >> On 3/18/24 10:53

Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

rn day browsers, and neither blink or webkit are spec > compliant (in distinct ways). > > > On Fri, Mar 22, 2024 at 2:57 PM Mike Taylor > wrote: > >> On 3/22/24 1:37 AM, Yoav Weiss (@Shopify) wrote: >> >> >> On Thu, Mar 21, 2024 at 10:11 AM Zheda Chen wro

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

LGTM1 once the fix to the above issue lands. On Monday, March 18, 2024 at 7:56:52 PM UTC+1 yshal...@microsoft.com wrote: > Yes, I believe the bug [1] is a blocker. > > [1] https://issues.chromium.org/issues/328102503. > > On

Re: [blink-dev] Intent to Ship: Add JavaScript timer wake up alignment for unimportant cross-origin frames

On Thu, Mar 21, 2024 at 10:11 AM Zheda Chen wrote: > The privacy/security/enterprise/debuggability gates are requested on > Chrome Status. Testing gate to be requested later. > > "Unimportant" cross origin frames means they are cross-origin, visible but > use non-large proportion (<75%) of

Re: [blink-dev] Re: Intent to Ship: 'writingsuggestions' attribute

On Thu, Mar 21, 2024 at 8:07 AM Marcos Caceres wrote: > > > On Wednesday, March 20, 2024 at 4:57:56 AM UTC+11 Sanket Joshi (Edge) > wrote: > > Hi Marcos, > > The spec for the writing suggestions attribute > doesn't specify how > UAs should

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

twork blocks *any* deployment of post-quantum >>> algorithms, so ultimately the middleboxes will just need to get fixed. The >>> various ecosystem pressures towards getting to post-quantum are >>> particularly strong in enterprise anyway, so hopefully admins will be more >>

Re: [blink-dev] Intent to Ship: Protected Audience: Split up large trusted signals fetches & deprectedReplaceInURN via auction config

On Thu, Mar 14, 2024 at 8:48 PM Paul Jensen wrote: > Contact emails > > pauljen...@chromium.org > > > Explainer > > Split up large trusted signals fetches: > https://github.com/WICG/turtledove/pull/1070 > > deprectedReplaceInURN via auction config: > https://github.com/WICG/turtledove/pull/1069

[blink-dev] Re: Intent to Ship: Extending Storage Access API (SAA) to non-cookie storage

gun here, but given the > direction these APIs seem to be heading I don't think the risk is high. > What are the chances vendors decide to add new storage mechanisms that are > loaded at document initialization with all data synchronously available? > > ~ Ari Chivukula (The

[blink-dev] Re: Intent to Ship: Extending Storage Access API (SAA) to non-cookie storage

isms that users would not want to expose along with current ones? > > ~ Ari Chivukula (Their/There/They're) > > > On Wed, Mar 20, 2024 at 7:29 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Thursday, March 14, 2024 at 2:27:20 PM UTC+1 Ar

[blink-dev] Re: Intent to Ship: Extending Storage Access API (SAA) to non-cookie storage

On Thursday, March 14, 2024 at 2:27:20 PM UTC+1 Ari Chivukula wrote: Contact emails aric...@chromium.org, wanderv...@chromium.org, johann...@chromium.org, rosh...@google.com Specification https://privacycg.github.io/saa-non-cookie-storage/ Design Doc

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

o post-quantum are particularly strong > in enterprise anyway, so hopefully admins will be more likely to understand > why it's important for them to fix those. > https://chromeenterprise.google/policies/#PostQuantumKeyAgreementEnabled > Makes sense, thanks!! I'll LGTM once the review ga

Re: [blink-dev] Intent to Ship: X25519Kyber768 key encapsulation for TLS on Desktop

On Mon, Mar 18, 2024 at 3:37 PM 'David Adrian' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsdadr...@google.com > > Explainer > https://www.ietf.org/archive/id/draft-tls-westerbaan-xyber768d00-02.html > > Specification >

Re: [blink-dev] Intent to Extend Experiment: Capture all screens

On Mon, Mar 18, 2024 at 5:28 PM 'Simon Hangl' via blink-dev < blink-dev@chromium.org> wrote: > Hello blink-dev, > > We’d like to ask for an extension to our Origin Trial, from M124 to M130. > This is due to the dependency on isolated web apps. > > Contact emails > > sim...@google.com

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

lya wrote: > The flag is a base::features flag named > kAncestorChainBitEnabledInPartitionedCookies. > > Updated the review gates on chromestatus.com > > On Wed, Mar 13, 2024 at 11:25 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> A

Re: [blink-dev] Re: Intent to Ship: 'writingsuggestions' attribute

Thanks for the heads up, Marcos! :) On Tue, Mar 19, 2024 at 3:51 AM Marcos Caceres wrote: > Hi Blink-Dev Friends! > > We (WebKit) hit some web compat issues with this feature while testing our > implementation is Safari Tech Preview. > > Could you please take a look at: >

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

Great to see a positive position from Mozilla on this. Is the above mentioned bug a blocker here? On Friday, March 8, 2024 at 12:52:58 AM UTC+1 yshal...@microsoft.com wrote: > Thanks for taking a look and your feedback! Please let me know if you have > any other questions or concerns. > On

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

LGTM2 actually.. On Mon, Mar 18, 2024 at 7:40 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 to ship the ID assertion endpoint CORS requirements. > > On Wed, Mar 13, 2024 at 3:11 PM Nicolás Peña wrote: > >> >> On Wednesday, March 13, 2024 at 7:3

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

wrote: > > No, Sec-Fetch-Dest > <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest> > is not changing. Sec-Fetch-Mode > <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Mode> > is. > > On Wednesday, March 6, 2024 at 11:31:3

Re: [blink-dev] Re: Intent to Ship: Compute Pressure

LGTM2 given the strong developer feedback and plans for use in user-facing features. On Fri, Mar 15, 2024 at 6:57 PM Philip Jägenstedt wrote: > On Fri, Mar 15, 2024 at 6:42 PM Raphael Kubo da Costa < > raphael.kubo.da.co...@intel.com> wrote: > >> Philip Jägenstedt writes: >> >> > Taking a

Re: [blink-dev] Intent to Ship: Protected Audience: Downsampled forDebugOnly & Increase number of component ads

LGTM1 On Monday, March 11, 2024 at 4:21:36 PM UTC-4 Paul Jensen wrote: On Wed, Mar 6, 2024 at 12:07 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: On Mon, Mar 4, 2024 at 7:00 PM Paul Jensen wrote: On Wed, Feb 28, 2024 at 12:24 PM Yoav Weiss (@Shopify) < yoavwe...@chr

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

Also, can you flip on the relevant review gates in chromestatus.com? On Wed, Mar 13, 2024 at 11:24 AM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > > > On Tue, Mar 12, 2024 at 4:46 PM 'Aaron Selya' via blink-dev < > blink-dev@chromium.org> wrote: > >>

Re: [blink-dev] Intent to Ship: Adding Cross-site Ancestor Chain Bit to CHIPS Partition Key

On Tue, Mar 12, 2024 at 4:46 PM 'Aaron Selya' via blink-dev < blink-dev@chromium.org> wrote: > The first mitigation listed here is to migrate existing >> partitioned cookies to include the new bit, and the second mitigation is to >> have a flag that can disable this feature. Would disabling the

Re: [blink-dev] Re: Intent to Ship: Standard-compliant pseudo-element argument for getComputedStyle & KeyframeEffect

LGTM2 On Wed, Mar 13, 2024 at 10:59 AM Noam Rosenthal wrote: > > > On Wed, Mar 13, 2024 at 12:36 PM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Monday, March 11, 2024 at 6:36:07 AM UTC-4 Noam Rosenthal wrote: >> >>

Re: [blink-dev] Re: Intent to Ship: Standard-compliant pseudo-element argument for getComputedStyle & KeyframeEffect

On Monday, March 11, 2024 at 6:36:07 AM UTC-4 Noam Rosenthal wrote: I've run a rough HTTP archive query on it, testing all HTTP responses last month (666 million): getComputedStyle with an argument that doesn't begin with "::" is called in 0.45% of pages, out of which 55% is ":before", 28%

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

on wrote: On Wed, Mar 6, 2024 at 8:28 AM Nicolás Peña wrote: On Wednesday, March 6, 2024 at 5:11:09 AM UTC-5 Yoav Weiss wrote: On Wed, Mar 6, 2024 at 10:21 AM Yoav Weiss (@Shopify) wrote: On Mon, Mar 4, 2024 at 9:36 PM Mike Taylor wrote: LGTM1 On 3/4/24 1:33 PM, Nicolás Peña wrote: Cont

Re: [blink-dev] Intent to Ship: Interoperable mousemove default action

canceling mousedown in >>> iframe >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/RYzJrvPzHss/m/QsopwzYQAAAJ> >>> . >>> >>> >>> On Wed, Mar 6, 2024 at 5:25 AM Yoav Weiss (@Shopify) < >>> yoavwe...@chromium.org>

Re: [blink-dev] Intent to Ship: WebGPU: ServiceWorker and SharedWorker support

LGTM1 On Tue, Mar 12, 2024, 15:10 'François Beaufort' via blink-dev < blink-dev@chromium.org> wrote: > > > On Tue, Mar 12, 2024 at 6:58 PM Mike Taylor > wrote: > >> On 3/11/24 4:06 PM, 'François Beaufort' via blink-dev wrote: >> >> Contact emails fbeauf...@google.com >> >> Explainer None >> >>

Re: [blink-dev] Intent to Ship: RegExp duplicate named capture groups

LGTM2 On Mon, Mar 11, 2024 at 5:00 PM Shu-yu Guo wrote: > On Mon, Mar 11, 2024 at 8:26 AM Mike Taylor > wrote: > >> On 3/11/24 6:49 AM, Yoav Weiss (@Shopify) wrote: >> >> >> >> On Fri, Mar 8, 2024 at 4:26 PM Mike Taylor >> wrote: >>

Re: [blink-dev] Intent to Ship: RegExp duplicate named capture groups

On Fri, Mar 8, 2024 at 4:26 PM Mike Taylor wrote: > LGTM1 > On 3/7/24 6:22 PM, Shu-yu Guo wrote: > > Contact emails pth...@chromium.org, s...@chromium.org > > Explainer None > > Specification https://github.com/tc39/ecma262/pull/2721 > > What are the implications of this on regexes that already

Re: [blink-dev] Intent to Ship: FedCM CORS requirement on ID assertion endpoint

>> >>> >>> >>> On Wednesday, March 6, 2024 at 5:11:09 AM UTC-5 Yoav Weiss wrote: >>> >>> On Wed, Mar 6, 2024 at 10:21 AM Yoav Weiss (@Shopify) < >>> yoavwe...@chromium.org> wrote: >>> >>> >>> >>

Re: [blink-dev] Intent to Ship: Private Aggregation debug mode for auctionReportBuyers reporting

on a page, > there is also a potential barrier in the need to edit the top-level page. > > Best, > Alex > > On Thu, Mar 7, 2024 at 4:26 AM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> Alex T - can you expand on the other debug modes that are a

Re: [blink-dev] Intent to Extend Experiment: Extending Storage Access API (SAA) to non-cookie storage

LGTM to extend to M125 (inclusive) On Friday, March 8, 2024 at 11:06:16 PM UTC+1 Mike Taylor wrote: > I'm recused on this one, but even with the extension to 125, you're still > not going beyond the default 6 milestones for an OT (the original request > was for 120 to 124) - so the approval

Re: [blink-dev] Intent to Ship: Private Aggregation debug mode for auctionReportBuyers reporting

, we can use OTs and set a date-certain for removal >>> and prevent over-use that would back us into a corner. >>> >>> Without some sort of guardrail, I'm not optimistic that we'll be able to >>> actually get rid of a useful debugging aid that is web-exposed. >&g

Re: [blink-dev] Re: Intent to Ship: Document Render-Blocking

LGTM2 On Wed, Mar 6, 2024 at 7:23 PM Mike Taylor wrote: > LGTM1 > On 3/6/24 11:00 AM, Vladimir Levin wrote: > > Re failing tests: > The flag is currently in "test" status >

Re: [blink-dev] Intent to Ship: Protected Audience: Downsampled forDebugOnly & Increase number of component ads

On Mon, Mar 4, 2024 at 7:00 PM Paul Jensen wrote: > > > On Wed, Feb 28, 2024 at 12:24 PM Yoav Weiss (@Shopify) < > yoavwe...@chromium.org> wrote: > >> >> >> On Thu, Feb 22, 2024 at 6:07 PM 'Orr Bernstein' via blink-dev < >> blink-dev@chromium.o

  1   2   >