fire.Man wrote:CTR 1.4.3 / 1.4.4 b5
Linux Mint/KDE
tested with fresh, empty profile
just an FYI - whether i enable the movable window control buttons (min/max/close) or not, they are available in abut:customizing
the problem is when i drag the window controls to a tool bar and exit about:customizing, the buttons disappear and so they are not available - if i re-enter about:customizing, they reappear and can be dragged back into the tool box
i just moved to linux and am wanting to put the tab bar on top and get rid of the window title bar, which is easy enough, except i would prefer to have the window controls available
You have to enable the option "movable fullscreen window controls" to see them on toolbars in fullscreen mode (not in normal/maximized modes). They are always visible in "customizing" mode, so users can move them to the toolbar location they want them to be in fullscreen mode.
I thought it makes more sense being able to place them anywhere before entering fullscreen mode (and customizing mode while in fullscreen mode).
Ach3r0n wrote:...
1. I'm not talking about the corner case of replacing the Firefox brand icon on the about:config page, when you have selected to not display brand icons. That's just something I noticed when testing all the different options. Personally I like the new brand icon and also that you improved it by adding a background color to it.
I'm talking about hiding the favicon for about:addons and about:preferences pages, as I prefer these pages to just display the Firefox brand icon (+ orange Firefox text).
Currently it looks like this on my system:
http://i68.tinypic.com/2dak4lk.jpg
I can disable the Firefox brand icon, but then I get Favicon (+ orange Firefox text). You already explained that you will not remove the Firefox text on these pages, as it would be against Mozilla security policy.
2. I can live with that at the moment. I hope Firefox developers will improve these pages a bit. I don't visit the preferences pages that much.
3. I understand that you want some security checks on these input boxes, but is it not possible to add some checks to these boxes (maybe through background colors) and just not save any value outside the valid range.
1. It does not make any sense to hide the actual "favicon" about:addons page provides to display the brand icon. Thats not what the favicon option is for. This behavior won't be changed.
2. Default about:preferences in content/tab was made of mobile devices and looked ugly right from the beginning. I doubt any Moz dev will spent a few minutes on css tweaking to improve it, but you can do a request on Bugzilla for that, if you have hope.
3. Yes, it is possible, but not needed. Its not like anybody has to change those values a couple of times a day. If you really need to enter whatever you want, use about:config for this:
Height: extensions.classicthemerestorer.aboutprefswh
Width: extensions.classicthemerestorer.aboutprefsww
jputting wrote:Hi,
I have just read in numerous places on the internet that Mozilla's Firefox developers have announced plans to completely strip out all Firefox Themes at some unknown time in the future.
This is a part of As part of Mozilla's "Go Faster" initiative for Firefox, the company is removing features that aren't used by many and require a lot of technical effort to continually improve.
The first two features to get the axe are tab groups and complete themes which change the whole Firefox UI.
Classic Theme Restorer is of course is used to get rid of the Chrome clone style UI which I and many others simply don't like.
The question is will we still be able to use Classic Theme Restorer to restore the classic Firefox UI.
I certainly hope that this is the case as I don't wish to abandon Firefox and move to an alternative browser.
As long as XUL is supported by Firefox, CTR should work fine. Once they move to the new engine (and remove xul), CTR won't work anymore.
Virtual_ManPL wrote:Aris wrote:Thanks for reporting. This will be fixed on next beta.
Thank you very much for instant fix.
No problem. The Bugzilla link in your post pointed to the solution, so there was not much to research.