This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Waterfox support

  • 10 răspunsuri
  • 1 are această problemă
  • 10 vizualizări
  • Ultimul răspuns de cor-el

more options

How do I report a page that can not be accessed using Waterfox? See Attached Also, is "Facebook Container" ever going to be available for use with Waterfox?

How do I report a page that can not be accessed using Waterfox? See Attached Also, is "Facebook Container" ever going to be available for use with Waterfox?
Capturi de ecran atașate

Toate răspunsurile (10)

more options

Hello simpleman2,

For Waterfox support :

https://www.reddit.com/r/waterfox/

more options

You are using a pre Quantum Firefox version based upon Firefox 56 and that version only has some basic support for WebExtensions.

Each WebExtension has a minimum Firefox version and for Facebook Container the minimum requirement is Firefox 67.

Modificat în de cor-el

more options

Thanks for responding. The only reason that I'm still using Waterfox Classic is because it will continue to support all the old legacy add-ons like (Classic Theme Restorer 1.7.7.2), (Hide Tab Bar With One Tab 1.5.1) and such. There is a whole Legacy Addon Data Base that supposedly will only work with Waterfox Classic. The latest versions of Firefox no longer support all these add-ons. If I'm wrong, please correct me and direct me where I can read up on it. https://www.ghacks.net/2019/05/06/what-you-need-to-know-about-add-ons-in-waterfox-68/

https://www.ghacks.net/2019/10/25/waterfox-development-splits-into-classic-and-current-branches/

more options

McCoy said

Hello simpleman2, For Waterfox support : https://www.reddit.com/r/waterfox/

Can't get past the whole Flair thing, it would be easier to just switch over to Chrome than deal with this whole mess. What am i suppose to do with this??? There is already a picture next to my profile name.

more options

The nextmd.com website works for me with Firefox 52 and thus should work in Waterfox 56 as well.

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

simpleman2 said

Can't get past the whole Flair thing, it would be easier to just switch over to Chrome than deal with this whole mess. What am i suppose to do with this??? There is already a picture next to my profile name.

 Instead of copying and pasting everything, I'll let you take a look at
these search results .....

more options

cor-el said

You are using a pre Quantum Firefox version based upon Firefox 56 and that version only has some basic support for WebExtensions. Each WebExtension has a minimum Firefox version and for Facebook Container the minimum requirement is Firefox 67.

I thought Firefox was doing away with WebExtensions. That is the only reason that I'm forced to stick with Waterfox Classic. From what your saying that means that Firefox is not backwards compatible either. So every time that that someone upgrades to the latest Firefox version they risk losing the WebExtentions that they previously enjoy/need......Not good.

The only two WebExtentions that I use are the "Classic Theme Restorer 1.7.7.2" (so that I can hide the navigation toolbar) and the "Hide Tab Bar with One Tab 1.5.1" (so that I can hide the annoying tab bar completely).

Does the Latest version of Firefox have any WebExtentions that provide the same two functions listed above: (A way to hide the navigation toolbar) and (A way to hide the annoying tab bar completely) ??? This just keeps getting worse, why am I seeing a scroll bar in the middle of my reply??? See attached

Modificat în de simpleman2

more options

It hardly ever happens that WebExtensions get broken in newer Firefox versions. When this happens then this is usually about APIs that are deprecated and no longer supported and usually the old API is replaced by a new API with more/other feature. In such a case the developer of the extension needs to address this with an update.

Quote: The only two WebExtentions that I use are the "Classic Theme Restorer 1.7.7.2" (so that I can hide the navigation toolbar) and the "Hide Tab Bar with One Tab 1.5.1" (so that I can hide the annoying tab bar completely).

You can do both with code in userChrome.css, but if you haven't used more curent Firefox versions for a long time then you will likely want to make more changes that require additional code in userChrome.css.

Note that you break a lot of things if you would hide the Navigation Toolbar as there are a lot button on this toolbar for important features and there are also notification icons that anchor to the location bar like the shield icon for Tracking Protection. So maybe you first should try this out with the Navigation Toolbar visible and possibly consider autohide for this toolbar. You can search the Reddit website for code how to deal with the Navigation Toolbar.

more options

cor-el said

It hardly ever happens that WebExtensions get broken in newer Firefox versions. When this happens then this is usually about APIs that are deprecated and no longer supported and usually the old API is replaced by a new API with more/other feature. In such a case the developer of the extension needs to address this with an update. I know that WebExtentions don't get broken, the problem is that newer versions of FF just stop supporting certain ones over time. FF also makes it next to impossible for developers to make the older and greater WebExtentions work in newer FF versions. Quote: The only two WebExtentions that I use are the "Classic Theme Restorer 1.7.7.2" (so that I can hide the navigation toolbar) and the "Hide Tab Bar with One Tab 1.5.1" (so that I can hide the annoying tab bar completely). You can do both with code in userChrome.css, but if you haven't used more curent Firefox versions for a long time then you will likely want to make more changes that require additional code in userChrome.css. First of all I have no idea what code is, do you mean typing script into a command prompt? Second, that would not work for hiding the Navigation Toolbar, it can't be permanent, I need to be able to hide and unhide at will like I do now. Note that you break a lot of things if you would hide the Navigation Toolbar as there are a lot button on this toolbar for important features and there are also notification icons that anchor to the location bar like the shield icon for Tracking Protection. So maybe you first should try this out with the Navigation Toolbar visible and possibly consider autohide for this toolbar. You can search the Reddit website for code how to deal with the Navigation Toolbar.

Nothing gets broken hiding the Navigation Toolbar. LOL I prefer no clutter what's so ever, when I'm on a website and viewing photos this is how I like my screen to look......see attached. By losing the ui customization ability for users Firefox definitively took a big step back. It loses the only advantage it had over all other browsers. Does the Latest version of Firefox have any WebExtentions that provide the same two functions listed above: (A way to hide the navigation toolbar) and (A way to hide the annoying tab bar completely) ??? If not I'll just start trying out other web browsers to see if they have such WebExtentions. Thanks for your help, but I should not have to deal with writing script for such features'''

Modificat în de simpleman2

more options

Web Extensions can't modify or hide elements in the user interface like was possible with Legacy extensions. You can only do this in Firefox versions that only support Web Extensions via code in userChrome.css.