3 ms·
Read my other comment in this thread, the stylish file has a bad domain restriction, enclose everything after it in a set of braces ({}), and it's fine.
by mhd 13y ago
Read my other comment in this thread, the stylish file has a bad domain restriction, enclose everything after it in a set of braces ({}), and it's fine.
- oneeyedpigeon 13y agoStill didn't work for me in Chrome. I wasn't sure how that conflicted with the 'applies to' config setting in the UI, and I tried various combinations before giving up. A shame, but it seems that Stylish just isn't production-ready.
- mhd 13y agoStylish does very little (and you don't need it at all in Chrome), if there's anything wrong with the matching/styling, that's a fault of the userstyle/userscript, which have been around since, well, forever. The chrome extensions pointed to by the OP link has a long list of domains it matches against in its manifest.json file. Looks alright to me.
- johnchristopher 13y agoThanks, maybe I'll try later. Note: I have to ask myself why stylish seems to allow modification of firefox's chrome. I have lost touch with the state of things in firefox extensions but I don't remember it being promoted as a skinning extension.