Editorial review: Topics API docs #30107
Merged
Conversation
This file contains 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
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
This pull request has merge conflicts that must be resolved before it can be merged. |
github-actions
bot
added
size/l
wbamberg
requested changes
Feb 22, 2024
Co-authored-by: wbamberg <[email protected]>
Co-authored-by: wbamberg <[email protected]>
Co-authored-by: wbamberg <[email protected]>
Co-authored-by: wbamberg <[email protected]>
3 tasks
|
Yay, thanks @wbamberg! |
|
Thanks all, for being so patient and thorough!
One thing we'll need to update:
developer.mozilla.org/en-US/docs/Web/API/Topics_API/Using#selecting_topics_of_interest_to_influence_ad_choice
The algorithm for top topics selection used by Chrome has been updated:
developers.google.com/privacy-sandbox/blog/topics-enhancements. With a
little tweaking, we could pretty much use that explanation as it is.
…On Fri, 23 Feb 2024 at 09:28, Chris Mills ***@***.***> wrote:
Yay, thanks @wbamberg <https://github.com/wbamberg>!
—
Reply to this email directly, view it on GitHub
<#30107 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABSDKRK32WQK6YEPIUGHU3YVBOLNAVCNFSM6AAAAAA7CXGMRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRQHE4DSMZYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
#28196 contains the engineering technical review for my work on Topics API docs, which has been completed and approved. Thank you to @samdutton for your thorough and detailed review work.
This is a new PR based on the same branch, which is intended to contain the editorial review for the same work.
Background information
The Topics API is an integral part of Google's privacy sandbox technologies. Many parts of this set are being made available by default in Chrome 115 (depending on a gradual ramp up to 100% of userbase over the 115 release period).
This PR provides documentation for the Topics API and its related HTTP headers and HTTP features.
See my research document for more details of exactly what changes are expected in the PR.
Motivation
Additional details
Related issues and pull requests