Removed re-registering HTTP_ALLOWED content settings.#32992
Merged
Conversation
boocmp
force-pushed
the
content_settings_http_allowed
branch
from
6f71531 to
61b0070
Compare
Contributor
|
Chromium major version is behind target branch (144.0.7559.59 vs 145.0.7632.31). Please rebase. |
github-actions
bot
added
the
chromium-version-mismatch
netzenbot
approved these changes
Feb 28, 2026
boocmp
force-pushed
the
content_settings_http_allowed
branch
from
61b0070 to
9070762
Compare
github-actions
bot
removed
the
chromium-version-mismatch
goodov
approved these changes
Mar 2, 2026
Collaborator
|
Released in v1.89.90 |
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
4 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.
Our registration is pretty the same with the upstream. Looks like this was different at the time, but no longer relevant.