It comes down to chrome not supporting various css styles per site [1]. Other browsers have a menu option to load alternative styles if a site provides them.

[1] https://www.thesitewizard.com/css/switch-alternate-css-style...

sorry, what? you can just include the <style> on the server side, where you render the page. Or do what I did, <style media="none"> and turn it on with a js click, store the value in cookie/localstorage for which <style> needs to be on.

I also don't really understand how this connects to the topic.

That creates the same functionality for one page but leaves the end-user unaware of the general duality of content and style. Choosing a style from a browser menu is not perfect but it is a hint for the end-user to see that each and every page can be rendered differently quite easily. Without that knowledge, end-users take the given layout as an unchangeable necessity and don't expect several styles for their blogging system or a page without a nag bar.

Ah. I wasn't referring to end user choices, I was talking about publisher design choices.

Medium.com is a platform, where your control is negligable. Earlier hosts, such as blogger, allowed you to theme your blog, you magazine, just like a completely owned site would.

My comment has nothing to do with end user, or in-browser themeing.

We can only hope it goes the same way as posterous did.

Pepperidge farm remembers

Please put more substance in your comments.