-
Notifications
You must be signed in to change notification settings - Fork 36
[Customizing mode][Firefox/Waterfox 56] How to add spaces and separators? #383
Comments
Waterfox 56 and Firefox 56 do not support spaces, flexible spaces and separators anymore. |
Thanks for letting me know Aris. It's a real shame then that the Waterfox developer decided to base it on FF56 because not having the option to add separators in between toolbar buttons means that they're all cluttered up together. |
@Telmesomething commented on 2017. dec. 3. 10:11 CET:
There's a workaround. Add them via their context menu, then you can move them. |
WorkaroundWhilst customising, use the contextual menu. This screenshot was taken after adding a flexible space, divider and space: PostscriptSorry for the duplication. #383 (comment) above was not shown until after I had posted this comment. (Waterfox, like Firefox, suffers terribly from stale representations of content with sites such as GitHub.) |
Magic! Just what the doctor ordered. Thanks very much mzso. Many thanks also to grahamperrin for the screenshot. |
I think we can keep this open so others can find this workaround too. |
Just as well as it turns out. After adding spaces between toolbar buttons and then closing the Customization menu I noticed I'd missed one between two buttons. On reopening the Customize menu all the separators had disappeared. However, after exiting Waterfox and restarting it again, they reappeared. So just a minor anomally. |
@Telmesomething commented on 2017. dec. 25. 11:15 CET:
Yes. This his how it works on v56... You only have the separators the first time. After you switch tabs and back or close/open the customize tab the separators are gone for that session... |
Firefox runs a code to remove those items once in customizing mode. We are lucky it fails the first time. A shame Waterfox team incorporated this into their browser as they are eager to keep Firefox' rubbish code out of their project. |
@Aris-t2 commented on 2017. dec. 25. 13:07 CET:
Judging by the answers of the WF dev it might be done in a future update. |
No need to be concerned about the post I made here yesterday Aris. It turned out to be a config setting namely I managed to find it after creating a new profile and then restarting it every time I made a change either by adding an extension or making a config change. |
@jemonaff commented on 2018. ápr. 17. 12:35 CEST:
All of this was discussed before, and it doesn't actually work completely. You can only use the context menu to add them. |
Hopefully this gets fixed, as it was very frustrating to deal with and wasted a lot of my time figuring it out, but the workaround described here was very helpful, so thank you! I didn't realize at first what was meant by it and thought the items had to be added in order, that it was an issue of not being able to move the spaces around. So I removed all my items then started re-adding them with spaces, and at that point I realized what was meant. Edit: Also, another issue I've encountered is that adding certain items to toolbars (adding dual icon bookmark button with star and list icons to bookmarks toolbar and downthemall buttons to status bar/addon toolbar) makes the toolbars get much larger (their height increases). It fixes itself with a restart of the browser. I was going to add it as an issue, but it seems somewhat related to this issue, and I'm not sure if it's CTR-specific or not. |
@vertigo220 The icon issue might be related to a general icon problem, when internal icons or add-on icons switched to svg images or large images in general. This is another issue and I'm not sure, if there is real need to look into it, if a browser restart fixes the problem. |
@Aris-t2 I would agree it's not a high-priority since a restart fixes it, but I wasted a fair amount of time trying to figure out how to fix it before realizing that, and fixing the problem would avoid others having to deal with that as well. Anyways, hopefully by me mentioning it someone else will figure it out a little easier, and it might be useful to know if others have the issue without CTR or in other setups. I've added both the issues to my list of things to report. |
Could you open a new bug for this and run some tests to ensure this issue can be reproduced step by step? Use Firefox 56 portable or Waterfox 56 portable (creating a new browser profile), install CTR, install one of the affected add-ons and test, if the issue still occurs in that environment. |
Well, I just tried with a fresh install and couldn't reproduce it. Not sure if it was a conflict with another addon or just some really obscure fluke bug or what, but since it doesn't seem to be readily reproducible and since it's fixed with a browser restart, and it hasn't recurred since, I'd say it's not worth worrying about. If someone else comes along with the same issue, maybe they can provide more info that can help narrow it down, but if nothing else hopefully this will help them figure out to restart their browser without spending as much time as I did trying to figure out other solutions. |
Do you mean, the disappearance (from available buttons) after first use of Customise? |
Fully transparent would make them invisible, but if that is what you are looking for, replace the "red" with "transparent": #main-window:not([customizing]) #nav-bar toolbarspring {
-moz-appearance: unset !important;
min-width: 0px !important;
max-width: 0px !important;
border-right: 1px solid red !important;
-moz-margin-start: 5px !important;
-moz-margin-end: 5px !important;
} |
Thank you! You are a magician! |
Workaround (a complementary legacy extension) Puzzle Bars
In the Classic Add-ons Archive:
|
After installing CTR in Waterfox 56, I'm unable to add spaces between the buttons on the toolbar. Dragging a space from the Customize menu takes it up there, but is doesn't remain in place. Same goes for flexible spaces.
In the top half of the attached screenshot a space has been dragged to the spot indicated by the red arrow, but after releasing the mouse button, the space has been removed and has reappeared in the Customize panel.
Here's what it looks like after closing the Customize menu.
The text was updated successfully, but these errors were encountered: