The Future of CSS
- ID
- 37822
- Status
- summarized
- Published
- 21 Oct 2026, 9:47 AM
- Fetched
- 21 Oct 2026, 6:28 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.joshwcomeau.com/css/interop-2027/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 7.0
- Created
- 21 Oct 2026, 6:28 PM
- Tags
- Audience
- developersvibe_coders
What happened
Josh W. Comeau lists his top 10 CSS features for Interop 2027, the cross-vendor effort involving Google, Apple, Microsoft, Mozilla, Igalia, and Bocoup, and notes Mozilla has opened a ranking system for developers to upvote requested features. His first pick is CSS functions using @function and result, supported in Chrome 155 and Edge 154 but not Firefox 157 or Safari 27 as of October 2026. He shows a --translate-polar example that converts an angle and distance into translate(calc(cos(...)), calc(sin(...))).
Why it matters
If you build web UI, treat @function as progressive enhancement today: it is usable in Chrome 155 and Edge 154, but you still need a plain-CSS fallback for Firefox 157 and Safari 27 rather than making it your baseline. If reusable CSS functions would simplify your design system, use Mozilla's Interop 2027 ranking to vote instead of assuming cross-browser support will arrive on its own.
Discussion angle
Which CSS feature would you upvote for Interop 2027, and how would you test @function in Chrome/Edge while keeping Firefox/Safari users working?