Repository navigation
Docs: show the dark-mode border on API example panels - #53
Merged
Merged
Conversation
The :global(.dark) rule in the scoped style compiled to a selector that did not match; move it next to the fenced-code rule in custom.css.
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.
Follow-up to #52. The dark-mode border rule in the component's scoped style didn't match the panel, so the border never appeared. This moves the rule into custom.css, next to the fenced-code border rule.
Local check: the panel border is #36363a in dark mode and unchanged in light mode.
npm run validatepasses.