Only somewhat related and unfortunately misses the point.
CSS Zen Garden was powered by style sheets as they were designed to be used. Want to offer a different look? Write an alternative style sheet. This site doesn't do that. It compiles everything to a big CSS blob and then uses JS (which for some reason is also compiled to a blob, despite consisting of a grand total of 325 SLOC before being fed into bundler) to insert/remove stuff from the page and fiddle with a "data-theme" attribute on the html element.
Kind of a bummer since clicking through to the author's Mastodon profile shows a bunch of love for stuff like a talk about "Un-Sass'ing my CSS" and people advocating others "remove JS by pointing them to a modern CSS solution". (For comparison: Firefox's page style switcher and the DOM APIs it depends on[1] are older than Firefox itself. The spec[1] was made a recommendation in November 2000.)
Even ignoring your hyperbolic (i.e. wrong) use of "has to", the options are not "use tooling that produces crummy bundles, or else don't go to Paris"; the Paris that we're talking about definitely has more than one way to get there.
Me too. I do use it. It is very useful when you redesign a site and want to compare them. Just switch between themes and you instantly see if something is pixel-perfectly at the same spot.
I think it should be "sticky" the same way non-submitted form content stays persistent across page-reloads.
This kind of features should be what browsers are judged and compared on.
CSS Zen Garden was powered by style sheets as they were designed to be used. Want to offer a different look? Write an alternative style sheet. This site doesn't do that. It compiles everything to a big CSS blob and then uses JS (which for some reason is also compiled to a blob, despite consisting of a grand total of 325 SLOC before being fed into bundler) to insert/remove stuff from the page and fiddle with a "data-theme" attribute on the html element.
Kind of a bummer since clicking through to the author's Mastodon profile shows a bunch of love for stuff like a talk about "Un-Sass'ing my CSS" and people advocating others "remove JS by pointing them to a modern CSS solution". (For comparison: Firefox's page style switcher and the DOM APIs it depends on[1] are older than Firefox itself. The spec[1] was made a recommendation in November 2000.)
1. <https://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-87355129>)