(The comment there that removing this "is going to help increase speed significantly in the future" is pure BS. If anything, user stylesheet functionality was handled in native code --- just adding another CSS to the page --- which makes it far more efficient than going through the whole JS/extensions route.)
Ironically, IE11 is the last MS browser to support user stylesheets (Tools->Options->Accessibility) but Edge doesn't.
Even in Firefox, the fact that it's named "toolkit.legacyUserProfileCustomizations.stylesheets" is ominous.
The Internet is becoming more and more user-hostile, and it's not just websites who are responsible.
>The Internet is becoming more and more user-hostile, and it's not just websites who are responsible.
That's because the webbrowser has been pushed away from hyperlinked documents viewer, to essentially a virtual machine running untrusted code from anywhere.
It's probably Googles fault somehow. They seem determined to ruin everything.
Issue asking for reintroducing native user style sheets in Chrome, with precise argumentation and long discussion. Does not seem likely to be heard, but symbolical starring doesn't hurt…
Reminds me of those times when I built a website that doesn't have a functioning mobile view, put it on reddit, and it turns out that everybody is mobile
You could probably make a bookmarklet to pull the stylesheet from github and add it to the document stylesheets. Maybe using the new Stylesheet constructor?
Heres a fun Firefox fact. Firefox handles audio/media files differently than chrome. Since it has a small market share, it becomes a rather annoying lose-lose: either spend a bunch of time to support Firefox for the ~20 people that will access your site using Firefox, or you don't support Firefox.
It's a shame that laziness is more important than interoperability. Part of the life of frontend or webdev is dealing with compatilibity issues, and it has been that way since forever. If you got into this biz thinking you could do that work and avoid those problems you thought wrong.
Laziness? Don't you mean unpractical and financially unviable? If I support Firefox do I support Edge, Opera, Android Webview, UC Browser? Explain how pragmatic prioritization can constitute as laziness.