News for hackers. Stuff that matters.
Re:The Future of CSS by crocone on Wednesday October 21, 2026 @05:21AM (#50177989)
How niche would a website have to be to target the less than 1% of users who have disabled JS?
Re:The Future of CSS by thisislife2 on Wednesday October 21, 2026 @08:29AM (#50179789)
OP is saying disabling javascript may no longer work as desired if CSS is enhanced with JS features ...
Re:The Future of CSS by afavour on Wednesday October 21, 2026 @08:56AM (#50180127)
But it isn’t? The functions discussed in the article are not connected to JS at all.
Re:The Future of CSS by Izkata on Wednesday October 21, 2026 @12:59PM (#50184155)
As someone mentioned above, it probably would have been better if they weren't called functions. Macros, maybe.

Also the blog really doesn't help by describing it like this:

> If you’re familiar with JavaScript, this should feel pretty familiar. We define new functions with @function and specify the returned value with result.

Re:The Future of CSS by kdkwmdowmxks on Wednesday October 21, 2026 @02:37PM (#50185530)
So this is a semantics complaint? Man, developers are so anal about everything.
Re:The Future of CSS by zahlman on Wednesday October 21, 2026 @11:22AM (#50182552)
Almost every blog posted here qualifies, for example. For that matter, Substack still works fine that way, as long as you can deal with (one way or another) a white-on-red stripe banner at the bottom of a black-on-white page.