Remove Wayland color manager disabling flag from Chromium configs (#4610)#4615
Merged
dhh merged 1 commit intobasecamp:devfrom Feb 17, 2026
Merged
Conversation
…secamp#4610) Signed-off-by: Shreyansh Malviya <shreyanshmalviya0012@gmail.com>
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
2 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.
Fix: This commit removes the
--disable-features=WaylandWpColorManagerV1flag fromchromium-flags.confandbrave-flags.confconfig files as discussed in #4610The
--disable-features=WaylandWpColorManagerV1flag was added as a temporary measure to resolve the browser window crashing on monitor change hyprwm/Hyprland#11957The flag was added through this commit introducing 1760401344.sh migration.
What this fixes:
and other stuff that Wayland Color Manager has to offer.
Sufficient amount of time has passed after the Chromium upstream fix Review #7003036.