Note on the WebKit signal: They do have some concerns listed on the GitHub issue but no official position On Monday, January 9, 2023 at 11:15:30 AM UTC-8 Tommy Steimel wrote:
> Contact emailsstei...@chromium.org, liber...@chromium.org, > y...@chromium.org > > Explainer > https://github.com/WICG/document-picture-in-picture/blob/main/README.md > > Specificationhttps://wicg.github.io/document-picture-in-picture > > Summary > > Document PiP adds a new API to open an always-on-top window that can be > populated with arbitrary HTMLElements. This is an expansion upon the > existing HTMLVideoElement API that only allows for an HTMLVideoElement to > be put into a PiP window. This allows web developers to provide a better > PiP experience to users. > > > Blink componentBlink>Media>PictureInPicture > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia%3EPictureInPicture> > > TAG reviewhttps://github.com/w3ctag/design-reviews/issues/798 > > TAG review statusPending > > Risks > > > Interoperability and Compatibility > > > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/670) > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/41) > > *Web developers*: Positive ( > https://discourse.wicg.io/t/proposal-document-picture-in-picture/5736/2?u=steimel) > > In addition to the linked comment, we have some signals from partners that > this would be valuable, and are checking to see if they are OK making that > public > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > N/A since we are not enabling this API on Android > > > Goals for experimentation > > We want to make sure the API is ergonomic/powerful enough to enable > websites to provide the improved picture-in-picture experiences they've > wanted to create (improved vs the existing video picture-in-picture API). > We'll look at developer feedback for issues/limitations that we hadn't > considered. We'll look at the usage of the CSS copying feature to see if > it's actually useful and worth pursuing. > > > Reason this experiment is being extended > > N/A > > > Ongoing technical constraints > > None > > > Debuggability > > The new methods and properties proposed in this spec will show up in > autocomplete functionality (e.g. window.documentPictureInPicture). The > enter event will support event listener breakpoints in the > "Picture-in-Picture" category. > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?No > > At least initially, we're not supporting Android since the Android APIs > don't easily support always-on-top windows with arbitrary interaction > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > > Flag nameDocument Picture-in-Picture API > > Requires code in //chrome?True > > Tracking bughttps://crbug.com/1269059 > > Launch bughttps://crbug.com/1269059 > > Estimated milestones > OriginTrial desktop last 115 > OriginTrial desktop first 111 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5755179560337408 > > Links to previous Intent discussionsIntent to prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGyVZ8L-SmBFbBMvvbm0x3TwZ66JQ1Fm7_zb3nSiBvYhXavAuA%40mail.gmail.com > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/03e97552-6e27-4c24-8a79-7b2f7f43e28en%40chromium.org.
