Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test coverage for property-specific colors #17436

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

scottbedard
Copy link
Contributor

@scottbedard scottbedard commented Mar 28, 2025

There are several property-specific color variables available to maintain compatibility with v3. My team and I would like to use them, but would feel more comfortable if they were formally supported by v4. This PR adds test coverage for those features.

@RobinMalfait has confirmed that these features are not intended to be removed, see conversation here →

@crswll Has opened a PR here for the related documentation

@scottbedard scottbedard marked this pull request as ready for review March 28, 2025 17:50
@scottbedard scottbedard requested a review from a team as a code owner March 28, 2025 17:50
Copy link
Member

@philipp-spiess philipp-spiess left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there! Thanks for your contribution. Adding more test coverage here makes sense but there seems to be an issue with box shadows. Mind looking into it?

Comment on lines 21304 to 21307
.shadow-blue-500 {
--tw-shadow: #3b82f6;
box-shadow: var(--tw-inset-shadow), var(--tw-inset-ring-shadow), var(--tw-ring-offset-shadow), var(--tw-ring-shadow), var(--tw-shadow);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems wrong, this ins setting the shadow property and not the shadow-color here. Looks like you want to define this as --box-shadow-color-blue-500.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, good eye. This was a typo and incorrect assertion. Fixed!

5ed59d2

Copy link
Contributor Author

@scottbedard scottbedard Apr 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, now my tests are passing locally, but are failing on CI 🤔

Nevermind, I forgot to pull main 😅
It looks like a browser support features was added that impacted my assertions

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@philipp-spiess Can we merge this? Keeping it out of conflict with the snapshot files is not so fun 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants