Add Skip-Ad media session action

[jiajiabingcheng]

こんにちは TAG-さん!

I'm requesting a TAG review of Adding Skip-Ad media session action.

This feature was initially proposed and implemented four years ago but remained disabled due to a lack of practical use cases. It already received LGTM from the Blink dev group back in February 2019. Given our team's plan to implement a feature related to this action, we are now proposing to enable it.

• Explainer¹ (minimally containing user needs and example code):
  https://developer.chrome.com/blog/media-updates-in-chrome-73#skipad

• Specification URL: https://www.w3.org/TR/mediasession/#dom-mediasessionaction-skipad

• Tests: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/mediasession/setactionhandler.html

• User research: [url to public summary/results of research]

• Security and Privacy self-review²:
  This new action does not provide any new data to the website. We just add a new media session action for the website to register an action handler for, but does not expose new data to the website. See more in the security and Privacy section in the Chrome Status

• GitHub repo:
  N/A

• Primary contacts (and their relationship to the specification):
  Jiaming Cheng (@jiajiabingcheng), Google

• Organization(s)/project(s) driving the specification:
  Google, SkipAd

• Key pieces of existing multi-stakeholder (e.g. developers, implementers, civil society) support, review or discussion of this specification:

  • Chromium comments: [url]
  • Mozilla comments: Support Skip-Ad media session action mozilla/standards-positions#1026
  • WebKit comments: Support Skip-Ad media session action WebKit/standards-positions#350
  • Etc.

• External status/issue trackers for this specification (publicly visible, e.g. Chrome Status):
  https://chromestatus.com/feature/4749278882824192?gate=6100738773614592

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: [please provide]
• The group where the work on this specification is currently being done:
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue):
• Major unresolved issues with or opposition to this specification:
• This work is being funded by:

You should also know that...

[please tell us anything you think is relevant to this review]

---

CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Please preview the issue and check that the links work before submitting.

In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer fully public documents though, since we work in the open.

¹ We require an explainer to give the relevant context for the spec review, even if the spec has some background information. For background, see our explanation of how to write a good explainer. We recommend the explainer to be in Markdown.

² A Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.

³ For your own organization, you can simply state the organization's position instead of linking to it. Chromium doesn't have a standards-positions repository and prefers to use comments from the teams that maintain the relevant area of their codebase.