The last launch gate approval came in today.
Thanks!
On Wed, Apr 3, 2024 at 11:49 AM Thomas Guilbert
wrote:
> I agree that this would have been a viable solution, and this was
> considered and discussed with the spec editors too [1]. These Opus flags
> were originally supposed to be
I agree that this would have been a viable solution, and this was
considered and discussed with the spec editors too [1]. These Opus flags
were originally supposed to be contentHint, but ultimately it would have
only ever been useful for Opus, so it was decided to keep it in the Opus
config.
[1]
FYI, the enterprise policy landed in M124 (under
"PrefixedVideoFullscreenApiAvailability"), and the deprecation trial will
activate when M125 branches, on April 15th.
On Fri, Feb 2, 2024 at 12:16 PM Mike Taylor wrote:
> LGTM3
> On 2/2/24 1:03 AM, Domenic Denicola wrote:
>
> LGTM2. Please be
Thanks for marking it for review!
I submitted a request to review this change to the chromium enterprise
mailing list.
Thanks,
Thomas
On Wed, Jan 31, 2024 at 1:08 PM Mike Taylor wrote:
> Yep - seems that's the cause of confusion. In your first email,
>
Ok for a 6 months trial, with the possibility to extend it further. I will
wait for the remaining security/privacy approvals and then update this
thread again.
Additionally, someone commented on the WebKit positions standards thread
Contact emails
tguilb...@google.com
Explainer
None
Specification
https://w3c.github.io/webcodecs/#dom-audioencoderconfig-bitratemode
Summary
Some audio codecs support specifying the audio encoder bitrate modes. This
feature adds a "bitrateMode" flag with a default value of “variable” to
