Comment by potato-peeler
3 hours ago
Security updates have nothing to do with level of support for css3 modules.
Much of the issues of layout were already solved more than 12 yrs back, ie when css3 became mainstream.
The issue is devs are unaware about different levels of css3 or just plain ignorant about it.
Are you aware about the different levels of css3? Are you even aware there are levels to css3? Why are these frameworks not listing them and simply saying that they comply with web standards? Which specific web standards do they comply?
Any new css3 feature should have a fallback if they say they comply to web standards, which these frameworks don’t add.
Basically you want to adopt latest w3c guideline but completely ignore wcag guidelines on accessibility - https://www.thewcag.com/principles/robust
Why should some population forced to suffer because of your ignorance. I am sorry if I am blunt, but your comment about polarising users is rude.
Which comes back to my main point, Devs are simply not educating themselves about the fundamentals of web design.
I think its fine to target compatability with 99.9% on people with updated devices and not some random old 2020 safafi build
To be fair on this particular point, talking about iOS Safari before version 14 isn't "some random old build". It depends on your own users, but I saw plenty of 6-year-old iPhone user agents in the web logs when dealing with a doctor's surgeries app.
Even though I provided a direct link to wcag principles and guidelines, you still are too lazy to read.