LGTM3 On Wednesday, September 24, 2025 at 8:14:08 AM UTC-7 [email protected] wrote:
> LGTM2 > > On Wednesday, September 24, 2025 at 8:13:25 AM UTC-7 [email protected] > wrote: > >> LGTM1 >> >> On Tuesday, September 23, 2025 at 4:57:15 PM UTC-4 Tommy Steimel wrote: >> > *Contact emails* >>> [email protected] >>> >> >>> >>> *Explainer* >>> None >>> >>> *Specification* >>> https://github.com/w3c/mediasession/pull/362 >>> >>> *Summary* >>> Adds `enterPictureInPictureReason` to the `MediaSessionActionDetails` >>> sent to the `enterpictureinpicture` action in the Media Session API. This >>> allows developers to distinguish between `enterpictureinpicture` actions >>> triggered explicitly by the user (e.g. from a button in the user agent) and >>> `enterpictureinpicture` actions triggered automatically by the user agent >>> due to the content becoming occluded. >>> >>> *Blink component* >>> Blink>Media>Session >>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EMedia%3ESession%22> >>> >>> *Web Feature ID* >>> media-session <https://webstatus.dev/features/media-session> >>> >>> *TAG review* >>> N/A, minor change to existing spec >>> >>> *TAG review status* >>> Not applicable >>> >>> *Risks* >>> >>> >>> *Interoperability and Compatibility* >>> N/A >>> >>> *Gecko*: No signal >>> >>> *WebKit*: Positive (https://github.com/w3c/mediasession/pull/362) Approved >>> specification change >>> >>> *Web developers*: Strongly positive We've received requests from >>> multiple sites for this information >>> >>> *Other signals*: >>> >>> *Ergonomics* >>> N/A >>> >>> *Activation* >>> N/A >>> >>> *Security* >>> N/A >>> >>> *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 >>> >>> >>> *Debuggability* >>> Can use devtools to inspect the received MediaSessionActionDetails object >>> >>> *Will this feature be supported on all six Blink platforms (Windows, >>> Mac, Linux, ChromeOS, Android, and Android WebView)?* >>> Yes >>> >>> *Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >>> NoNot able to trigger media session actions with web platform testing >>> tooling >>> >>> *Flag name on about://flags* >>> None >>> >>> *Finch feature name* >>> None >>> >>> *Non-finch justification* >>> Just a new bool sent inside an existing object >>> >>> *Rollout plan* >>> Will ship enabled for all users >>> >>> *Requires code in //chrome?* >>> False >>> >>> *Tracking bug* >>> https://issues.chromium.org/u/1/issues/446738067 >>> >>> *Estimated milestones* >>> Shipping on desktop 142 >>> Shipping on Android 142 >>> Shipping on WebView 142 >>> >>> *Anticipated spec changes* >>> >>> Open questions about a feature may be a source of future web compat or >>> interop issues. Please list open issues (e.g. links to known github issues >>> in the project for the feature specification) whose resolution may >>> introduce web compat/interop risk (e.g., changing to naming or structure of >>> the API in a non-backward-compatible way). N/A >>> >>> *Link to entry on the Chrome Platform Status* >>> https://chromestatus.com/feature/6415506970116096?gate=4969788698918912 >>> >>> 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/af01bbd3-c9fb-4bd0-9253-db57e8fb5c50n%40chromium.org.
