fix: restore resolved badge contrast - #166
Merged
Merged
Conversation
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.
Summary
The Resolved badge appeared as a solid green bar because its text and background both resolved to the same green in Obsidian's default theme. Use the theme's secondary background with green text and a border, matching the existing Confirmed and Eligible badges.
Extend the existing contrast regression check to cover Resolved; the check fails before the CSS change and passes afterward.
Validation
npm run lintnpm run lint:obsidian-warningsnpm run buildnpm test(780 tests across 56 files)npm pack --dry-run(8 package files)Live Obsidian visual verification has not been performed for this patch.