CSS Custom Functions are coming

Post by nemomarx » Mon, Mar 03, 2025, 2:36 AM UTC

IncreasePosts wrote: post #45

userbinator wrote: post #44

This is exactly the sort of propaganda which encourages making sites that don't work in any browser but Google's. If web developers would just focus on making simple and widely-accessible sites instead of churnful trendchasing, the browser monopoly wouldn't exist. Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. Exactly.

Either it will be popular enough that other browsers will implement the open standard, or it will not be popular and no one will implement it in other browsers and few sites will use it. Mozilla has a revenue of like $600M. They should have no problem keeping up with popular w3c standards. Hell, even opera, with only a tiny fraction of users can keep up.

Post by [deleted] » Mon, Mar 03, 2025, 3:10 AM UTC

sureIy wrote: post #33

andirk wrote: post #4

Thanks. Looks hideous. @function --light-dark(--light, --dark) { result: var(--light); @media (prefers-color-scheme: dark) { result: var(--dark); } }

Looks decent to me, I understand they have to stay within the normal look of CSS. That function, other than nesting, could every well be parsed by a 20-year-old parser.

Post by userbinator » Mon, Mar 03, 2025, 3:20 AM UTC

tkcranny wrote: post #47

userbinator wrote: post #44

This is exactly the sort of propaganda which encourages making sites that don't work in any browser but Google's. If web developers would just focus on making simple and widely-accessible sites instead of churnful trendchasing, the browser monopoly wouldn't exist. Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google. Exactly.

I agree Google has too much market share and sway over plenty of browser features. However… CSS features are a W3C specification and are an early stage [1]. It’s a process that vendors draft and agree on and can terminate. On top of that I wouldn’t characterise improving css with functions isn’t a _churnful trendchasing_. If anything this will improve accessibility because it’ll be easier to manage size, colour, and…

Post by userbinator » Mon, Mar 03, 2025, 3:27 AM UTC

charliesbot wrote: post #56

userbinator wrote: post #55

Earlier quoted context omitted.

At this point the W3C is basically under control of Google anyway.

Non sense. Read the reply: this is a feature that is coming to all major browsers

Post by namuol » Mon, Mar 03, 2025, 5:41 AM UTC

klabb3 wrote: post #43

namuol wrote: post #17

This is it. This is all I’ve wanted in CSS for the last decade. In fact, I just wanted basic mixins without function-like behavior, but this gets me there. The comments here indicate that the article doesn’t do much to explain what this does or why you’d want it, but basically this gives you a way to reuse blocks of styles without needing to resort to e.g. utility classes or other hacks that get around specificity is…

Can you expand with some examples of pressing use cases? To me, great complexity should bring even greater utility. I have no use for this, and I’m not sure who it’s for. Can we get rid of tailwind? Polyfills? Any UI libs?