3 ms·
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
by tkcranny 2y ago
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 motion preferences with better abstractions than media queries everywhere.
[1] https://drafts.csswg.org/css-mixins/ https://drafts.csswg.org/css-mixins/
- userbinator 2y agoAt this point the W3C is basically under control of Google anyway.
- charliesbot 2y agoNon sense. Read the reply: this is a feature that is coming to all major browsers
- userbinator 2y agocoming to all major browsers Chrome, Chrome, Chrome, and Chrome?
- lolinder 2y agoToo many on HN seem to forget that Safari exists and has a large market share. If you break Safari then no one on an iPhone or iPad can use your site. That's an unacceptable level of breakage for almost every site, and is enough to ensure that if Apple doesn't implement it it won't be used. Ironically, Apple's walled garden is the last thing standing between Google and total web dominance.
- rchaud 2y ago> If you break Safari then no one on an iPhone or iPad can use your site. A CSS issue is not going to break any site unless it causes interactive elements to overlap or be hidden from view. Most sites do not implement bleeding-edge features for this reason. Those that want to set it up will do it in such a way that there's a fallback for browsers that don't support that function.
- deleted 2y ago[deleted]