The slow adoption of new CSS features

[@drewbird87]

Thanks for the nudge! I need check out container queries again. Theoretically, they’d shine in “components” - just need to take a step back and think through how it interacts with existing responsiveness.

[@Brendan2Alexander]

Good points. I stand convicted as one of those devs who often manhandles css just to get something done while my "real" work is with javascript or dotnet etc. Your channel really helps me to genuinely focus on the art and science of css. Because of you I DO use container queries.

[@PicSta]

I am a web developer over 20 years but had a few years of break now. I lost completely track of newer CSS features and play catch up at the moment. Most people have a specific workflow or way of thinking where container queries change, like everything in thinking of design structures. Like for 10 years you walk down the street on right side, now someone comes up say, please use left side instead. This is how it must feel for most people adopting it. Perhaps one day we all will use it as there come some benefits with it in the way we design things independently of device their width.

[@tanim_mahbub]

The people who are working on the adoption of new CSS features for browsers are the most important to do this in my opinion, if they implement the new features the people who try to adopt them will try harder. I have 2 incidents to tell you about. The first is about a few months ago, I applied border-radius, outline, and outline-offset to a set of buttons. They were working fine, except one day one of the team members told me that it was not working on the mobile browser, so I tried with an Android mobile browser Chrome, and he was right, it's not working. After a little bit of digging, I found out that border-radius doesn't work with outline in some browsers. So I changed the CSS and used border and box-shadow as a CSS-Trick for the design I wanted. The second incident is recent. I have done like 25% of a project using the new CSS nesting, and guess what, it got me again in mobile browsers. After checking a little bit and chatting with the ChatGPT I concluded that for now, it won't be wise to use the new CSS features except for practice purposes. I felt sooooo bad because the new features are so awesome.

[@markopizurica]

css grew so much in the last couple of years, so it's probably overwhelming for new designers. also, with so many new features people need to keep track on caniuse, people just opt to use near perfect adoption, and just wait for the community to announce that 'it's ok now!' it feels to me that wide adoption of flex and grid was just yesterday.. and look at as now! @container lol!!

[@hemantduttacodes]

People don't look for something new once they have something that works for them. People don't every day have the mentality that I will improve my workflow and techniques, not only CSS but in general; once they learn something that fulfills their needs, it is enough for them. They learn something new once they have a requirement that pushes them to do so.

[@CyberTechBits]

TBH CSS is so powerful nowadays you can do a lot without JS.... it's awesome 😎

[@techyjc]

Is there also the question of browser adoption for new CSS? Some browsers adopt faster than others. The time between initial release, adoption and full(ish) support probably means enthusiasm is curbed or sometimes the feature just slips off the list. With the exception of features that are progressive enhancements, which can be used early on. Just my thoughts.

[@killerwolle88]

I used container queries, they broke our modals. (Because it catches position: fixed, like relative catches absolute) So... Next project.

[@Tenaciousgolem939]

That stat is interesting, i'd say my current role id say im 80% html and css😅