[blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

Contact emails tguilb...@chromium.org Explainer None Specification https://fullscreen.spec.whatwg.org/#dom-document-fullscreenenabled Summary There was an attempt in 2014 to deprecate and remove the HTMLVideoE

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

on Trial, or would this sampling be enough? Thank you, Thomas On Sun, Jan 21, 2024 at 7:56 PM Domenic Denicola wrote: > It would be very exciting to clean this up! I have some questions that > might help clarify the cost-benefit analysis. > > On Sat, Jan 20, 2024 at 6:43 AM T

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

e: > > > On Tue, Jan 23, 2024 at 7:55 AM Thomas Guilbert > wrote: > >> Good point about the most used APIs being the boolean properties! The >> APIs are now only aliases for the standard non-prefixed fullscreen APIs (see >> this code for the current implementation >

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

I opened a support ticket with Mux, and opened an issue for Clappr <https://github.com/clappr/clappr/issues/2136>. On Wed, Jan 24, 2024 at 3:40 PM Thomas Guilbert wrote: > I've created a new ChromeStatus entry > <https://chromestatus.com/feature/5111638103687168>, and

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

> >>> Just thought to mention it but iOS never supported the generic >>> fullscreen API until very recent >>> https://twitter.com/jensimmons/status/1717937227190460797 >>> It always required the webkit prefixed API on the video element (not any >>>

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

is currently blocking LGTMs). >> >> On Wednesday, January 24, 2024 at 7:23:28 AM UTC-5 Mike Taylor wrote: >> >>> Would you mind requesting reviews for the various gates (privacy, >>> security, debuggability) for an OT/DT in your chromestatus entry? >>> On

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

n > trial to re-enable them for 6 months. If you hear feedback requesting an > extension towards the end of those 6 months, please request an extension > for another 6 months. > > On Thu, Feb 1, 2024 at 12:43 AM Thomas Guilbert > wrote: > >> Thanks for marking it for r

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

Contact emailstguilb...@chromium.org ExplainerNone Specification https://w3c.github.io/webcodecs/opus_codec_registration.html#dom-opusencoderconfig-signal Summary `OpusEncoderConfig.signal` and `OpusEncoderConfig.application` were recently added to the WebCodecs spec [1]. Both parameters are ma

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

y? > > On Tuesday, March 26, 2024 at 11:29:53 PM UTC+1 Thomas Guilbert wrote: > >> Contact emailstguilb...@chromium.org >> >> ExplainerNone >> >> Specification >> https://w3c.github.io/webcodecs/opus_codec_registration.html#dom-opusencoderco

[blink-dev] Intent to Prototype: Transferable RTCDataChannel to workers

Contact emailstguilb...@chromium.org ExplainerNone Specification https://w3c.github.io/webrtc-extensions/#rtcdatachannel-transferable Summary The RTCDataChannel interface is part of the WebRTC standard, and represents a network channel which can be used for bidirectional peer-to-peer transfers

[blink-dev] Intent to Implement & Ship: Transferable RTCDataChannel to dedicated workers

Contact emailstguilb...@chromium.org ExplainerNone Specification https://w3c.github.io/webrtc-extensions/#rtcdatachannel-transferable Summary The RTCDataChannel interface is part of the WebRTC standard, and represents a network channel which can be used for bidirectional peer-to-peer transfers

Re: [blink-dev] Intent to Implement & Ship: Transferable RTCDataChannel to dedicated workers

> >> LGTM1 >> >> /Daniel >> On 2024-08-09 01:21, Thomas Guilbert wrote: >> >> Contact emails tguilb...@chromium.org >> >> Explainer None >> >> Specification >> https://w3c.github.io/webrtc-extensions/#rtcdatachannel-transferable >&

Re: [blink-dev] Intent to Implement & Ship: Transferable RTCDataChannel to dedicated workers

The security review concluded last week. The change to enable this by default has landed, and will be available starting in M130: https://chromium.googlesource.com/chromium/src.git/+/1f5f2853635ab7a43d3507f02e1de903d2703019 Thank you! On Thu, Aug 15, 2024 at 12:26 PM Thomas Guilbert wrote

[blink-dev] Intent to Ship: Remove Prefixed HTMLVideoElement Fullscreen APIs

Contact emailstguilb...@chromium.org ExplainerNone SpecificationNone Summary The prefixed HTMLVideoElement-specific fullscreen APIs have been deprecated since approximately M38. They were replaced by the Element.requestFullscreen() API, which first shipped un-prefixed in M71, in 2018. As of 202

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

there is pushback. Does this sound like a reasonable plan? Thank you, Thomas On Tue, Apr 2, 2024 at 5:47 PM Thomas Guilbert wrote: > FYI, the enterprise policy landed in M124 (under > "PrefixedVideoFullscreenApiAvailability"), and the deprecation trial will > activate when M125

[blink-dev] Intent to Implement & Ship: AudioEncoderConfig.bitrateMode

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 WebC

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

rial. So how about we > start with 6 months, and if we see that there are sites using the trial to > re-enable the feature, then we extend it by another 6 months. Would that > work? > > On Thu, Jan 25, 2024 at 9:22 PM Thomas Guilbert > wrote: > >> Thank you Wesley fo

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

com/feature/5259513871466496 is linked from the > bottom, so our review tooling is presenting that to us. But I've just > flagged the new one so it will show up as well. > > thanks! > On 1/31/24 2:41 PM, Thomas Guilbert wrote: > > I requested privacy/security/debuggability

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

> LGTM2. Please be sure to update Chrome Status with the deprecation trial > timelines and removal milestones so that data gets fed into the feature > dashboard, beta blog posts, etc. > > On Fri, Feb 2, 2024 at 7:35 AM Thomas Guilbert > wrote: > >> Thank you! >> >&

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

chromium.org/d/msgid/blink-dev/CADxkKiLH6ViLccGxHZzbCG_ChtSxiG59XoeYMPRqeW1Wk410rg%40mail.gmail.com > > [2] ContentHint: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9K9_YmJRFn%3DQBKb0GsETsSFex0DPprMRRpWUWgcvAtbA%40mail.gmail.com > > > On 2024-03-28 08:43, Yoav Weiss (@Shopify) wrote: > > Thanks

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

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 suppo

Re: [blink-dev] Intent to Implement & Ship: Transferable RTCDataChannel to dedicated workers

c-pc/issues/2986> to start a discussion. Thanks for the suggestion! On Thu, Aug 15, 2024 at 11:55 AM Vladimir Levin wrote: > LGTM3 > > On Thu, Aug 15, 2024 at 12:11 AM Domenic Denicola > wrote: > >> LGTM2. >> >> On Fri, Aug 9, 2024 at 8:22 AM Thomas

Re: [blink-dev] Request for Deprecation Trial : HTMLVideoElement-specific Prefixed Fullscreen API

; > On Tue, Oct 15, 2024 at 1:39 PM Thomas Guilbert > wrote: > >> The deprecation trial has been underway for ~6months. A small handful of >> websites have registered for the OT. M131 has branched, and is the last >> release with the deprecation trial. >> >> U

Re: [blink-dev] Intent to Ship: Remove Prefixed HTMLVideoElement Fullscreen APIs

On Wed, Nov 6, 2024 at 7:28 AM Yoav Weiss (@Shopify) wrote: > > > On Mon, Nov 4, 2024 at 7:20 PM Thomas Guilbert > wrote: > >> Contact emailstguilb...@chromium.org >> >> ExplainerNone >> >> SpecificationNone >> >> Summary >> >