torgo
commented
1 month ago Just a quick note - and noting this is not formal TAG feedback, but a question that came up in our discussion in this morning's breakout call where we discussed this: could this API could be generalized so that it's not specifically referencing advertizing but more the general use case of skipping an intro or skipping "to the main content"? It feels like there are multiple cases where this could be used that are not advertizing related, and also we don't currently have other APis in the platform that are just supporting advertising.
martinthomson
miketaylr
chrisn
matatk
こんにちは 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:
External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): https://chromestatus.com/feature/4749278882824192?gate=6100738773614592
Further details:
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.