Các câu trả lời gần đây cho Two address bar problemshttps://support.mozilla.org/vi/questions/12900922020-06-06T13:03:18-07:00Edmeister,
Thanks for this background, but I still don't know how to move the tabs to below the addr2020-06-06T13:03:18-07:00mikejanus100https://support.mozilla.org/vi/questions/1290092#answer-1321017<p>Edmeister,
Thanks for this background, but I still don't know how to move the tabs to below the address bar and how to have the address bar act as it did previously.
</p> userChrome.css is specific to the Firefox Profile in which that css file is located. And different 2020-06-06T11:00:17-07:00the-edmeisterhttps://support.mozilla.org/vi/questions/1290092#answer-1321003<ol><li> <strong>userChrome.css</strong> is specific to the Firefox Profile in which that css file is located. And different versions of the same operating system may be different enough that Win7 tweaks may not work exactly the same as with Win10.
</li><li> Wrong place to ask for help with userChrome.css - <a href="https://www.reddit.com/r/FirefoxCSS/" rel="nofollow">https://www.reddit.com/r/FirefoxCSS/</a> is a better source.
</li><li> Typically user <strong>Content</strong>.css is for styling content of web pages and some internal browser pages, such as the older <strong>chrome:/ </strong> 'pages' that are built into Firefox along with the newer <strong>xhtml</strong> internal pages.
</li><li> Firefox has been undergoing a continual rewrite of internal code to move away from XUL and moving towards xhtml code for a few years now. And lately <strong>css</strong> has been broken in small pieces and sometimes with every version release that comes out. Firefox 75 and then again with Fx 77 happened to affect the address bar. Plus some of the preferences that were added for Fx75 were temporary and were removed with Fx77, something that the developers have been doing from time to time for a couple of years now.
</li></ol>
<p>Personally, if I were a software programmer I would have started with a clean sheet of paper with building Quantum rather than deciding to "fix" the code base in this piece-meal fashion, which is taking too long <em>(too many years thus far, with no end in sight)</em> to reach the end with a "new Firefox". I said that that 20 version releases ago with Firefox Quantum 57 and still feel so now even more so. IMO, too many "self-inflicted" small injuries will eventually "kill the patient" as exsanguination would, just takes much longer and is more painful as it slowly happens.
</p><p>Overall, imo userChrome.css is now is expected to far more that what it was intended for back in the early days of Netscape, then the Mozilla Suite from which Firefox was derived. I have only been a user since 9/2002, before the name Firefox was placed upon this web browser in 2004, and I started employing a userChrome.css file in late 2003 for very minor tweaks and later to hide context menu items that I didn't even use, to pare the contextual menu down to keep it from "bouncing off the bottom of the browser window" with the number of extensions that I was using back in those days.
</p>