Fix Padding #5
Closed
Fix Padding #5
Conversation
This file contains 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
uncenter
suggested changes
Jun 17, 2024
| @@ -1,8 +1,6 @@ | |||
| .markdown-alert { | |||
| padding: 1em; | |||
| padding: 0 1em !important; | |||
There was a problem hiding this comment.
This is what GitHub itself uses, though maybe it wouldn't even match correctly due to the weird CSS? Looks good to me this way though.
Suggested change
| padding: 0 1em !important; | |
| padding: 0.5rem 1rem !important; |
|
Closing this because I think the root cause of the problem is with the generated CSS packaged with Markdown Preview GitHub Styling extension. See mjbvz/vscode-github-markdown-preview-style#137 (comment) for more details. |
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.
I'm not super fond of using
!importantbut I wasn't sure what selectors were available. Had I known, I would've opted to increase specificity by using a stronger selector.for #4