Going CSS only pushes all executed logic to the rendering engine of the client/browser. It's an exercise in minimalism, it pushes the boundaries of what can be done and it encourages webdevs to get familiar with the newest available features of CSS (Which these days is quite a challenge, as everyone who's been around since the dawn of the web can attest).
All that is fun and a good thing.
No need to lugg around JS logic for mere UI stuff if that is available with the means of the visual composer/renderer. Advanced SVG features such as transformations and animations are good for such things as well. If your requirements only go back as far as Blink, Quantum and Safari from 3-4 years ago, you can do 95%+ of modern fancy GUI stuff without a single line of JS.
That's the challenging and fun thing about attempting "HTML/CSS/SVG only".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, that's easy to answer:
Going CSS only pushes all executed logic to the rendering engine of the client/browser. It's an exercise in minimalism, it pushes the boundaries of what can be done and it encourages webdevs to get familiar with the newest available features of CSS (Which these days is quite a challenge, as everyone who's been around since the dawn of the web can attest).
All that is fun and a good thing.
No need to lugg around JS logic for mere UI stuff if that is available with the means of the visual composer/renderer. Advanced SVG features such as transformations and animations are good for such things as well. If your requirements only go back as far as Blink, Quantum and Safari from 3-4 years ago, you can do 95%+ of modern fancy GUI stuff without a single line of JS.
That's the challenging and fun thing about attempting "HTML/CSS/SVG only".