When is the Navigation bar problem going to get fixed?
We used to be able to toggle the navigation bar on and off with Ctrl-L. New, "improved" versions made it difficult so a plug-in was created to "hide" the navigation bar but it didn't work consistently and newer versions of FF disabled it. I am holding off updating until this problem get fixed
Gekose oplossing
I am now running 52 ESR. That was the smoothest transition ever. My ver 24, by the way, was also ESR. The tabs are now fully legible, the nav bar is gone though very awkward to retrieve, and other add-ons are once again available.
I did not fine ver 57 to be faster, in fact it seemed a bit slower. I have learned over the years to be hesitant to install "upgrades" because they always, always, always, create new bugs without fixing the old bugs. Why a programmer would consider making tabs less legible to be an "upgrade" is beyond me. I am still hopeful that someday the navigation bar control will be returned to its Ctrl-L (or file menu, "L") ease. The install program still has windows (dialogues?) that appeal all white for me. Thank you guys for really outstanding help. I am now up to ver 52 but will keep auto updates turned off until there is a sign that the nav bar problem and ability to configure FF has improved. I will try to attach some screen shots to show what I talked about above.
Oh well, I can only copy screen shots to a .doc file and this system only allows me to upload .jpg. Sorry.
Lees dié antwoord in konteks 👍 0All Replies (17)
In case it helps to download a file. You'll need to shorten the name to userChrome.css after moving it into the chrome folder. If you can't see the .css extension, set Windows to show all extensions.
- https://www.userchrome.org/samples/userChrome-hide_navbar.css
- https://www.bleepingcomputer.com/tutorials/how-to-show-file-extensions-in-windows/
priopel said
I found the following website with a suggestion for eliminating the "fading": https://support.mozilla.org/en-US/questions/1163524
Hopefully that will work.
it says that the userChrome.css file has to start with an @namespace command.
I disagree: https://www.userchrome.org/adding-style-recipes-userchrome-css.html#namespaces
The problem seems to be that userChrome.css is showing in the user profile but not in the toolbox.
priopel said
The problem seems to be that userChrome.css is showing in the user profile but not in the toolbox.
If it doesn't appear in the Browser Toolbox, it sounds as though Firefox is not reading it. Of course, you can tell that from looking at your navigation toolbar.
I'm leaving the keyboard now.
The file list in the toolbox is rather long and not sorted, so it is easy to miss it. Note that userChrome.css needs to be in the chrome folder for it to work.
The userChrome.css appears in the profile folder in the chrome directory but not in the toolbox. But that paths are so different that I don't know why it would appear in both places.
I may revert to ver 56 so I can use classic theme restorer.
Okay.
For future reference: "chrome://" is an internal address within Firefox, and "browser.xul" refers to the user interface, not to a folder on disk.
I notice that userChrome.css in my profile is listed as a text file. Is this correct?
priopel said
I notice that userChrome.css in my profile is listed as a text file. Is this correct?
It should say either CSS File or Cascading Style Sheet. You may need to set Windows to show file extensions and remove a .txt from the end of the file name: https://www.bleepingcomputer.com/tutorials/how-to-show-file-extensions-in-windows/
Aha. I used a different approach (This PC) but got the file extensions turned on and discovered that userChrome.css in my profile had been saved as userChrome.css.txt. I deleted the ".txt" and I now have userChrome.css showing in the toolbox. Unfortunately, this made no difference at all to the navigation bar. What about that namespace command? The web page https://support.mozilla.org/en-US/questions/1163524 says that a userChrome.css file has to start with a namespace command.
You can add a namespace if you like; it can't hurt, right?
If you paste the rule from the other thread, does that one work?
I am thinking that if I go back to ver 56 that plug-ins will work again and I can at least use Classic Theme Restorer to clean up the nav bar and tabs. In the listings of releases for ver 56, I chose Win64 and then have a bunch of choices which mean nothing to me. Which of these should I choose:
Dir ach/ Dir af/ Dir an/ Dir ar/ Dir as/ Dir ast/ Dir az/ Dir bg/ Dir bn-BD/ Dir bn-IN/ Dir br/ Dir bs/ Dir ca/ Dir cak/ Dir cs/ Dir cy/ Dir da/ Dir de/ Dir dsb/ Dir el/ Dir en-GB/ Dir en-US/ Dir en-ZA/ Dir eo/ Dir es-AR/ Dir es-CL/ Dir es-ES/ Dir es-MX/ Dir et/ Dir eu/ Dir fa/ Dir ff/ Dir fi/ Dir fr/ Dir fy-NL/ Dir ga-IE/ Dir gd/ Dir gl/ Dir gn/ Dir gu-IN/ Dir he/ Dir hi-IN/ Dir hr/ Dir hsb/ Dir hu/ Dir hy-AM/ Dir id/ Dir is/ Dir it/ Dir ja/ Dir ka/ Dir kab/ Dir kk/ Dir km/ Dir kn/ Dir ko/ Dir lij/ Dir lt/ Dir lv/ Dir mai/ Dir mk/ Dir ml/ Dir mr/ Dir ms/ Dir nb-NO/ Dir nl/ Dir nn-NO/ Dir or/ Dir pa-IN/ Dir pl/ Dir pt-BR/ Dir pt-PT/ Dir rm/ Dir ro/ Dir ru/ Dir si/ Dir sk/ Dir sl/ Dir son/ Dir sq/ Dir sr/ Dir sv-SE/ Dir ta/ Dir te/ Dir th/ Dir tr/ Dir uk/ Dir uz/ Dir vi/ Dir xh/ Dir xpi/ Dir zh-CN/ Dir zh-TW/
Going back to Firefox 56.0.2 isn't advisable. It is lacking security updates that came with all 5 of the Firefox 57 releases - the most important of which is 57.0.4.
https://thehackernews.com/2018/01/meltdown-spectre-patches.html
Gewysig op deur the-edmeister
But 57 is too difficult to configure. Moving from 24 to 56 should increase the security. Maybe someone will be able to create a plug-in like classic theme restorer with a checkbox interface for 57.
So how do I go back to 56 or a version that is configurable?
priopel said
Moving from 24 to 56 should increase the security.
Nobody should run Firefox 24.
What do you think about running the Extended Support Release of Firefox 52? It's not just for corporations any more; it's the last release for XP and Vista users, too. It will get security patches through this Summer.
priopel said
...chose Win64 and then have a bunch of choices which mean nothing to me. Which of these should I choose:
They are abbreviations for language locale. en-US and en-GB are easy as they are US and British English for example.
The locales you see in www.mozilla.org/firefox/all/ are same.
Gewysig op deur James
Gekose oplossing
I am now running 52 ESR. That was the smoothest transition ever. My ver 24, by the way, was also ESR. The tabs are now fully legible, the nav bar is gone though very awkward to retrieve, and other add-ons are once again available.
I did not fine ver 57 to be faster, in fact it seemed a bit slower. I have learned over the years to be hesitant to install "upgrades" because they always, always, always, create new bugs without fixing the old bugs. Why a programmer would consider making tabs less legible to be an "upgrade" is beyond me. I am still hopeful that someday the navigation bar control will be returned to its Ctrl-L (or file menu, "L") ease. The install program still has windows (dialogues?) that appeal all white for me. Thank you guys for really outstanding help. I am now up to ver 52 but will keep auto updates turned off until there is a sign that the nav bar problem and ability to configure FF has improved. I will try to attach some screen shots to show what I talked about above.
Oh well, I can only copy screen shots to a .doc file and this system only allows me to upload .jpg. Sorry.
Please Mark Solved the Solution That worked for you. Thank You.