Since Firefox 157 introduced Nova, I’m finding container tabs much harder to distinguish.

With native vertical tabs, the prominent vertical container marker has been replaced by a thin horizontal line. The colours and icons also appear more subtle and less solid. As a colour-blind user, that makes it harder to tell at a glance which container I’m using.

This also happens on a PC without Tree Style Tab installed, so it isn’t specific to that extension.

Container identity matters when separating accounts and browsing contexts. I’d like to see:

• A supported option for a thicker, solid container marker.
• A visible container name or distinct symbol on each tab, so identification doesn’t depend on colour alone.
• Accessibility testing of selected and unselected tabs in both light and dark themes.

For now, setting browser.nova.enabled to false in about:config is a potential workaround, but it changes the broader interface and may not remain available.

Has anyone else, particularly other colour-blind users, found this harder to use? Have you found a supported way to improve the indicators while keeping Nova?

I requested an accessibility review in https://bugzilla.mozilla.org/show_bug.cgi?id=2077901.
If you’re affected, please add your Firefox version, theme, and specific difficulties to the report, especially if they provide new information.

this is unacceptable on android lmao

Please vote for this feature request if you think it deserves it.

Pretty disappointed with my PWA experience on Android. Seems like any site I want to use for PWA end up just loading as a separate tab.

It is rare i find a website that works with FF's PWA.

In my humble opinion, if the following bugs are prioritized it would improve the experience greatly for Android users:
Installing PWAs doesn't work
Allow installing any website as a fullscreen web app
Automatically switch to PWA as long as web app is installed

Painfully slow progress by Mozilla, e.g:

https://connect.mozilla.org/t5/ideas/hdr-support-for-windows/idi-p/6468

https://bugzilla.mozilla.org/show_bug.cgi?id=1889288

https://bugzilla.mozilla.org/show_bug.cgi?id=1918773

If you have a high quality HDR monitor (or basically any modern phone), visit the following with Chrome/Edge/Safari to understand what Firefox users are missing when HDR photographs fall back to SDR:

https://gregbenzphotography.com/hdr/

HDR photography has been enabled by default on pretty much all Androids & iPhones released in the past few years, and ISO 21496-1 (recently finalized) now means HDR photographs are sharable across Android/iOS/MacOS/Windows platforms, etc., with seamless SDR fallback when software doesn't support HDR... like Firefox.

https://en.wikipedia.org/wiki/Ultra_HDR

As the title says, I can positively confirm that Google is throttling uploads to Youtube through Firefox. For a few weeks I was noticing upload speeds around 40Mbps, and to test my theory that Google hates Firefox, I downloaded and installed Chrome, and uploaded a 30 minute video through Chrome instead of Firefox. And wouldn't you know it, my upload speed shot up to 400+Mbps.

This is such a shame that Google is so strongly opposed to people who use Firefox instead of Chrome, when Firefox is by far the better browser. I just wanted to create this post in hopes of helping somebody else out there who is experiencing the same problem that I am.

I'm experiencing frequent Firefox (v156.0) crashes on macOS Golden Gate on an M3 MBP. This seems to be specific to macOS Golden Gate as I hadn't experienced this in several years of using Firefox on this specific laptop, and it started right after I upgraded.

It's not specific to any one site (though I do use Google Docs / Sheets / Slides a lot, and I know those are fairly complex webapps), and the crash reporter pops up each time (and I've been faithfully sending in every report).

Anyone else experiencing something similar? Better yet, anyone know of a fix?

Strange flickering on my website in Firefox. Sometimes, (not always) when changing the page it shows a gray background for about a frame / split second, before loading in the new page. This example is running on localhost, but the exact same problems happens on the site when uploaded to my host server.

Why is this happening? It's not a problem on Chromium / Edge, Chrome.

This has honestly been an on going issue that nobody seems to address, There is already a bugzilla report and this bug has been confirmed but completely ignored, and not to mention the bug is already 2 years old. It seems over time the more videos you watch for example like on youtube, the VRAM stacks up even when you have closed the tab. It eventually gets up 7-8GB of VRAM (for reference that is literally half my VRAM pool being used on nothing and for most other people that would literally be all of it). Honestly it is very inconclusive as to what exactly triggers this build up, from what I have witnessed it seems to building up when I have a video tab left open for a while, even if the video is paused. The Bugzilla report is also saying: "I can reproduce bug in 5-15 seconds consistently. The key is no force decoding more chunks of video, just by seeking through video. I used two 4k videos in two tabs, to get from 0 to >2GB vram in seconds. Also with media.use-blank-decoder there is seemingly no leak." Although for me I am not able to reproduce that result on my end.

The only solution I have found is to completely close down Firefox to release it. And usually it might not be that big of a deal but having literally only 1 tab open and half my VRAM pool being eaten up for no reason is insane, I also like to keep tabs and windows open, so its not exactly ideal having to constantly close up Firefox.

This issue seems to be on every branch of Firefox, (Stable, Nightly, Dev, Beta). From what I have tested. Does anyone else have this issue or has noticed this also? Or I am the only one?

For those who have preferred using the "Search the web" entry field in the Firefox home page, it seems like a recent experiment broke this feature and it now redirects your searches to the main address bar.

Some of you may recall this behavior was controlled by the about:config setting "browser.newtabpage.activity-stream.improvesearch.handoffToAwesomebar", and you could set this option to false to keep your searches within the home page widget rather than automatically jumping to the main address bar.

The study that broke this feature is "New Tab 149.1.20260121.51415 to Release 147.0.3", and after turning that study off in about:studies you can get back the old behavior - at least for now!

But really someone should fix the underlying problem here, before this experimental study eventually goes into the mainstream code.

