You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
I’m not opposed to that. Though HCT off the bat hasn’t performed clearly better than OKLAB/OKLCH (not to mention OKLAB/OKLCH support has landed in all modern browsers but the path to HCT adoption is unclear), it’s still new enough that in time there may be a clearer use for when it shines better than OKLAB/OKLCH.
And as an aside, I’m actually second-guessing the future of this library now that OKLAB/OKLCH adoption has reached all major browsers and is widely available in CSS—perhaps this should just be the bare-minimum JS implementation? In which case supporting similar formats like HCT may also fit, especially for users like yourself that are using Material Design but don’t want the massive overhead of culori, color.js, etc at runtime.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can we support HCT in Google Material design 3?
See:
The text was updated successfully, but these errors were encountered: