Draft
Conversation
As multiple third-party scripts might be added to a site during development, it can be difficult to see when a script is attempting to use new browser features that might have privacy consequences. Consider adding a simple alert so that scripts can be checked and/or the site Permissions-Policy set before deploying to production. The "alert" is for development purposes, and could be replaced with an analytics event if a site wants to monitor attempted use of Topics API by third parties in production. Related: h5bp#2459
This comment was marked as off-topic.
This comment was marked as off-topic.
Member
|
interesting info - thanks for sharing! This might be useful to include in the docs once it becomes a standard/shipping in browsers - right now it's just in initial draft stage so I don't think it should be part of the base template or docs just yet. |
Author
|
@coliff Thank you for reviewing. |
Author
|
There is an issue in the Topics API repository for a better opt-out in HTML, such as a meta tag. If there is a better opt out in the final version of the proposal I will modify this draft pull request. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As multiple third-party scripts might be added to a site during
development, it can be difficult to see when a script is
attempting to use new browser features that might have privacy
consequences.
Consider adding a simple alert so that scripts can be checked and/or
the site Permissions-Policy set before deploying to production.
The "alert" is for development purposes, and could be replaced with
an analytics event if a site wants to monitor attempted use of
Topics API by third parties in production.
Related: #2459
Types of changes
Checklist:
Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project. With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code. Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.
Thanks!