Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

Friendly ping. It looks like conversation died down ~2 weeks ago. Has there been movement in the meantime, or should we consider this intent on hold for a while? -mike On Tuesday, September 20, 2022 at 11:21:13 AM UTC+2 Yoav Weiss wrote: > Once the PR lands, this seems fine to ship (IMO). Let

Re: [blink-dev] Re: Intent to Experiment: User Agent Reduction Origin Trial

I agree with Rick's analysis here. Given the purely-negative nature of this OT, there's little risk in this burning-in unless we ship it, in which case we want it to burn in. Dropping the usage limitation for this OT LGTM2. -mike On Fri, Sep 30, 2022 at 7:34 PM Mike Taylor wrote: > On 9/30/22

Re: [blink-dev] Intent to Ship: CSS Overflow for replaced elements

Thanks for the details, Nic! :) Should we be worried about the numbers of deprecation reports you're seeing for this specific intent? On Mon, Oct 3, 2022 at 8:37 PM Nic Jansma wrote: > Thank for updating the message! > > Yoav - For our RUM product, we have a limited set of customers that have >

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

The spec PR is approved and we'll be landing the spec change today or tomorrow. In the meantime, we would like to answer any questions for the Blink API Owner approval. Cheers, Hongchan On Tue, Oct 4, 2022 at 1:16 AM Mike West wrote: > Frie

Re: [blink-dev] Re: Intent to Implement and Ship: Trusted Types fromLiteral

This seems like a pretty minor and uncontroversial extension to trusted types to me. But it also seems like a good time to just check-in on the state of discussion around TrustedTypes with other vendors. I see Mozilla has a "neutral " s

Re: [blink-dev] Re: Intent to Implement and Ship: Trusted Types fromLiteral

Oh, I should also add that I reviewed the TAG design review of trusted types. It sounds like TAG was only able to provide feedback on the high-level design, not API-by-API detail, so I suspect TAG wouldn't find value in spending time on this one

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

The spec change has been landed: https://webaudio.github.io/web-audio-api/#dom-audiocontext-setsinkid -Hongchan On Tue, Oct 4, 2022 at 7:40 AM Hongchan Choi wrote: > The spec PR is approved > and we'll be > landing the spec change today or

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

LGTM1 On 10/4/22 5:30 PM, Hongchan Choi wrote: The spec change has been landed: https://webaudio.github.io/web-audio-api/#dom-audiocontext-setsinkid -Hongchan On Tue, Oct 4, 2022 at 7:40 AM Hongchan Choi wrote: The spec PR is approved

[blink-dev] Intent to Experiment: Network State Partitioning (once more, with feeling)

** *Contact emails* * brgoldst...@chromium.org , miketa...@chromium.org , mme...@chromium.org Summary We would like to run another experiment for the Network State Partitioning eff

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

LGTM2. Mozilla is positive. Interoperability risk looks small. On Wed, Oct 5, 2022 at 7:08 AM Mike Taylor wrote: > LGTM1 > > On 10/4/22 5:30 PM, Hongchan Choi wrote: > > The spec change has been landed: > https://webaudio.github.io/web-audio-api/#dom-audiocontext-setsinkid > > -Hongchan > > > O

Re: [blink-dev] Intent to Ship: AudioContext.setSinkId()

LGTM3 On Wed, Oct 5, 2022, 00:54 TAMURA, Kent wrote: > LGTM2. > Mozilla is positive. Interoperability risk looks small. > > > On Wed, Oct 5, 2022 at 7:08 AM Mike Taylor wrote: > >> LGTM1 >> >> On 10/4/22 5:30 PM, Hongchan Choi wrote: >> >> The spec change has been landed: >> https://webaudio.gi