Hi Jeffrey Thanks for the feedback, and sorry about the delay. I updated the chromestatus entry as you suggested, and just sent an I2S. The feature is landed off-by-default right now.
Thanks Frank On Thursday, May 9, 2024 at 10:00:50 AM UTC-7 jyas...@chromium.org wrote: > Could you confirm that you meant to send an Intent to Prototype here? You > have "Shipping on desktop 126" in Estimated milestones, and > https://chromestatus.com/feature/5183881532932096 has some of the Prepare > to ship reviews approved, but you haven't checked the box at the top of > https://chromestatus.com/guide/stage/5183881532932096/5/5080971834818560 > to set the "prepare to ship" stage, and your implementation status is set > to "No active development". What's the actual state of this feature? > > All of these affect the position of the feature in > https://chromestatus.com/reports/external_reviews/gecko, which I'm trying > to make useful for Mozilla to prioritize its reviews. > > Thanks, > Jeffrey > > On Fri, Apr 26, 2024 at 5:11 PM 'Frank Liberato' via blink-dev < > blin...@chromium.org> wrote: > >> Contact emails: libe...@chromium.org, ste...@chromium.org >> >> Explainer: None >> >> Specification: >> https://github.com/WICG/document-picture-in-picture/pull/119 >> >> Summary >> >> This adds a new parameter ("ignorePreviousWindowBounds") to the document >> picture-in-picture API that, when set to true, hints to the user agent that >> it should not try to reuse the position or size of the previous document >> picture-in-picture from this site when opening this one. Often, a document >> picture-in-picture window will close and re-open multiple times for the >> same site, such as moving a video conference to and from PiP. The user >> agent is free to re-open the PiP window at its most recent size / location, >> so that it stays where the user last moved it and provides continuity >> between the PiP windows. However, if the new window is semantically >> unrelated to the previous window, such as if it is a new VC, then the >> developer can use this parameter provide a hint to the user agent that this >> window might be better opened in its default position / size instead. >> >> >> Blink component: Blink>Media>PictureInPicture >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia%3EPictureInPicture> >> >> Motivation >> >> Often, a document picture-in-picture window will close and re-open >> multiple times for the same site, such as moving a video conference to and >> from PiP. The user agent is free to re-open the PiP window at its most >> recent size / location, so that it stays where the user last moved it and >> provides continuity between the PiP windows. However, if the new window is >> semantically unrelated to the previous window, such as if it is a new VC, >> then the developer can use this parameter provide a hint to the user agent >> that this window might be better opened in its default position / size >> instead. >> >> >> Initial public proposal: None >> >> TAG review: None >> >> TAG review status: Pending >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/670#issuecomment-2072932641 >> ) >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/41#issuecomment-2072931535 >> ) >> >> *Web developers*: Positive ( >> https://github.com/WICG/document-picture-in-picture/issues/120) >> >> *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? >> >> None >> >> >> Debuggability >> >> None >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justification >> >> not required due to "Simple parameter changes (adding params, changing >> the type etc.)" -- this feature simply adds one boolean to an existing >> param structure. >> >> >> Requires code in //chrome?False >> >> Estimated milestones >> Shipping on desktop >> 126 >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5183881532932096?gate=5102907239432192 >> >> 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+...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/30002034-794f-4c61-a6f1-186ba7ff004dn%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/30002034-794f-4c61-a6f1-186ba7ff004dn%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- 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/5853ca0d-1933-4337-b098-b7776616f220n%40chromium.org.
