Hacker News new | past | comments | ask | show | jobs | submit login

And yet there is only one browser that 5 people always comment about saying "not working" when there's some kind of web thing posted on HN. Those tests don't seem to reflect reality.

I still recall a time 3 years ago when they didn't even have working webrtc support hah.




I still recall a time 3 years ago when they didn't even have working webrtc support hah.

That’s a long time ago in web years. Things are different now.

For example, Safari supports the oklch and oklab color spaces starting with Safari Technology Preview 137, released December 2021.

It’s November 2022 and Chrome still doesn’t support them yet, though they are expected to be enabled by default in Chrome 110, due next month.

And of course the most anticipated selector probably ever :has() shipped in Safari 15.4 back in March [1]; Chrome didn’t ship it until August and Firefox still doesn’t have enabled by default—it’s behind a flag due to bugs.

The oklab and oklch color spaces solve a bunch of color issues with RGB and HLS [2].

This is not WebKit from 3 years ago.

[1]: https://webkit.org/blog/13096/css-has-pseudo-class/

[2]: https://evilmartians.com/chronicles/oklch-in-css-why-quit-rg...


I decided to rebuild the OP post in Oklab just to see what would happen - https://observablehq.com/@mjbo/oklab-named-colors-wheel

Turned out pretty well


This is much more useful than RGB for telling which colors are overrepresented imo. Thanks for making/sharing this!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: