userChrome.css file not being recognised/implemented by Firefox
Recently updated Firefox to FX65 and as expected had the 'Tabs on top problem return.' Followed advice given earlier in <Tabs not on Bottom> forum post and found that there was no 'chrome' folder in my Profile folder so created one and then added the 'userChrome.css' corrected file to move my Tabs back to the bottom. However, on restarting Firefox this fix did not work on my laptop. N.B.: it worked fine for my desktop PC.
So i now need help please?
被選擇的解決方法
If you used the same userChrome.css file and created the chrome folder in the correct location then this should work. You can check that the userChrome.css file doesn't have a hidden .css or .txt file extension (userChrome.css.css or userChrome.css.txt) and that it is a plain text file (e.g. open the file in a Firefox tab).
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:preferences page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
所有回覆 (2)
選擇的解決方法
If you used the same userChrome.css file and created the chrome folder in the correct location then this should work. You can check that the userChrome.css file doesn't have a hidden .css or .txt file extension (userChrome.css.css or userChrome.css.txt) and that it is a plain text file (e.g. open the file in a Firefox tab).
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:preferences page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
Well i don't quite understand why, but after deleting all my work and re-applying the 'chrome' folder and corrected 'userChrome.css' file it all worked fine this time. I suspect, as you suggested, there was some file permissions trickery going on.
Thank you for your help.