Skip to content

Conversation

@adamwathan
Copy link
Member

This PR fixes an issue I discovered when live-streaming a few weeks ago that prevents code like this from working:

<div class="shadow-[0px_2px_4px] shadow-red-500">

Currently in the v4 engine, arbitrary shadows require a color to be specified in the arbitrary value in order for shadow color utilities to properly replace the color. This was not the case in the v3 engine, and is definitely something we want to work in v4.

The fix is to append the color variable to the arbitrary shadow if no color can be parsed from the shadow value, instead of bailing if no color is found.

@adamwathan adamwathan merged commit 62de02a into next Jun 21, 2024
@adamwathan adamwathan deleted the optional-shadow-color branch June 21, 2024 21:37
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.

3 participants