fix: explicit border-gray-200 on Nuxt page elements#5347
Merged
Conversation
Yndira-E
enabled auto-merge
July 20, 2026 15:13
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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
On Nuxt-served pages,
theme.cssloads afterstyle.cssand its Tailwind v4 preflight (border: 0 solid) resets the default border color to currentColor, overriding the border-color: var(--color-gray-200) thatstyle.csssets in@layer base. This caused border and border-b elements on Nuxt pages to render with the inherited text color instead of the expected light gray.Fix: add explicit
border-gray-200to the two affected elements in Nuxt pages.Related Issue(s)
Checklist