Skip to content

fix: parsing custom declarations with auto values#80

Merged
marklawlor merged 1 commit into
mainfrom
08-15-fix_parsing_custom_declarations_with_auto_values
Aug 15, 2025
Merged

fix: parsing custom declarations with auto values#80
marklawlor merged 1 commit into
mainfrom
08-15-fix_parsing_custom_declarations_with_auto_values

Conversation

@marklawlor

Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@marklawlor marklawlor merged commit b491572 into main Aug 15, 2025
6 of 7 checks passed

Copy link
Copy Markdown
Contributor Author

Merge activity

@marklawlor marklawlor deleted the 08-15-fix_parsing_custom_declarations_with_auto_values branch August 15, 2025 02:52
danstepanov pushed a commit to sarathfrancis90/react-native-css that referenced this pull request Jun 20, 2026
color-mix() resolved at compile time by lightningcss can yield NaN
chromaticity channels for degenerate mixes (e.g. mixing black with
transparent in oklab). Passing NaN to colorjs.io produced an invalid
color string like "#NaNNaNNaN80" that React Native silently discards,
so utilities such as Tailwind's bg-black/50 rendered with no background.

Treat NaN channels as 0 (a missing component per CSS Color 4) for the
lab/lch/oklab/oklch cases, so the example resolves to nativewind#80.

Fixes nativewind#317
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.

1 participant