Re: [blink-dev] Re: Intent to Ship: WebGPU: GPUAdapterInfo isFallbackAdapter attribute

LGTM2 On Thu, Mar 27, 2025 at 6:43 PM Yoav Weiss (@Shopify) < yoavwe...@chromium.org> wrote: > LGTM1 > > On Monday, March 24, 2025 at 10:13:11 AM UTC-4 François Beaufort wrote: > >> Contact emailsfbeauf...@google.com >> >> ExplainerThe GPUAdapter isFallbackAdapter boolean attribute currently >>

[blink-dev] Intent to Ship: Protected Audience: Creative scanning via BYOS/V1 trusted scoring signals

Contact emails o...@google.com, pauljen...@chromium.org, morlov...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1406 Specifically, see addition of creativeScanningMetadata to the interest group here

Re: [blink-dev] Intent to Ship: AudioContext Interrupted State

LGTM3 - it's nice to see cross-vendor support for this. On 3/28/25 5:35 AM, TAMURA, Kent wrote: LGTM2. On Thu, Mar 27, 2025 at 12:37 AM Chris Harrelson wrote: LGTM1 On Tue, Mar 25, 2025 at 1:57 PM Chromestatus wrote: Contact emails gabrielbr...@micr

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

Hello Philipp. Philipp is the "vocal member of our community" that I referenced earlier as you may have guessed. Regarding "for what gain?", I think it is good that all browsers align on behavior to avoid edge case surprises. That is good in and of itself. Considering the latest spec changes in

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

Am Fr., 28. März 2025 um 08:31 Uhr schrieb Harald Alvestrand : > WRT "no SSRC signalling": Of course it's allowed to include RFC 5576 style > signalling if you want to. > But RFC 8829 (JSEP) has only this reference to 5576: > > >- Any "a=ssrc" attributes MUST be parsed as specified in [RFC5576

Re: [blink-dev] Re: Intent to Ship: WebGPU: GPUAdapterInfo isFallbackAdapter attribute

LGTM3 On 3/28/25 5:44 AM, TAMURA, Kent wrote: LGTM2 On Thu, Mar 27, 2025 at 6:43 PM Yoav Weiss (@Shopify) wrote: LGTM1 On Monday, March 24, 2025 at 10:13:11 AM UTC-4 François Beaufort wrote: Contact emails fbeauf...@google.com

[blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

Contact emails h...@chromium.org, h...@chromium.org ExplainerNone Specification https://w3c.github.io/webrtc-stats/#the-rtp-statistics-hierarchy Summary RTP stats objects, of type "outbound-rtp" or "inbound-rtp" in this case, represents a WebRTC stream. The identifier of this stream is the SSR

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

WRT "no SSRC signalling": Of course it's allowed to include RFC 5576 style signalling if you want to. But RFC 8829 (JSEP) has only this reference to 5576: - Any "a=ssrc" attributes MUST be parsed as specified in [RFC5576 ], Section 4.1

Re: [blink-dev] Intent to Ship: [WebRTC getStats] Align implementations on when RTP stats should be created

4 Am Fr., 28. März 2025 um 05:47 Uhr schrieb Henrik Boström : > Contact emails > h...@chromium.org, h...@chromium.org > > ExplainerNone > > Specification > https://w3c.github.io/webrtc-stats/#the-rtp-statistics-hierarchy > > Summary > > RTP stats objects, of type "outbound-rtp" or "inbound-rtp" in

[blink-dev] Re: I2P&S: Strict Same Origin Policy for Storage Access API

Thanks Alex (and Vlad), those concerns make sense. Re: next steps, I've improved the existing UMA, but more importantly, I added a UKM-based UseCounter that will precisely measure the % of pageloads that would be affected by this chang

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Hi Mike, Thank you for your feedback. We've redoubled our efforts to investigate the root cause of the flakiness and are looping in more people internally to assist with this. I agree with disabling the feature for now - I will submit a CL to disable it and will keep you posted on how we plan

Re: [blink-dev] Intent to Ship: Type-agnostic var() fallback

On Mon, Mar 17, 2025 at 7:18 PM Alex Russell wrote: > Hey Anders, > > I deeply appreciate the work you did to investigate the incompatibilities > you found. 👍 > Dan noted that we hadn't filed for signals with the other engines > directly. Can you do that? > I intentionally didn't, since this

Re: [blink-dev] Intent to Ship: AudioContext Interrupted State

LGTM2. On Thu, Mar 27, 2025 at 12:37 AM Chris Harrelson wrote: > LGTM1 > > On Tue, Mar 25, 2025 at 1:57 PM Chromestatus < > ad...@cr-status.appspotmail.com> wrote: > >> Contact emails gabrielbr...@microsoft.com, stev...@microsoft.com >> >> Explainer >> https://github.com/MicrosoftEdge/MSEdgeExp