[Website]: Fix cut off list items in demo-server-info panel #2190
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
lsymds
pushed a commit
to lsymds/htmx
that referenced
this pull request
Jan 20, 2024
…ftware#2190) Fix cut off list items in demo-server-info panel
rekado
pushed a commit
to rekado/htmx
that referenced
this pull request
Feb 9, 2024
…ftware#2190) Fix cut off list items in demo-server-info panel
FraserChapman
pushed a commit
to FraserChapman/htmx
that referenced
this pull request
Feb 16, 2024
…ftware#2190) Fix cut off list items in demo-server-info panel
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.
Description
This PR resolves #2189
Fixes a small visual bug on the docs site where list items in the demo-server-info panel are cut off because they overflow past the edge of the viewport.
Before fix:
After fix:
Again, (as I mentioned in #2188), apologies if I'm jumping the gun by sending this PR before explicit approval of the associated issue. This was also a one-line CSS fix, so I thought it wouldn't hurt to just send in a PR at the same time as the issue.
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded