Stylish 3.0.1 - 100% non-working add-on
It was my understanding that add-ons had to be approved by Mozilla before being published on addons.mozilla.org.
The popular add-on "Stylish" got a "WebExtension" upgrade to version 3.0.1 for Firefox 57 support. However, the add-on is completely 100% non working.
It's not just me, check the reviews and you'll see this is a problem. Also, try installing the extension yourself and loading a custom style. You will see that it does not work.
Additionally, the Stylish 3.0.1 update does not work with user's saved styles, and there is no warning when updating the add-on that all saved styles will be lost. The stylish.sqlite database is not deleted, so it still resides on the user's file system. Clicking on support links will bring up instructions to manually add back in all styles. But the instructions only show it working in Google Chrome. The issue is moot because the add-on simply does not work, at all, even if manually re-adding the styles back.
Is this really the user experience you want your users to have?
Please remove Stylish 3.0.1 from addons.mozilla.org. It is a completely 100% non working version that should never have been approved and published in the first place.
Eminye Imininingwane Yohlelo
- Shockwave Flash 27.0 r0
- Adobe Shockwave for Director Netscape plug-in, version 126.96.36.199
- The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
- Next Generation Java Plug-in 11.151.2 for Mozilla browsers
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- Adobe PDF Plug-In For Firefox and Netscape 11.0.04
- Version 0.9.9, copyright 1996-2009 The VideoLAN Teamhttp://www.videolan.org/
- iTunes Detector Plug-in
- Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
- DRM Netscape Network Object
- Npdsplay dll
- DRM Store Netscape Plugin
- I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 5.1; rv:32.0) Gecko/20100101 Firefox/32.0
Please contact the devs of stylish for support with their add-on.
Also, there is an alternative, Stylus
Developers have been contacted by me and multiple other people, but they leave version 3.0.1 up anyways. They don't seem to care. That is why I posted here.
I am aware of Stylus and it appears to be pretty much identical to the 3.0.1 update of Stylish, except for the fact that it actually works. :)
Since developers won't remove Stylish 3.0.1 version, Mozilla should "unapprove" the add-on as it behaves destructively. (Causes (recoverable) data loss, does not warn user, does not function as advertised or at all.) Surely that is not OK.
Fwiw, the same happened to me with GreaseMonkey. Luckily, you should be able to downgrade to a previous version of Firefox and install an older version of Stylish. At least, that made it work for me regarding GreaseMonkey.
In the meantime, I'm looking for a replacement for Firefox, because I'm getting tired of being broken after every update and having to fix it again.
Note that you can't use Stylish to modify the appearance of the Firefox user interface. A WebExtension can only modify website content displayed in a tab. If you want to modify the Firefox user interface then you need to place your code in the userChrome.css file and possibly use @import rules to load individual files each with there own style set.
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder
- create the chrome folder (lowercase) in the <xxxxxxxx>.default profile folder if this folder doesn't exist
- use a plain text editor (Windows: Notepad; Mac: Textedit) to create a (new) userChrome.css file in the chrome folder (file name is case sensitive)
- paste the code in the userChrome.css file in the editor window
- make sure that the userChrome.css file starts with the default @namespace line
- make sure that you select "All files" and not "Text files" when you save the file via "Save file as" in the text editor as userChrome.css.
otherwise Windows may add a hidden .txt file extension and you end up with a not working userChrome.css.txt file