Edit 1: I reported this on Bugzilla. The ticket number is 2016227.

Edit 2: I received a response from the Firefox developers, who confirmed that they are deliberately getting rid of the legacy "Search the web" widget on the home page. Here is what they said:

This is an intentional change. As part of a larger refactor of our search UI, we removed the non-default (and unsupported) non-handoff mode from the search input on New Tab. This is letting us clean up the surrounding code (which had deep tendrils into New Tab) so that the Search team can work on and eventually land in an inline search experience later this year which will replace the current handoff mode.

See https://bugzilla.mozilla.org/show_bug.cgi?id=1999334#c1 and https://bugzilla.mozilla.org/show_bug.cgi?id=1999334#c5 for more details.

Edit 3: (26 Feb 2026) Apparently the Firefox developers are currently working on something to revert to old behavior, but it's not clear exactly when this will be available.

Meanwhile, they pushed out a new study called "New Tab 149.1.20260121.51415 to Release 147" which reintroduced the same unhappy behavior as I originally described for "New Tab 149.1.20260121.51415 to Release 147.0.3" several weeks ago. Again you can opt-out via "about:studies" -- for now! -- while we keep waiting for a more permanent solution to this issue.

Edit 4: (10 Mar 2026) The problem appears to be fixed in Firefox 148.0.2

This is the only issue which is bugging me a lot.

https://bugzilla.mozilla.org/show_bug.cgi?id=1752594

I am experiencing an issue where videos on YouTube glitch out and frames repeat with major corruption. Entirely randomly and I can rewind to view the same section without issue. I'm not sure how to debug for this or know what exactly is going wrong.

==System==

Steam Deck LCD

BIOS F7A0131

AMD APU 0405

16 GB Ram

Arch Linux (not SteamOS) Kernel 6.13.8-arch1-1

Gnome 48

Wayland

Firefox 137.0

Go to your phone's system settings and manually advance your time by a few hours. Go back to Firefox and manually sync, then set your system time back to automatic.

The above appears to temporarily fix the issue. The only catch is that Firefox won't attempt an automatic sync again until its perception of time catches up (i.e., if you advanced system time 4 hours, synced, then went back to automatic timekeeping, Firefox won't let you manually or automatically sync until 4 hours elapses.)

There's another "fix" that doesn't involve manually changing your time, but it's a huge pain in the ass: uninstall the app and then reinstall.

Apparently the developers are possibly aware of this issue after people reporting this for more than a year. https://bugzilla.mozilla.org/show_bug.cgi?id=1924544 https://bugzilla.mozilla.org/show_bug.cgi?id=2038290

I'm using Firefox 152.0.3 (at the time of writing) from the mozillateam PPA on Xubuntu 24.04 LTS. It uses pipewire-pulse, so should be PulseAudio.

What seems to be my issue was documented here in this 8 year old bugreport.

What I tried:

• With media.volume_scale and media.default_volume → set it to double digits in about:config. I thought 2 for both would suffice but it did not work reliably. I'm in double digits now, but I'm afraid once Mozilla fixes this I'll go deaf or my speakers will really really hate it.
• In .config/pipewire/pipewire-pulse.conf.d in my home directory, I made a custom.conf file with contents stream.properties = { channelmix.normalize = false }
• In PulseAudio's daemon.conf I set flat-volumes = no and /usr/share/pipewire/ in pipewire-pulse.conf I added:

​

pulse.rules =
[
  {
    matches =
    [
        { client.name = "Firefox" }
        { application.process.binary = "firefox" }
        { application.name = "Firefox" }
    ]
    actions =
    {
        update-props = { #node.latency = 512/48000 }
        quirks = [ block-sink-volume ]
    }
  }
]

It doesn't sound like much effort put into it, but I searched all over and found near nothing on this. I'm honestly lost as to what else to do with this weird issue.

Even with double-digits for the two settings I caught how it ended up having some streams start quieter today. It remembered the volumes now after setting ones, but well… that just showed me the issue is still there and requiring attention.
Note that it does not change it midstream, only upon stream start, and now after setting a volume, it keeps it even when the stream restarts.

I'm not sure if it's Pipewire, PulseAudio, or whatever doing it, or allowing it (if so, I would love to turn this off – permanently, for all applications), or if it's a Firefox quirk, exclusively.

How to reproduce:
I found Aphex Twin's Vordhosbn (and the Windowlicker audio upload, though no idea I should or could link it here due to thumbnail) to be two cases where volumes changed against my expectations.
Without the edits mentioned, skipping with arrow keys through the video position, clicking through it, or hitting a number key to jump to a fixed position did reset the audio stream and consequently also its volume.
Pausing the video kept the stream active and as a result the volume remained in place.

Any help appreciated.
Would be great to hear if anyone solved this on their end. It's mildly infuriating.
I only found solutions involving Windows where it seemed to have been an audio driver setting allowing it to do so.

Following the latest Firefox update, it seems though the clear site data control within the SSL section is no longer usable, it's grayed out. Am I missing anything ?

You can customize new tab shortcuts (the squares) but it will throw error for invalid link if I try to make it go to about:translations for example

I'm not sure if it's just me or what, but ever since the last two updates, I've noticed that history is basically nonfunctional from the sidebar.

Nothing I type or try to search works at all. Like I even tried to search YouTube of all things, and it cannot be found. But when I don't use the sidebar and just pull up the full history panel, everything shows up.

I didn't see anyone else commenting on this, so does anyone have any clues?

Edit: I've already tried troubleshooting mode, it doesn't change anything even with all add-ons disabled.
Edit 2: Thank you, I understand the issue (bug 2043614) and will just wait for an update I guess.