3 ms·
If you want to use the normal non-& syntax, then you will need to use Safari 17.2, yes. I am referring to the fact that there are no browsers with native CSS n
by baggy_trough 2y ago
If you want to use the normal non-& syntax, then you will need to use Safari 17.2, yes.
I am referring to the fact that there are no browsers with native CSS nesting that support Windows < 10.
- JimDabell 2y ago> If you want to use the normal non-& syntax, then you will need to use Safari 17.2, yes. Non-& is not “the normal syntax”. It was a late addition to the specification. Both with and without & are normal, but with & has better compatibility. Even if you don’t use the &, you can still write nested CSS and support older versions of Safari, like I said. Use PostCSS or Lightning CSS. There are normally several areas where you can start writing modern CSS today and fill in the backwards compatibility with these tools. It’s not just nesting. https://preset-env.cssdb.org https://preset-env.cssdb.org https://lightningcss.dev/transpilation.html https://lightningcss.dev/transpilation.html
- baggy_trough 2y agoI guess we will have to disagree about what is normal or not. Perhaps it depends what tools one was using before going CSS native. Obviously I'm talking here about direct serving of CSS assets without precompiling.