docs(examples) 🎨: Fix dayClassName specificity issue #72
+14
−1
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
- Previous `text-success` color style was overridden by the default specificity of the react-datepicker__day class. - Added a new class to increase the specificity
balajis-qb
force-pushed
the
docs/fix/css-specificity
branch
from
8b81961 to
27de959
Compare
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.
Problem
This fix is related to a CSS specificity issue in the docsite example "Custom day class name". In that example even though the
dayClassNameis applied properly, it's not applied in the UI due to CSS Specificity issue.Changes
dayClassNamestyle to the day elementScreenshots
Contribution checklist