Use initial
for @property
fallbacks instead of
#13949
Merged
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.
This PR updates the way we generate
for properties that are defined with no initial value:
@property
fallbacks for Firefox to useinitial
instead ofBefore:
After:
This is necessary because we have code in our CSS that depends on variables like
--tw-gradient-via-stops
resolving to an invalid value to trigger a fallback:If
, then
instead of falling back to the fallback value, which prevents 2-stop gradients from working in Firefox at the moment.
--tw-gradient-via-stops
resolves to--tw-gradient-stops
will also resolve toFixes #13948.