Stylish for Firefox 2.0.0b4
Available here.
This version does not include any changes to the Stylish database, so you should be safe switching back and forth between it and 1.4.3.
Please provide your feedback and bug reports here or in GitHub.
This version does not include any changes to the Stylish database, so you should be safe switching back and forth between it and 1.4.3.
Please provide your feedback and bug reports here or in GitHub.
Changes from 2.0.0b3 to 2.0.0b4
- Disable Firefox's fast find when using source editor
- Added F3 as shortcut to search source editor
- Make disabled buttons look disabled in editor window
Changes from 2.0.0b2 to 2.0.0b3
- Network error downloading md5 no longer prevents style installation
- Fixed "Stack level too deep" when undoing a style delete
- Edit window now matches devtools light/dark theme option
- Combine the two edit window "toolbars" into one
- Saving new style with template code no longer keeps the code parameter on save
- Ctrl+S now works in Hungarian
- Preview now also checks for errors
- Updated Russian and Chinese (Taiwan) localizations.
Changes from 2.0.0b1 to 2.0.0b2
- Regexp matching site styles now show up in toolbar button when they match
- Edit window now reliably prompts only once when there are unsaved changes.
- Completed Czech and Chinese (Taiwan) localizations.
Changes from 1.4.3 to 2.0.0b1
New features
There's not as many new features as you may expect from a 2.0.0, but there's more than any version in a long time...- Electrolysis support. This will ensure Stylish remains compatible when Firefox makes the switch in the (near?) future. If you're going to test this, use a nightly and set browser.tabs.remote.autostart to true.
- Configure which styles show up in the toolbar button dropdown. Set the prefs under the branch extensions.stylish.buttonStylesDisplay:
- app - App styles
- global - Global styles
- siteMatching - Styles matching the current site
- siteNonMatching - Site styles not matching the current site
- show - show the styles directly in the dropdown
- submenu - group the styles in a submenu in the dropdown
- hide - don't show the styles in the dropdown
- Editor refresh. The editor now shows up in a tab (in supporting programs) with buttons along the top (that don't close the editor!). This allows for easier editing as well as a much larger code textbox. Programs that do not support tabs will open the editor in a new window. You can set extensions.stylish.editorWindowMode to 1 to force the new window mode.
- When a style from userstyles.org is uninstalled, users can report it as broken. This will feed into stats on userstyles.org to identify popular, but non-functional, styles.
- Faster loading of Add-ons Manager, especially when you have 100+ styles.
- Sort styles in toolbar button by name.
Bug fixes
- Various fixes for updating styles.
- Ctrl-S saves when code textbox is focused.
- Don't allow Undo to undo the initial value in editor.
- Stop showing partial regexp matches as styles for the current page.
- Prevent zombie styles when a style is disabled while its edit window is open.
- Prevent bad update URLs in a style from breaking all add-on updates.
- Fix Stylish in Pale Moon 25
- Fix padding of toolbar button on Windows
- Fix autocomplete in code editor.
Removed features
(This stuff is probably going to break Stylish-Custom and otherwise angry up the blood.)- Removed support for Firefox prior to 19.0 and the equivalent version in other programs. Electrolysis support necessitated this.
- Removed various compatibility fixes required for older programs as well as deprecated Gecko interfaces.
- Removed support for tags.
- Removed old pre-Firefox 4 XUL manage interface, as well as the ability to show it in the sidebar.
- Removed ability to switch to edit window when installing a style.
Comments
Removed ... the ability to show it in the sidebar
WHY?!?!?.....
What was wrong with it? This was the only way i used the ext. All styles sorted in groups by tags easily accessible from the sidebar on a click.
Sorry, can't say thanks for the update. I'm back to 1.4.3 and will stay there.
WHY?!?!?....
I can't breathe...
What is your reason for removing such vital features?
There was no upkeep at all with continuing them on through future versions was there?
● Set the prefs under the branch extensions.stylish.buttonStylesDisplay ?
Instead of a proper Options window like all other firefox addons?
● Stylish-Custom editor does not exist AT ALL. Completely gone. Non-existent. Wiped out.
● Click "write new style" and Editor will only open in tab and Errors do not show. I guess you have to continuously click the errors button to check...
but I clicked it and nothing happened.
● No Stylish-Custom standalone appears.
Sigh... Staying with 1.4.3 but I don't know how long that will be functional through future firefox updates.
Then what?
You can of course still use 1.4.3, or (bug someone to) reimplement these features. The backend hasn't changed, and the code history is in GitHub.
If you can add some function it shall be great and
help to forget the fact it Break S. Custom totally... :-( :
- Auto ! important
- Comment / Uncomment
- Insert text
- Undo / Redo
- line number
- go to line number
- Syntax highlighting
And with my quick test , i don't see who to open the editor in an independent windows..
"Shift ! enter" will autofill "!important;" also.
Can you add an option for that ?
set extensions.stylish.editorWindowMode to 1...
I read Make edit window open in a tab #193 :
But for everybody, an option (in Stylish) should be more easy, no?
and to switch on different way to use the editor too.
Bugreport: having simple style, eg
@-moz-document regexp(".*forum.*"){*{color:red!important;}}I am not able to toggle it from toolbar button menu, because it is not present in available nor global styles list.Update:
extensions.stylish.buttonStylesDisplay.siteNonMatchingset toshowmakes it appear, so it seems it is not that serious bug.So I think it would be much more practical if the Editor opens in a sidebar instead of a tab.
● In the sidebar, you will be able to see the immediate results of preview without having to switch tabs to see a delayed result of the preview.
● And the sidebar can slide open and close to as far as you want width wise... unlimited.
#sidebar
{ max-width: none !important; }
#sidebar-box
{ overflow-x: hidden !important; }
● When dropping Editor focus, you will not have the problem of the Editor disappearing to the taskbar, the way it does now with 1.4.3
● The sidebar could open on rightside so you will still be able to open Bookmarks/History etc on leftside simultaneously.
Or option to choose left/right for 'Editor Sidebar'.
▶ And so with this plan then you might as well bring back the sidebar for the manage styles !!!!!!!!!!!!!!!!!!!!!
MOCKUP
@Jason
Does that mean from this version onwards, user can only manage their style via the full page addon management? My understanding is pre-firefox 4 XUL interface refers to the small pop out window.
Yes I saw your reply to barbie. You mention cost was zero up to this point. Is the full page addon management taking minimum effort from you as you are using existing code from firefox?
If it isn't, and the effort to maintain either method of management interface, I hope you will reconsider your decision of having your effort go the path of addon management view. It is actually rather silly to manage your style on a separate tab.
Another issue you're talking about is the editor opening in tab or window, which you can still do:
"You can set extensions.stylish.editorWindowMode to 1 to force the new window mode"
Not being able to test styles before installing, or even, to edit before installing to me is a big no-no because it adds the inconvenience of committing to an install, when before the install process was commit-free if you didn't like what the style did. I do hope that when Stylish is out of beta, a preview routine that saves the style in a temporary SQLite file and opens it from there is integrated.
Expanding upon that, maybe a "Previewed styles" section could be made for people who are simply previewing a lot of stuff, which would only be available for the current browsing session.
I was almost to complain about a new tab being used for style writing, until I realized tabs can be moved to new windows. While mildly inconvenient, it is an ideal solution for people who wanted to use Tile Tabs and have the editor and page side-by-side, so opening up new use options is a positive, and the benefit outweighs the caveats.
The option to change code format colours would be nice to integrate, which would obsolete the need for any style directly affecting the Stylish interface.
Also, I saw no preview button in Pale Moon when installing styles from userstyles.org. I'll have to look again and see f I need to recant my prior concerns.
Some people make "Template" styles with clear directions on what to modify prior to installing. Since websites often change, I don't like creating pre-fab options and leaving people in the dark when a website decides to change their classes around. So instead of making options and forcing my audience to constantly re-specify their options and reinstall the style, the advice I generally give is "Remember your settings and re-apply them upon update."
On a further note about my personal decision to do that, I want people to be able to do some things themselves, because once people know how to do something in one style, they can apply it to a hundred more, and I like to push people using my content to expand their minds briefly, at least far enough to understand how to change a background image, or specify colours, or fonts, or what-not.
Thanks for the info myf ! :)
On the other hand, if you're asking them to change the code, whenever you update the style, they'll lose their customizations. I don't see how this is better in any way.
If you still wanted people to edit the code themselves, it seems like it'd be better to not have it update at all.
Also, a request; When I modify a website, I tend to separate things out if it means I can save a few lines or enhance the human-readable understanding of the code. Maybe for the 2.0.0 final release, an option to specify a series of line numbers with a color filter, paired with a a function to show only those lines in a document? style? It would make managing large swafts of code a little bit easier.
i tested this in 3 profiles. As soon as i install S2, whenever i try to close the editor (i have it set to open in window, don't know if it makes any difference) by clicking the window close button (since i don't see any other way to close it), i get this dialog popup:
Do you know anything about it? How do i get rid of this thing? For the record, i don't get it in my main profile where i use S143.
EDIT: just reset the editor in window and still get the dialog when i try to close the editor tab (happens when i don't save changes, just trying to close tab or window.
And, still no way to Find installed styles in the Manager. The Search box hits the network for new styles instead of hitting the kaboodle for installed styles. In fact it saves the stylesheet even when some other element is focused. If the URL bar is focused, though, it attempts to save the editor page itself; that's an error.
No new "Save as" or "Save a copy as", though. It's nice to be able to edit a style and still have the original, and also nice to have a copy that won't be updated and overwritten. (Sorry, I thought this was a stock function until I updated else I would have asked for it earlier.) So far so good, but once you're infested with zombies you can't ever be completely rid of them. Fait accompli, but this is a real nuisance because it isn't possible now to examine a broken style in response to a forum question without installing it and then uninstalling it. Installing it is a non-starter if you've already edited your local copy, because you'll overwrite your changes if you do, and uninstalling it is no fun if you've got to scan a list of 100+ styles for a new name. I don't think either of us wanted it to come to that. Anyway, they were less questions than statements of preference. (And now they're documentation.)