fix(style): adjust alignment of copy button for smaller code blocks#7807
Open
TusharThakur04 wants to merge 2 commits intowebpack:mainfrom
Open
fix(style): adjust alignment of copy button for smaller code blocks#7807TusharThakur04 wants to merge 2 commits intowebpack:mainfrom
TusharThakur04 wants to merge 2 commits intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
@evenstensberg please review |
evenstensberg
requested changes
Feb 12, 2026
Member
evenstensberg
left a comment
There was a problem hiding this comment.
could you pad the top abit too?
Contributor
Author
|
@evenstensberg
|
Member
|
Yes |
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.

Summary
This PR corrects the copy button positioning for smaller code blocks
What kind of change does this PR introduce?
style
Did you add tests for your changes?
no
Does this PR introduce a breaking change?
no
before
after