Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alert on attempt to use Topics API #2762

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

dmarti
Copy link

@dmarti dmarti commented May 5, 2022

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

  • Bug fix (non-breaking change which fixes an issue)
  • [x ] New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • [ x] My code follows the code style of this project.
  • [ x] My change requires a change to the documentation.
  • [ x] I have updated the documentation accordingly.
  • [ x] I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

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!

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
@lgtm-com

This comment was marked as off-topic.

@coliff
Copy link
Member

coliff commented May 6, 2022

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.

@coliff coliff requested a review from roblarsen May 6, 2022 00:01
@dmarti
Copy link
Author

dmarti commented May 6, 2022

@coliff Thank you for reviewing.

@coliff coliff marked this pull request as draft May 6, 2022 02:50
@dmarti
Copy link
Author

dmarti commented May 6, 2022

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.

patcg-individual-drafts/topics#60

Imran-imtiaz48

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants