X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Firefox updated and it took my tabs off the bottom and above address bar

Kuphostiwe

Dang these updates that do this. how to move tabs back below address bar? I know many people are tired of this problem!

Dang these updates that do this. how to move tabs back below address bar? I know many people are tired of this problem!

Isisombululo esikhethiwe

The one place I looked said no code for firefox update 71.0

The code from support article did nothing!

BUT!! this worked from reddit https://www.reddit.com/r/FirefoxCSS/

What you want to do is Open your userChrome.css and look for a section that should look like

#TabsToolbar {
 position: absolute !important;
 bottom: 0 !important;
 width: 100vw !important;
}

Then add in "display: block !important;" so that it becomes

#TabsToolbar {
 position: absolute !important;
 bottom: 0 !important;
 width: 100vw !important;
 display: block !important;
}

And you should be good to go. Just restart Firefox.

Funda le mpendulo ngokuhambisana nalesi sihloko 0
Isicaphuno

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 32.0 r0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Eminye Imininingwane

evhenry
  • Top 25 Contributor
  • Administrator
33 izisombululo 193 izimpendulo
Kuphostiwe
See this https://support.mozilla.org/en-US/kb/forum-response-tabs-below-url-bar
Ingabe lokhu kube usizo kuwena? 1
Isicaphuno

Impendulo Ewusizo

Way too complicated, need to know step by step how to get tabs on bottom. Have 71.0 update.

Way too complicated, need to know step by step how to get tabs on bottom. Have 71.0 update.

Okulungisiwe ngu tfinniii

Ingabe lokhu kube usizo kuwena? 1
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17699 izisombululo 160142 izimpendulo
Kuphostiwe

What code in userChrome.css did you previously use? can you post this code?

In Firefox 69 and later you need to set this pref to true on the about:config page to enable userChrome.css and userContent.css in the chrome folder.

What code in userChrome.css did you previously use? can you post this code? *https://www.userchrome.org/what-is-userchrome-css.html *https://www.userchrome.org/how-create-userchrome-css.html In Firefox 69 and later you need to set this pref to true on the <b>about:config</b> page to enable userChrome.css and userContent.css in the chrome folder. *toolkit.legacyUserProfileCustomizations.stylesheets = true *https://www.userchrome.org/firefox-changes-userchrome-css.html
Ingabe lokhu kube usizo kuwena?
Isicaphuno

Umnikazi wombuzo

I already had changes to put tabs on bottom and 71.0 broke it. I have chrome with it's contents still there. everything has been reset that wasn't and still not on bottom.

I already had changes to put tabs on bottom and 71.0 broke it. I have chrome with it's contents still there. everything has been reset that wasn't and still not on bottom.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
scottish2 7 izisombululo 93 izimpendulo
Kuphostiwe

Got this same issue all I want to do it have my tabs on the bottom the rest seem unaffected by the changes as far as the top area of the browser is concerned.

Got this same issue all I want to do it have my tabs on the bottom the rest seem unaffected by the changes as far as the top area of the browser is concerned.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
the-edmeister
  • Top 25 Contributor
  • Moderator
5420 izisombululo 40438 izimpendulo
Kuphostiwe

tfinniii said

I already had changes to put tabs on bottom and 71.0 broke it. I have chrome with it's contents still there. everything has been reset that wasn't and still not on bottom.

Swap out the code that you are now using for the code provided in that support article.


I feel your pain as I use userChrome.css to modify 6 other areas of the Firefox UI - not the Tabs. It seems that almost every recent update has had a minor change (or two) that has affected "Tabs on Top" and that has created problems for too many users. My advice is to keep up with "the curve" and get used to editing your code as needed OR just switch to a different web browser that better suits your desires.

IMO, with threads like this the end result just may be that the developers end support for userChrome.css altogether! And a Bug report to do that was filed long before Firefox 57 Quantum was released on November 14, 2017.

Mozilla very purposely disallows extensions that do such UI modifications so userChrome.css is being used not in lieu of those older Legacy extensions. Too many complaints and thus support issues as we now get, and Mozilla just may eliminate userChrome.css in total.

Try keeping up with the changes that happen, here: https://www.reddit.com/r/FirefoxCSS/

And maybe learn a bit about the modifications that you are doing to Firefox.

''tfinniii [[#answer-1271347|said]]'' <blockquote> I already had changes to put tabs on bottom and 71.0 broke it. I have chrome with it's contents still there. everything has been reset that wasn't and still not on bottom. </blockquote> Swap out the code that you are now using for the code provided in that support article. ------------------------ I feel your pain as I use userChrome.css to modify 6 other areas of the Firefox UI - not the Tabs. It seems that almost every recent update has had a minor change (or two) that has affected "Tabs on Top" and that has created problems for too many users. My advice is to keep up with "the curve" and get used to editing your code as needed OR just switch to a different web browser that better suits your desires. IMO, with threads like this the end result just may be that the developers end support for userChrome.css altogether! And a Bug report to do that was filed long before Firefox 57 Quantum was released on November 14, 2017. Mozilla very purposely disallows extensions that do such UI modifications so userChrome.css is being used not in lieu of those older Legacy extensions. Too many complaints and thus support issues as we now get, and Mozilla just may eliminate userChrome.css in total. Try keeping up with the changes that happen, here: https://www.reddit.com/r/FirefoxCSS/ And maybe learn a bit about the modifications that you are doing to Firefox.
Ingabe lokhu kube usizo kuwena? 0
Isicaphuno
scottish2 7 izisombululo 93 izimpendulo
Kuphostiwe

the-edmeister said

Swap out the code that you are now using for the code provided in that support article.

That doesn't seem to work though as I copied the one for the most recent versions and then went into about:profiles so I know I had the proper profile folder and then into Chrome and opened the CSS file and changed out the code and the tabs were in same spot I also downloaded the copy of the file they had on the support page and same thing.

''the-edmeister [[#answer-1271447|said]]'' <blockquote>Swap out the code that you are now using for the code provided in that support article. ------------------------ </blockquote> That doesn't seem to work though as I copied the one for the most recent versions and then went into about:profiles so I know I had the proper profile folder and then into Chrome and opened the CSS file and changed out the code and the tabs were in same spot I also downloaded the copy of the file they had on the support page and same thing.

Okulungisiwe ngu scottish2

Ingabe lokhu kube usizo kuwena? 0
Isicaphuno

Isisombululo Esikhethiwe

The one place I looked said no code for firefox update 71.0

The code from support article did nothing!

BUT!! this worked from reddit https://www.reddit.com/r/FirefoxCSS/

What you want to do is Open your userChrome.css and look for a section that should look like

#TabsToolbar {
 position: absolute !important;
 bottom: 0 !important;
 width: 100vw !important;
}

Then add in "display: block !important;" so that it becomes

#TabsToolbar {
 position: absolute !important;
 bottom: 0 !important;
 width: 100vw !important;
 display: block !important;
}

And you should be good to go. Just restart Firefox.

The one place I looked said no code for firefox update 71.0 The code from support article did nothing! BUT!! this worked from reddit https://www.reddit.com/r/FirefoxCSS/ What you want to do is Open your userChrome.css and look for a section that should look like #TabsToolbar { position: absolute !important; bottom: 0 !important; width: 100vw !important; } Then add in "display: block !important;" so that it becomes #TabsToolbar { position: absolute !important; bottom: 0 !important; width: 100vw !important; display: block !important; } And you should be good to go. Just restart Firefox.

Okulungisiwe ngu cor-el

Ingabe lokhu kube usizo kuwena? 0
Isicaphuno
Fire Marshal Bil 1 izisombululo 35 izimpendulo
Kuphostiwe

I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( I did a system restore, to no avail. I have spent over an hour screwing with this thing. Nothing like a slap in the face of users with every update! :-(0 The reward we get for using this obtrusive browser!

All this time, I have had _rounded_ tabs at the _bottom_, but all that changed as soon as I went to 71.0. This is an ongoing issue, forcing me to make Chrome my default browser. It was bad enough when they remove the Renaissance theme from Settings, but thankfully, there is an add-on.

I was going to attach userChrome.css but it allows only images.

Sorry to be extremely irritated. TIA.

I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( I did a system restore, to no avail. I have spent over an hour screwing with this thing. Nothing like a slap in the face of users with every update! :-(0 The reward we get for using this obtrusive browser! All this time, I have had _rounded_ tabs at the _bottom_, but all that changed as soon as I went to 71.0. This is an ongoing issue, forcing me to make Chrome my default browser. It was bad enough when they remove the Renaissance theme from Settings, but thankfully, there is an add-on. I was going to attach userChrome.css but it allows only images. Sorry to be extremely irritated. TIA.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
scottish2 7 izisombululo 93 izimpendulo
Kuphostiwe

Impendulo Ewusizo

Fire Marshal Bil said

I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( I did a system restore, to no avail. I have spent over an hour screwing with this thing. Nothing like a slap in the face of users with every update! :-(0 The reward we get for using this obtrusive browser! All this time, I have had _rounded_ tabs at the _bottom_, but all that changed as soon as I went to 71.0. This is an ongoing issue, forcing me to make Chrome my default browser. It was bad enough when they remove the Renaissance theme from Settings, but thankfully, there is an add-on. I was going to attach userChrome.css but it allows only images. Sorry to be extremely irritated. TIA.

I think we're all fed up but with all the intrusions going on with the big name companies I can't trust google much so don't want to get involved in chrome and have hated microsofts browsers for awhile so not much choice left.

I mean I do like that we have been able to control FF up until now to get it set as we want but these breaks are as you said very very irritating!

''Fire Marshal Bil [[#answer-1271609|said]]'' <blockquote> I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( I did a system restore, to no avail. I have spent over an hour screwing with this thing. Nothing like a slap in the face of users with every update! :-(0 The reward we get for using this obtrusive browser! All this time, I have had _rounded_ tabs at the _bottom_, but all that changed as soon as I went to 71.0. This is an ongoing issue, forcing me to make Chrome my default browser. It was bad enough when they remove the Renaissance theme from Settings, but thankfully, there is an add-on. I was going to attach userChrome.css but it allows only images. Sorry to be extremely irritated. TIA. </blockquote> I think we're all fed up but with all the intrusions going on with the big name companies I can't trust google much so don't want to get involved in chrome and have hated microsofts browsers for awhile so not much choice left. I mean I do like that we have been able to control FF up until now to get it set as we want but these breaks are as you said very very irritating!
Ingabe lokhu kube usizo kuwena? 1
Isicaphuno
the-edmeister
  • Top 25 Contributor
  • Moderator
5420 izisombululo 40438 izimpendulo
Kuphostiwe

Fire Marshal Bil said

I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( .....

You just don't get it! If you can't handle periodically tweaking the modifications that you make to Firefox, just learn to live with Firefox as it is built with Tabs at the Top of the UI.

Mozilla has been releasing updates and improvements to Firefox every 6 weeks for the last 7 years. Most changes don't affect the user interface (UI), but for quite awhile now multiple small changes have affected the UI, one new version at a time. I wish they would just rewrite Firefox all at once, rather than one step at a time; but it really seems to affect only for the small number of users who insist modifying / moving toolbars lately.

Tabs on Bottom hadn't been the default since March 22, 2011 when Firefox 4.0 was released, although until April 29, 2014 with Firefox 29 Australis there was a user pref for "Tabs on Bottom" when that pref disappeared as a built-in option. Due to Mozilla no longer wanting to support double the code and testing for an option they had changed 3 years prior. After that an extension, like Classic Theme Restorer, was needed for "Tabs on Bottom". Then as of November 14, 2017 with Quantum Firefox 57 and the new WebExtensions format, the ablility of extensions to greatly modify the UI was cut back. That's when userChrome.css modifications skyrocketed, and the "average user" started screwing up their Firefox installations.

Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing (and can't follow specific instructions) AND not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone!

''Fire Marshal Bil [[#answer-1271609|said]]'' <blockquote> I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( ..... </blockquote> You just don't get it! If you can't handle periodically tweaking the modifications that you make to Firefox, '''just learn to live with Firefox as it is built''' with '''''Tabs at the Top''''' of the UI. Mozilla has been releasing updates and improvements to Firefox every 6 weeks for the last 7 years. Most changes don't affect the user interface ''(UI)'', but for quite awhile now multiple small changes have affected the UI, one new version at a time. ''I wish they would just rewrite Firefox all at once, rather than one step at a time''; but it really seems to affect only for the small number of users who insist modifying / moving toolbars lately. '''Tabs on Bottom''' hadn't been the default since March 22, 2011 when Firefox 4.0 was released, although until April 29, 2014 with Firefox 29 Australis there was a user pref for "Tabs on Bottom" when that pref disappeared as a built-in option. ''Due to Mozilla no longer wanting to support double the code and testing for an option they had changed 3 years prior.'' After that an extension, like Classic Theme Restorer, was needed for "Tabs on Bottom". Then as of November 14, 2017 with Quantum Firefox 57 and the new WebExtensions format, the ablility of extensions to greatly modify the UI was cut back. That's when userChrome.css modifications skyrocketed, and the "average user" started screwing up their Firefox installations. Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing ''(and can't follow specific instructions)'' '''AND''' not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone!
Ingabe lokhu kube usizo kuwena? 0
Isicaphuno
scottish2 7 izisombululo 93 izimpendulo
Kuphostiwe

the-edmeister said

Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing (and can't follow specific instructions) AND not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone!

But the instructions have to be proper. Telling someone to add this code or that code to their user file and the code not working gets frustrating as well. Not faulting the user who suggested the code but firefox can very easily add this feature back as it's a popular feature being requested since they stopped it as alot of users prefer their tabs on the bottom. It would be far easier to put it back in then to have users messing about with various codes some of which do screw up the browser and make it unstable in some cases.

''the-edmeister [[#answer-1271626|said]]'' <blockquote> Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing ''(and can't follow specific instructions)'' '''AND''' not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone! </blockquote> But the instructions have to be proper. Telling someone to add this code or that code to their user file and the code not working gets frustrating as well. Not faulting the user who suggested the code but firefox can very easily add this feature back as it's a popular feature being requested since they stopped it as alot of users prefer their tabs on the bottom. It would be far easier to put it back in then to have users messing about with various codes some of which do screw up the browser and make it unstable in some cases.
Ingabe lokhu kube usizo kuwena? 1
Isicaphuno
Fire Marshal Bil 1 izisombululo 35 izimpendulo
Kuphostiwe

the-edmeister said

Fire Marshal Bil said
I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( .....

You just don't get it! If you can't handle periodically tweaking the modifications that you make to Firefox, just learn to live with Firefox as it is built with Tabs at the Top of the UI.

Snip the drivel...but it really seems to affect only for the small number of users who insist modifying / moving toolbars lately.

Tabs on Bottom hadn't been the default since March 22, 2011 when Firefox 4.0 was released, although until April 29, 2014 with Firefox 29 Australis there was a user pref for "Tabs on Bottom" when that pref disappeared as a built-in option. Due to Mozilla no longer wanting to support double the code and testing for an option they had changed 3 years prior. After that an extension, like Classic Theme Restorer, was needed for "Tabs on Bottom". Then as of November 14, 2017 with Quantum Firefox 57 and the new WebExtensions format, the ablility of extensions to greatly modify the UI was cut back. That's when userChrome.css modifications skyrocketed, and the "average user" started screwing up their Firefox installations.

Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing (and can't follow specific instructions) AND not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone!

Oh, I do get it, alright! Another condescending, name-calling know-it-all who wants to put down others just because he THINKS they are a lower form of life! I am not a fool, do make a living in I.T., have been using computers since 1988 and don't need your contemptuous blatherings, which I dismiss with a summary laugh!

For your information., I, thanks to no help from the likes of you, have modified the code to put the tabs in the bottom, widen it, round off the corners and make it the right color.

Next time, show some consideration and stop calling everyone else "clueless" and "screw-ups"! An iota of humility is in order here. It really displays and recognizes your arrogance and heightened sense of importance! Show respect and others will do likewise.

''the-edmeister [[#answer-1271626|said]]'' <blockquote> ''Fire Marshal Bil [[#answer-1271609|said]]'' <blockquote> I am sick of this. Mozilla thinks we users have lots of free time in a day trying to fix the issues that happen with every update! :-( ..... </blockquote> You just don't get it! If you can't handle periodically tweaking the modifications that you make to Firefox, '''just learn to live with Firefox as it is built''' with '''''Tabs at the Top''''' of the UI. Snip the drivel...but it really seems to affect only for the small number of users who insist modifying / moving toolbars lately. '''Tabs on Bottom''' hadn't been the default since March 22, 2011 when Firefox 4.0 was released, although until April 29, 2014 with Firefox 29 Australis there was a user pref for "Tabs on Bottom" when that pref disappeared as a built-in option. ''Due to Mozilla no longer wanting to support double the code and testing for an option they had changed 3 years prior.'' After that an extension, like Classic Theme Restorer, was needed for "Tabs on Bottom". Then as of November 14, 2017 with Quantum Firefox 57 and the new WebExtensions format, the ablility of extensions to greatly modify the UI was cut back. That's when userChrome.css modifications skyrocketed, and the "average user" started screwing up their Firefox installations. Mark my words, complaints from users who create and post in threads like this and have no knowledge of what the hell they're doing ''(and can't follow specific instructions)'' '''AND''' not taking the time to learn from their mistakes will eventually force Mozilla to eliminate the use of userChrome.css files altogether. Thus ruining Firefox for everyone! </blockquote> Oh, I do get it, alright! Another condescending, name-calling know-it-all who wants to put down others just because he THINKS they are a lower form of life! I am not a fool, do make a living in I.T., have been using computers since 1988 and don't need your contemptuous blatherings, which I dismiss with a summary laugh! For your information., I, thanks to no help from the likes of you, have modified the code to put the tabs in the bottom, widen it, round off the corners and make it the right color. Next time, show some consideration and stop calling everyone else "clueless" and "screw-ups"! An iota of humility is in order here. It really displays and recognizes your arrogance and heightened sense of importance! Show respect and others will do likewise.

Okulungisiwe ngu Fire Marshal Bil

Ingabe lokhu kube usizo kuwena? 1
Isicaphuno
jscher2000
  • Top 10 Contributor
8839 izisombululo 72253 izimpendulo
Kuphostiwe

Hi Fire Marshal Bil, are you using a rule set you picked up somewhere on line? Do you recall the source?

There's a dedicated subreddit for CSS tweaking where you can find like-minded UI hackers and learn about potential issues from users of beta versions so you can be better prepared when more changes come.

See: https://www.reddit.com/r/FirefoxCSS/

Hi Fire Marshal Bil, are you using a rule set you picked up somewhere on line? Do you recall the source? There's a dedicated subreddit for CSS tweaking where you can find like-minded UI hackers and learn about potential issues from users of beta versions so you can be better prepared when more changes come. See: https://www.reddit.com/r/FirefoxCSS/
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Fire Marshal Bil 1 izisombululo 35 izimpendulo
Kuphostiwe

No, I just modified the code that I already had with some online help, leaving much of it intact. And, that worked.

Thank you for the link, sir. In fact, I had already been there. They have been far more, no, infinitely more, helpful than the Firefox forums.

I have also made the background of the active tab black which looks sharp. I am good to go, until the next FF iteration. :-)

No, I just modified the code that I already had with some online help, leaving much of it intact. And, that worked. Thank you for the link, sir. In fact, I had already been there. They have been far more, no, infinitely more, helpful than the Firefox forums. I have also made the background of the active tab black which looks sharp. I am good to go, until the next FF iteration. :-)

Okulungisiwe ngu Fire Marshal Bil

Ingabe lokhu kube usizo kuwena?
Isicaphuno
Fire Marshal Bil 1 izisombululo 35 izimpendulo
Kuphostiwe

BTW, I came upon another of your helpful posts providing the following link:

https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox

I am certainly going to use that. Thank you.

BTW, I came upon another of your helpful posts providing the following link: https://developer.mozilla.org/en-US/docs/Tools/Browser_Toolbox I am certainly going to use that. Thank you.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17699 izisombululo 160142 izimpendulo
Kuphostiwe

That would be this selector:

.tabbrowser-tab[selected="true"] .tab-content { }
That would be this selector: .tabbrowser-tab[selected="true"] .tab-content { }
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Fire Marshal Bil 1 izisombululo 35 izimpendulo
Kuphostiwe

cor-el said

That would be this selector: .tabbrowser-tab[selected="true"] .tab-content { }

Thank you kindly.

''cor-el [[#answer-1271648|said]]'' <blockquote> That would be this selector: .tabbrowser-tab[selected="true"] .tab-content { } </blockquote> Thank you kindly.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
scottish2 7 izisombululo 93 izimpendulo
Kuphostiwe

Fire Marshal Bil said

No, I just modified the code that I already had with some online help, leaving much of it intact. And, that worked. Thank you for the link, sir. In fact, I had already been there. They have been far more, no, infinitely more, helpful than the Firefox forums. I have also made the background of the active tab black which looks sharp. I am good to go, until the next FF iteration. :-)

Can you post your coding here so I can try it also as so far nothing I have tried is getting the tabs set to bottom.

''Fire Marshal Bil [[#answer-1271646|said]]'' <blockquote> No, I just modified the code that I already had with some online help, leaving much of it intact. And, that worked. Thank you for the link, sir. In fact, I had already been there. They have been far more, no, infinitely more, helpful than the Firefox forums. I have also made the background of the active tab black which looks sharp. I am good to go, until the next FF iteration. :-) </blockquote> Can you post your coding here so I can try it also as so far nothing I have tried is getting the tabs set to bottom.
Ingabe lokhu kube usizo kuwena?
Isicaphuno
cor-el
  • Top 10 Contributor
  • Moderator
17699 izisombululo 160142 izimpendulo
Kuphostiwe

You can try this code in userChrome.css.

See also:

In Firefox 69 and later you need to set this pref to true on the about:config page to enable userChrome.css and userContent.css in the chrome folder.

You can try this code in userChrome.css. *https://support.mozilla.org/en-US/kb/forum-response-tabs-below-url-bar See also: *https://www.userchrome.org/what-is-userchrome-css.html *https://www.userchrome.org/how-create-userchrome-css.html In Firefox 69 and later you need to set this pref to true on the <b>about:config</b> page to enable userChrome.css and userContent.css in the chrome folder. *toolkit.legacyUserProfileCustomizations.stylesheets = true *https://www.userchrome.org/firefox-changes-userchrome-css.html
Ingabe lokhu kube usizo kuwena?
Isicaphuno
Buza umbuzo

Kufanele ulogele ukungena ku-akhawunti yakho ukuze uphendule amaphosti. Uyacelwauqale umbuzo omusha, uma ungekabi nayo i-akhawunti namanje.