DEV Community

Cover image for Some new features CSS in 2024

Some new features CSS in 2024

Sonay Kara on October 26, 2024

In this article we will explore some new CSS features in 2024. If you like my articles, you can buy me a coffee :) 1. CSS container quer...
Collapse
 
grahamthedev profile image
GrahamTheDev

Careful with the conclusion part!

While this is a great list, it is worth noting:

  • Container queries only have 90% browser usage support, so you need a polyfill or fallback styling
  • CSS nesting only has 87% browser usage support and is hard to polyfill without causing Cumulative Layout Shift (CLS).
  • :scope is not supported at all in Firefox.
  • color-contrast is not supported at all in any browser and is purely experimental.
  • anchor postioning - has only very recent chromium support (66% of browser usage), so you would need to heavily polyfill / have strong fall-backs.

So in reality, out of the list you gave, container queries are the only one that is "safe" to use at the moment, depending on how far back you want to support browsers!

Collapse
 
aloisseckar profile image
Alois Sečkár

When talkink about any "new" features of web technologies, one has to be aware of possible lack of support in certain browsers.

A dedicated website caniuse.com/ is here to save the day providing detailed info about browser adoption of most if not all of them. If anyone doesn't know it yet, bookmark it asap!

Collapse
 
whereisthebug profile image
@whereisthebug

This is a fantastic point. And this is common with new features in CSS or JavaScript. It's fine to play with them in your personal projects, but you must pay a lot of attention to browser support before using them in production.

Collapse
 
sonaykara profile image
Sonay Kara

Yes, I’m aware of the current support limitations. However, it’s worth noting that when Flexbox and Grid first came out, they faced similar browser support challenges, yet over time they became well-supported

Collapse
 
grahamthedev profile image
GrahamTheDev

absolutely! And I encourage people to play with things and put them in side projects, just wanted to point out they were not really "production ready" yet.

Thread Thread
 
sonaykara profile image
Sonay Kara

Thank you for your feedback. I respect every comment, every information and opinion made on my articles in this community. Your comment is very valuable to me

Collapse
 
tymzap profile image
Tymek Zapała

Workaround would be to install PostCSS and respective plugins which will transform modern CSS to output understandable to older browsers. Once the browser support of these features is acceptable, you just remove the PostCSS plugins from your build step without modyfing the code at all.

Collapse
 
sonaykara profile image
Sonay Kara

Thank you , it seems logical to easily provide legacy browser support with PostCSS and related plugins.

Collapse
 
mince profile image
Mince

This is true

Collapse
 
itsmeseb profile image
sebkolind | ⛺ Tent.js

Thanks for clarifying this! It’s important to check the browser support on any features you use.

Collapse
 
mince profile image
Mince

Most of these are beta features

Collapse
 
sonaykara profile image
Sonay Kara

Yes, I already said it is.

Collapse
 
mince profile image
Mince

Yes you did 😅

Thread Thread
 
mince profile image
Mince

But I personally love beta features

Collapse
 
johndotowl profile image
JohnDotOwl • Edited

Sometimes i wish everyone just put their effort into 1 package , tailwind css, utility based

Collapse
 
sonaykara profile image
Sonay Kara

You may be right, but a CSS framework contains CSS codes. To use a framework effectively, you need to understand css, so you have to learn css.

Collapse
 
jessica_kotei_1811 profile image
Jessica Kotei

Love it

Collapse
 
sonaykara profile image
Sonay Kara

:)

Collapse
 
jessica_kotei_1811 profile image
Jessica Kotei

I want you to teach me

Thread Thread
 
sonaykara profile image
Sonay Kara

You can ask whatever you want by commenting on the article or sending an e-mail
zonaykara@gmail.com