Is it time for "CSS: The Good Parts" ?
CSS Custom Functions are coming
61–70 of 90 posts
Re: CSS Custom Functions are coming
#62Oh man, and I thought the current JS status-quo was already full of vulnerabilities and privacy risks. If I had mind-boggling amounts of money, one of the things I would do is start an organization to name and shame and give anti-awards to websites that most abuse javascript and whatever-this-will-be. Or a dang mutual fund: "Like an index fund except we don't support companies with websites that require a ridiculous…
Okay you had your FUD, now for the just desserts: This is actually a feature that is likely to reduce the amount of JS that needs to run on the web. It allows for common component-oriented styling patterns to be employed without bloating CSS bundles or using runtime CSS-in-JS functionality to accomplish it. Source: I work on a web development platform (booo, hisss)
Re: CSS Custom Functions are coming
#63This feels like a really bad idea, I hope it doesn't make it into the browser. CSS Houdini would be a better path to take.
These are not mutually exclusive proposals. Houdini provides a way to extend e.g. CSS with arbitrary JS. This is merely a new abstraction for code-reuse in CSS. It’s inspired by the same concept from Sass, but doesn’t need to be compiled and thus won’t bloat your CSS bundle.
Re: CSS Custom Functions are coming
#64Earlier quoted context omitted.
It’s just a new addition and change, doesn’t dictate you must write that way. I still use as a tag (I know, HTML).
It's not about how they write CSS, it's about how everyone else does, and what browsers will need to be able to process. I don't know how you figured their complaint is somehow compat breakage. From what I know, CSS doesn't really have breaking changes.
It absolutely has breaking changes! But most developers will never notice. I work on a complex browser based web development platform and we’ve had certain specs change under our feet leading to incidents that required us to disable features until major browser vendors reverted things. I do not envy spec authors. Huge respect for their patience.
Re: CSS Custom Functions are coming
#65functions in stylesheets? That's nuts. The web is developing in the wrong way.
CSS preprocessors like Sass have had functions for, like, ever.
Re: CSS Custom Functions are coming
#66Thanks. Looks hideous. @function --light-dark(--light, --dark) { result: var(--light); @media (prefers-color-scheme: dark) { result: var(--dark); } }
makes my eyes hurt
Re: CSS Custom Functions are coming
#67Why do we allow Google to singlehandedly keep pumping garbage into the web ecosystem? Do they own W3C?
While I think this particular idea is bad, Google is following the W3C process for proposing new features. This is what browser vendors are supposed to do: develop the feature, document it so other vendors can implement/compete it, see if there's enough early-adopter developer interest to bother standardizing.
Are there any examples of the W3C refusing a submission from Google?
Re: CSS Custom Functions are coming
#68I wish we'd just admit we're heading for SASS and use that. It'd save a lot of hand-wringing and time spent justifying adding each feature.
Re: CSS Custom Functions are coming
#69Re: CSS Custom Functions are coming
#70Earlier quoted context omitted.
While I think this particular idea is bad, Google is following the W3C process for proposing new features. This is what browser vendors are supposed to do: develop the feature, document it so other vendors can implement/compete it, see if there's enough early-adopter developer interest to bother standardizing.
Are there any examples of the W3C refusing a submission from Google?
... no, you're still not understanding the nature of the W3C.
The W3C is descriptive, not prescriptive. It doesn't have any regulatory power, so it can't make design decisions or value judgements of any kind. It isn't even a separate group from the browser vendors; while individuals may join, the vast majority of active members are the developers working on the browsers.
The teeth come from the other browser vendors. They make pledges to each other to implement each other's features. They collaborate through the W3C to come to a consensus on feature designs, because a feature can't get standardized if it's not implemented by more than one vendor and it won't get implemented if the vendors can't come to a consensus.
Anything the W3C says is not how browsers should work, it's how they already work.