chore(tailwind): fix rgba typos in Update tailwind.config.js #2587
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
Invalid CSS: rgb() was used with 4 arguments (rgb(50, 50, 50, 1) and rgb(205, 205, 205, 1)). In comma-separated syntax, rgb() accepts only 3 arguments—alpha must be specified via rgba() or the modern space/slash syntax (rgb(50 50 50 / 1)). Why: Browsers ignore invalid rgb(… , … , … , a) declarations, so any utility relying on base.black/base.blackInvert would silently fall back to previous/ inherited color.
🟡 Heimdall Review Status
|
|
@HarleyQeen is attempting to deploy a commit to the Coinbase Team on Vercel. A member of the Team first needs to authorize it. |
|
@cb-heimdall rebased & squashed to a single commit. Could you approve the workflows and Vercel deployment pls? |
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.
Invalid CSS: rgb() was used with 4 arguments (rgb(50, 50, 50, 1) and rgb(205, 205, 205, 1)). In comma-separated syntax, rgb() accepts only 3 arguments—alpha must be specified via rgba() or the modern space/slash syntax (rgb(50 50 50 / 1)).
Why:
Browsers ignore invalid rgb(… , … , … , a) declarations, so any utility relying on base.black/base.blackInvert would silently fall back to previous/ inherited color.
How I tested:
Ran next build and verified Tailwind compiled without errors.
Confirmed generated CSS includes expected color values for utilities that reference base.black and base.blackInvert.
Notes:
No visual diffs included since this is a correctness fix; behavior is unchanged except that the colors now apply as intended.