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

On Wed, Dec 21, 2022 at 12:10 PM Corentin Wallez wrote: > Thank you Rick for the feedback, I'll try to answer the various questions > you have inline but I'm sure more will come up! I'll be OOO shortly, so > CCing a couple folks explicitly for future questions. > Thanks Corentin. Since you're

Re: [blink-dev] Intent to Deprecate: X-Requested-With in WebView

Hi Mike, We plan to open the deprecation trial for sign-up in January. We’re planning to roll out the change in behaviour in M110 Canary/Dev/Beta, and hopefully a small percentage of Stable in M111. The exact ramp-up schedule after that will depend on feedback, and is something we’re still

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

Thank you Rick for the feedback, I'll try to answer the various questions you have inline but I'm sure more will come up! I'll be OOO shortly, so CCing a couple folks explicitly for future questions. On Wed, Dec 21, 2022 at 5:14 PM Rick Byers wrote: > Hi Corentin, > It's exciting to see WebGPU

Re: [blink-dev] Intent to Remove: Calling getDisplayMedia() without user activation

LGTM3 /Daniel On 2022-12-19 18:16, Rick Byers wrote: LGTM2 On Mon, Dec 19, 2022 at 10:41 AM Mike Taylor wrote: LGTM1 - aligning with other browsers on this (and the spec!) is good. 0.0002% is indeed low. I'll also note that it's <1% the usage of getDisplayMedia

Re: [blink-dev] Intent to Ship: Style Container Queries for CSS Custom Properties

LGTM3 On 19/12/2022 14:57, Rune Lillesveen wrote: > On Fri, Dec 16, 2022 at 9:11 PM Rick Byers > wrote: > > LGTM1 > > For other reviewers, I verified these tests are all passing 100% > (thank you Rune!): > >

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

Hi Corentin, It's exciting to see WebGPU close to shipping! Clearly the broad support across browser vendors and web developers means it's just a matter of when, not if, WebGPU will ship. The primary job of API owners in this case is to help ensure that the design and implementation have crossed a

Re: [blink-dev] Intent to Deprecate: X-Requested-With in WebView

Thanks Peter! Can you say more about timelines? For example, which milestone you would launch the deprecation trial, and how long will sites have to enroll before the behavior changes (i.e., what's the milestone for turning XRW off)? A blog post in January sounds great - are there any other

Re: [blink-dev] Intent to Deprecate: X-Requested-With in WebView

Hi Peter, Thanks for the extra details, that makes sense to me and is roughly what I was assuming would be happening. So still LGTM1 Rick On Wed, Dec 21, 2022 at 5:53 AM Peter Birk Pakkenberg wrote: > Hi Rick, Mike, and blink-dev@ > > To clarify my last statement, here is our proposed plan: >

[blink-dev] Re: Ready for Trial: Compute Pressure

Hi, Correction on the previous Ready for Trial email: Debuggability : chrome-internals://compute-pressure *is not existing.* Apoligizing for the confusion. Br Arnaud On Wednesday, December 21, 2022 at 12:23:24 PM UTC+2 Arnaud Mandy wrote: > Contact emails kenneth.r.c...@intel.com > >

Re: [blink-dev] Intent to Deprecate: X-Requested-With in WebView

Hi Rick, Mike, and blink-dev@ To clarify my last statement, here is our proposed plan: We intend to start a deprecation trial, which will retain the current behaviour of sending the X-Requested-With header from WebView clients, however, as an opt-in rather than default behaviour. This trial is

[blink-dev] Ready for Trial: Compute Pressure

Contact emails kenneth.r.christian...@intel.com Explainer https://github.com/WICG/compute-pressure/blob/main/README.md Specification https://www.w3.org/TR/compute-pressure Summary Provides a way for websites to react to changes in the CPU pressure of