New version for Firefox
Hi everyone! If you're a Firefox user, this message is for you.
Please upgrade to the current version in the store (v2.1.1) as soon as possible. Upgrading to this version will save your currently installed themes and allow you to port them over to the newer version that we will be releasing, and that complies with the new Firefox extension guidelines.
Anyone that does not upgrade to v2.1.1 by Friday, November 10th will not have their installed themes in the following version (v3.0.0) to be released a few days later.
Thanks for your understanding and we hope you enjoy the new version :)
Please upgrade to the current version in the store (v2.1.1) as soon as possible. Upgrading to this version will save your currently installed themes and allow you to port them over to the newer version that we will be releasing, and that complies with the new Firefox extension guidelines.
Anyone that does not upgrade to v2.1.1 by Friday, November 10th will not have their installed themes in the following version (v3.0.0) to be released a few days later.
Thanks for your understanding and we hope you enjoy the new version :)
Comments
This is the first update to the Firefox version of Stylish since the new owner, Justin Hindman, took over development. Since that time, Justin Hindman also began working with SimilarWeb and added analytics data collection to the chrome extension.
Does this version 2.1.1 include any analytics systems that report back to the developer, SimilarWeb, or any other third parties?
The only significant change I noticed between 2.1.1 and 2.0.7 is code to migrate styles from the SQLite database to WebExtensions storage.
There are a bunch of locale folders for different languages that I didn't look into (I just looked at en-US).
I think all the big changes will be in the next release.
@Jefferson Thank you. That is very reassuring.
@undersky
Well, once I am forced to use a web-extension, I will probably switch to using Stylus anyway. If Stylus had a non-web-extension version, I would have already switched to that.
As I understand it, the 3.x branch is going to be the same as the Chrome version, tracking analytics and all. I have had auto-update off for a while as well.
Stylish 3.0.0 updated automatically today.
Broken!! ( Have gone back to 2.1.1)
If I click on the Stylish icon I get a notice and when I click on the "Click Here" at the bottom of it takes me to
.... https://userstyles.org/help/db_chrome .... nothing Firefox related there.
If I open add-ons and click on Stylish Options I get a blank box with no text at all.
If I click on the blank box "click here" at the bottom of the blank box it takes me here .... moz-extension://a46697d3-05b4-4c50-8367-86b79e86c883/migrate/index.html
Following instructions there I can copy a script but have nowhere to put it as there is no Manage All Styles page that I can find.
Of course, Stylish 3.0 is going to change significantly because WebExtensions-based add-ons cannot style the user interface, just web pages. For rules applying to the UI, you can create a userChrome.css file (a topic for another thread).
I will give this until Monday then I guess decide what to do then.
I do not work with installed styles from userstyles. I custom write my own. I generally don't like the ones that I've tried, and realized that my tastes were unique enough.
To clarify: I have used the "copy" button on all of my old scripts from the "migrate to new version" page. Despite that, only three scripts show up when I say "manage all styles".
I am using ESR firefox. I do not need to, nor plan to, upgrade to this newer, worser system that is little more than a reskinned chrome. I can buy a chromebook and have more functionality instead.
Reading this thread: Saying that the developers let us know that this would be coming is nonsense. I did not see anything, because no message came to users. Maybe a message and notice was here on the forums, but not everyone reads every forum on the web.
NB: I do not want to, nor plan on, upgrading to this new 3.0 version that will lose UI improvements. Sorry, but firefox's address bar (among other UI pieces) is too tiny unless made bigger. If this in-between version (2.11?) cannot, then how do I go back to the previous working version?
Here is a sample non-functioning script that I pretty much rely on to read anything on the web. Note that it applies to everything. It's job is simple: Use my font and font size. I'm sorry, but 10 pixel times/whatever is not readable for me.:
EDIT: Sorry, tabs do not display properly here. Maybe if I try code tags?
[code]
@namespace url(http://www.w3.org/1999/xhtml);
html, body
{
font-size: medium !important ;
font-family: normal !important ;
line-height: 1.33em !important ; /* Change 2011-12-28: FF 9 no longer does "normal" correct here */
/* margin: unset !important; */
}
input, textarea
, table tbody tr td
, p, td, tr, div, font, label, a
{
font-size: medium !important ;
line-height: inherit !important;
}
/* Notes on the above:
"medium" == browser specified default
"100%" == outer container size (usually CSS'd smaller)
16pt == a font size.
What that says: Default the page to my size, not the site's size; then, allow changes that I set to be kept.
Yes, it's odd. No, it's not perfect.
*/
.smalltext { /* Known to be used on an SMF site; seems "generic" enough. */
font-size: small !important ;
font-family: inherit !important ;
line-height: 1.33em !important ;
}
#bodyContent /* Wikipedia, also "generic" */
, .postbody /* Seen on some forums */
, .messageText /* also on some forums */
, .message /* ditto */
, .messageInfo
{
font-size: medium !important ;
font-family: inherit !important ;
line-height: 1.33em !important ;
}
.page, .pageWidth
{
/* margin: unset !important; */
}
body
{
/* padding-left: 5px; */
width: 100% !important;
}
body.div
{ /* Does not work, sadly. Still have things declaring 95%, etc. */
width: 100%!important;
}
.post
{
overflow: unset;
}
[/code]
Installed in my firefox now: Stylish 3.0.0.
I never saw the transition that was apparently released on the second.
And this announcement said that 3.0 would not be released until after the 10th.
... Time to restore my firefox profile from backup. Just no.
(Judging from the comments of others in the thread who somehow received 3.0 already, you may not want to rush it!)
Then it should do the data format conversion in preparation for 3.0.
----
Since you run ESR, you should stop updates for Stylish on 2.1.1. On the Add-ons page, click the More link for Stylish, scroll down, and disable auto-updates.
To open the Add-ons page, either:
* Ctrl+Shift+a (Mac: Command+Shift+a)
* "3-bar" menu button (or Tools menu) > Add-ons
* type or paste '''about:addons''' in the address bar and press Enter/Return
In the left column of the Add-ons page, click Extensions. Then find Stylish on the right side and click its "More" link for detailed information including the version number.
(1) To install an older version:
https://addons.mozilla.org/firefox/addon/stylish/versions/
(2) To block auto-updates:
Open the Add-ons page, either:
* Ctrl+Shift+a (Mac: Command+Shift+a)
* "3-bar" menu button (or Tools menu) > Add-ons
* type or paste '''about:addons''' in the address bar and press Enter/Return
In the left column of the Add-ons page, click Extensions. Then find Stylish on the right side and click its "More" link. Scroll down to the section on auto-updates and turn them off.
and the tooltip shows:
Any tips?
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
menupopup
{
max-height: 400px;
/* or any height you want */;
}
menupopup autorepeatbutton
{
display: none;
}
menupopup scrollbox
{
overflow-y: auto;
}
Thank you.
1. Should of waited to release the Web Extension version until Firefox 57 was on the release build.
2. Honestly should of created a new Stylish add-on and left the old one alone.
3. Seriously this looks like a straight copy of Stylus. The manage styles page is literally pixel for pixel the same for most of the page.
So if you want to continue to alter your Firefox UI revert back Stylish to 2.1.1 and do not let Firefox update past Firefox 56.
Mozilla is working on an experiment API so this altering of UI stuff is possible again but that will take them some time and not really any updates on it at the moment.
There are resources online about userChrome.css, and I've been working on another one. If anyone is curious: https://www.userchrome.org/