I went ahead and marked the review as started on chromestatus.com.

On Wed, May 22, 2024 at 7:36 AM Daniel Bratell <[email protected]> wrote:

> Unfortunately it doesn't show up in the API Owner UI/ToDo list and I can't
> directly see how to make it appear. jrobbins, is there anything strange
> with this one? It is very old so it might be different from anything done
> the last couple of years.
>
> /Daniel
> On 2024-05-17 22:39, 'Jiaming Cheng' via blink-dev wrote:
>
> Hi team,
>
> This feature was initially proposed and implemented 4 years ago but
> remained disabled due to a lack of practical use cases. Given our team's
> (chromeOS UI team) plan to use this SkipAd action in our upcoming project,
> we are now resending this intent email for LGTMs. Please let me know if you
> have any questions :]
>
> TAG: https://github.com/w3ctag/design-reviews/issues/957
> Mozilla: https://github.com/mozilla/standards-positions/issues/1026
> Webkit: https://github.com/WebKit/standards-positions/issues/350
>
> Below are the auto generated intent content:
> Contact [email protected], [email protected],
> [email protected]
>
> ExplainerNone
>
> Specificationhttps://wicg.github.io/picture-in-picture/#media-session
>
> Design docs
>
> https://developers.google.com/web/updates/2019/02/chrome-73-media-updates#skipad
> https://github.com/WICG/mediasession/pull/203
>
> Summary
>
> Support the SkipAd media session action. This skipad action allows Chrome
> to show a button in the system media controls or in the PiP window.
>
>
> Blink componentBlink>Media>PictureInPicture
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EMedia%3EPictureInPicture>
>
> TAG review:
> https://github.com/w3ctag/design-reviews/issues/957
>
> TAG review statusPending
>
> Chromium Trial NameSkipAd
>
> Link to origin trial feedback summary
> https://github.com/WICG/picture-in-picture/issues
>
> Origin Trial documentation link
> https://wicg.github.io/mediasession/#dom-mediasessionaction-skipad
>
> Risks
>
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: https://github.com/mozilla/standards-positions/issues/1026
>
> *WebKit*: Positive (
> https://github.com/WICG/mediasession/pull/203#issuecomment-432529816)
> And a new one created:
> https://github.com/WebKit/standards-positions/issues/350
>
> *Web developers*: Positive
>
> *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
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, ChromeOS, Android, and Android WebView)?No
>
> 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 justificationNone
>
> Requires code in //chrome?False
>
> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=910436
>
> Sample links
> https://googlechrome.github.io/samples/picture-in-picture/skip-ad.html
>
> Estimated milestones
> Shipping on desktop
> 127
> Origin trial desktop first
> 73
> Origin trial desktop last
> 74
>
> 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).
> None
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/4749278882824192?gate=4775000754618368
>
> Links to previous Intent discussionsIntent to Experiment:
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/l6sW0G4jzhE
> On Sunday, February 10, 2019 at 2:08:11 AM UTC-8 Yoav Weiss wrote:
>
>> Still LGTM
>>
>> On Thu, Feb 7, 2019 at 9:51 PM François Beaufort <[email protected]>
>> wrote:
>>
>>> After more thoughts, we'd like to extend the original trial to
>>> expire when M75 Stable is cut, instead of M74 Stable cut.
>>> Note that the origin trial didn't start yet.
>>>
>>> On Thursday, February 7, 2019 at 2:24:52 PM UTC+1, Yoav Weiss wrote:
>>>>
>>>> LGTM to experiment
>>>>
>>>> On Mon, Feb 4, 2019 at 8:40 PM François Beaufort <[email protected]>
>>>> wrote:
>>>>
>>>>> Contact emails
>>>>>
>>>>> [email protected], [email protected]
>>>>>
>>>>> Explainer
>>>>>
>>>>> https://github.com/WICG/mediasession/pull/203
>>>>>
>>>>> Design doc/Spec
>>>>>
>>>>> https://wicg.github.io/mediasession/#dom-mediasessionaction-skipad
>>>>>
>>>>> Summary
>>>>>
>>>>> Show a “Skip Ad” button in Picture-in-Picture window that websites can
>>>>> be notified when user interact with.
>>>>>
>>>>> Motivation
>>>>>
>>>>> Video advertisement model usually consist of pre-roll ads. Content
>>>>> providers often provide the ability to skip the ad after a few seconds. 
>>>>> The
>>>>> Picture-in-Picture window being not interactive, users watching a video in
>>>>> Picture-in-Picture can’t do this today. This feature will allow websites 
>>>>> to
>>>>> offer this experience also in the Picture-in-Picture window. This is one 
>>>>> of
>>>>> the most common feature requests around Picture-in-Picture.
>>>>>
>>>>> Risks
>>>>>
>>>>> Interoperability and Compatibility
>>>>>
>>>>> Safari has shipped a vendor-prefixed API for Picture-in-Picture and
>>>>> we’re working
>>>>> <https://github.com/WICG/picture-in-picture/pull/69#issuecomment-405394446>
>>>>> with them on the integration of the Media Session in Picture-in-Picture.
>>>>>
>>>>> Edge: Public support
>>>>> <https://github.com/WICG/picture-in-picture/pull/69#issuecomment-432516966>
>>>>>
>>>>> Firefox: No signals
>>>>>
>>>>> Safari: Public support
>>>>> <https://github.com/WICG/mediasession/pull/203#issuecomment-432529816>
>>>>>
>>>>> Web / Framework developers: Positive
>>>>>
>>>>> Activation
>>>>>
>>>>> Web developers will be able to simply set/unset a media session action
>>>>> handler for “Skip Ad” to control the visibility of the button in the
>>>>> Picture-in-Picture window. Developer documentation will cover this
>>>>> feature as we did before at
>>>>> https://developers.google.com/web/updates/2017/02/media-session.
>>>>>
>>>>> Goals for experimentation
>>>>>
>>>>>    -
>>>>>
>>>>>    Gather feedback about the shape of the API
>>>>>    -
>>>>>
>>>>>    Validate that the API provides sufficient functionality for
>>>>>    content providers using it to deliver user value. This will be 
>>>>> measured by:
>>>>>    -
>>>>>
>>>>>       content providers that join the origin trial and choose to
>>>>>       share their feedback
>>>>>       -
>>>>>
>>>>>       watch time that occurs in Picture in Picture mode
>>>>>
>>>>>
>>>>> Experimental timeline
>>>>>
>>>>>    -
>>>>>
>>>>>    Starts around M73 Beta release, 2019-02-07
>>>>>    -
>>>>>
>>>>>    Expires when M74 Stable is cut, around 2019-04-16
>>>>>
>>>>>
>>>>> Any risks when the experiment finishes?
>>>>>
>>>>> No significant risks - content providers will feature detect and fall
>>>>> back to their current behavior when we disable the origin trial.
>>>>>
>>>>> Ongoing technical constraints
>>>>>
>>>>> None
>>>>>
>>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>>>
>>>>> The feature will be supported on all platforms that currently support
>>>>> the Picture-in-Picture API.
>>>>>
>>>>> Link to entry on the feature dashboard <https://www.chromestatus.com/>
>>>>>
>>>>> https://www.chromestatus.com/feature/4749278882824192
>>>>>
>>>>> --
>>>>> 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 on the web visit
>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b8a46914-72f6-4bc2-a5ba-d10db89ce6f0%40chromium.org
>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b8a46914-72f6-4bc2-a5ba-d10db89ce6f0%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 [email protected].
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/466b0823-d33b-4d3b-a825-53955ca2a5ef%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/466b0823-d33b-4d3b-a825-53955ca2a5ef%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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ad00b08f-9135-4d9c-add6-92d84bc14d4bn%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ad00b08f-9135-4d9c-add6-92d84bc14d4bn%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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8b8baa0d-001b-48c3-bc21-b11240d449c9%40sarasas.se
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8b8baa0d-001b-48c3-bc21-b11240d449c9%40sarasas.se?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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8rOd5U8HCg-09Z84Mvv%2B5uBb732EGC0USunw6BaHWdRw%40mail.gmail.com.

Reply via email to