Open
Conversation
This flag has been at ga=0.5 in all regions since Nov 2023 — over 2 years at 50% rollout. Its only effect is setting the Document-Policy: js-profiling HTTP header. There's no reason it shouldn't be 100%. Always set the header unconditionally.
github-actions
bot
added
the
Scope: Backend
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
1 participant
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.
This flag has been at ga=0.5 in all regions since Nov 2023. Its only effect is setting the Document-Policy: js-profiling HTTP header. There's no reason it shouldn't be 100%.
Always set the header unconditionally.
Alternatively - should we just remove this feature?