Conversation
- Use resolved `colorScheme` instead of `mode` - Add regression test and changelog entry
This branch has not been deployed
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
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.
Issue
ImageColourSchemeSwitch(and soLogo) shows the light image when the OS is in dark mode and the user hasn't picked a mode.It decides on
useColorScheme().mode, which stays"system"until a mode is chosen, somode === "dark"is false even when the page renders dark. Seen in an app on0.7.2-rc.0: the page haddata-mode="dark", but the light logo sat on a dark header.This seems to be the case since v0.6.0.
Fix
colorSchemeinstead ofmodedata-testidon the same valueColourSchemeButtonis the only other user ofuseColorScheme, and it already handles"system".Consumer note
Apps passing
fixedToneas a workaround can remove it once this is released.