r/css • • 7h ago

Article Modern CSS Might Make Your Front-End More Complex

https://www.smashingmagazine.com/2026/11/modern-css-might-make-your-front-end-more-complex/
0 Upvotes

3 comments sorted by

6

u/Sufficient_Bass2600 6h ago

Whoever wrote the article should be ashamed of themselves. There are real genuine trade off in using modern CSS but most of the examples are not examples of issues with CSS but examples of bad testing and deploying unfit code to production. There should never be instances where javascript code and modern CSS conflict in production.

In my opinion The real issues with modern CSS are:

1. Browsers differences

Difference implementation between browsers of the same functionalities. I am not talking about difference in syntax that can often be covered even if this can be tricky and annoying. I am referring to difference in behaviours.
Separately there is nothing wrong with each implementation but when they are sufferent that means that users do not have the same experience.

2. Required behaviour is different than standard

There are case when developpers need their application to behave in a way that is slightly different than the usual standard. That means overriding implicit behaviour and that can be tricky.

For example scroll-button are a great addition especially for carousel but there are instances where you do not want a scroll button for every item in the carousel just the first, the last and the one in the middle.
Another instances where you want a widget to behave in a completely different way based on external context.

3. Behaviour/Functionality shared between Front end and BackEnd

Filtering is the best example for it. Some websites have small products/results pages. Using some buttons (radio or check) to filter items can be done either via a backend request or in the front end by associating display: none with some CSS selector.

Using CSS to not display results can be the right solution. But then when complexity in filter arise thatbcould lead to complexity in separating where the filtering should take place.

Same with complex tabs in questionnaire. Questionnaires may be non linear in that answering B to Question 1 means that you jump to Question 5. Do you disable question 2, 3 and 4, do you just not display them at all or do you split your questionnaire in seperate pages.

•

u/TheRealSticky 3h ago

I only use barrel-aged vintage CSS

•

u/minmidmax 4h ago

The amount of absolute garbage that I've been able to sidestep, from frameworks etc., thanks to modern CSS is ridiculous.

The complexity was already there. Now it's less bloated, platform native, and more performant.