fix: default to system accent color on invalid user color #47660
+42
−41
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 of Change
Fixes an issue where an invalid color passed as a string to
accentColor
would result in a white accent color. This happened because ourParseCSSColor
utility falls back to white on parse failure. When a user passes an invalid string we should instead fall back to system color.This fixes that by reworking our
ParseCSSColor
utility to return an optional value and leaving it up to the callers to decide their fallback color.cc @bpasero
Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where an invalid color passed as a string to
accentColor
would result in a white accent color.