Firefox Community Forum

The Back arrow/button in the address bar is unclickable, greyed out and no longer functional.

Is there a specific fix we can make in about:config to regain function of the back arrow/button? A response from a person (or people) would be appreciated.

Your really do not want as much detail from me as possible. I guarantee that. ("Everything is connected" should be enough of an explanation.) But you ask for details . . . .

This is specifically about updates (not also installation). Which update and and when I do not know, although it could be Microsoft fooling around with Firefox functionality. OR it could be ESR being updated when updates have been disabled. So that raises the question about the extent to which Microsoft is also configuring Firefox when FF is the default browser. (We deserve to know.) I have changed back to normal updates, and will try to disable the incessant frequent updates which always include undoing new standardized FF configurations that were labor intensive to find fixes for the first time. Fortunately, I have kept a file of many of them. Apparently A.I. (oops, maybe it was Firefox) has agreed to give access to Microsoft to interfere with how Firefox is configured when Firefox is the default browser, regardless of the FF version,

Specific details (I will try to make this as repetitive, overly simplified, and superfluous as the auto a.i. responses though I most likely will fail): And if expressing dissatisfaction is violating the rules and guidelines, then please understand I am human, and do not like everything I do online being the result of 1/0 on/off/humanizing A.I. (including genetically . . . oh yeah, we all know where this free "training" of a.i. is going that we are all being used to do without our consent - and worse).

The back arrow/button on the address bar is no longer clickable and it is greyed out. It is apparently another new Firefox standardization that is not one size fits all. The easy solution would have been for the people who do not like the feature to be advised to remove the button/arrow from the address bar. But, no. Instead, at some point, a new update standardized the arrow/button to become unclickable and dysfunctional.

I found a question about how to make the back arrow/button functional again. The question was not why has it been made dysfunctional. The answer was why it had been made dysfunctional.

In short, some people found the arrow/button to be problematic. A.I. said people were losing information they had input to a form, when they used the back arrow/button before completing the form.

So what did FF (or A.I.?) do? Made the arrow/button dysfunctional for everyone because a few folks in lala land did use common sense, and simply remove the button from the address bar so they would not be tempted to use it and lose information.

Why was that a solution instead of Support (A.I.?) telling people who found the arrow/button to be problematic, to remove the arrow/button from the address bar? Really? Why not advise people to make the feature dysfunctional for themselves - instead of the solution being to make it dysfunctional for everyone who uses Firefox Browser.

Here is the basic, simple, question and content I would have preferred, and I'm guessing many actual people would have too.:

Again:

The Back arrow/button in the address bar is unclickable, greyed out and no longer functional. Is there a specific fix we can make in about:config to regain function of the back arrow/button? A response from a person (or people) would be appreciated.

Thanks in advance.

I'm running Firefox under Ubuntu, Ubuntu is using Wayland which replaced X11.

Firefox's User Agent string still refers to X11, this does not cause me any problem but I'm curious.

I realise some websites might be expecting to see "X11" and could get upset if presented with "Wayland" instead but in various walks of life telling the truth is often the best policy.

about:support in Firefox shows me:

User Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0 Window Protocol wayland

Fonts are not scaled correctly. Too big and overlapping and too small on same page. Not scaling to fit page. Worse on Youtube and gmail. Screen shot is from this page!

Every time I log on to Firefox, or attempt to use the brozser, I am asked to update Firefox. So I proceed to do the update download; The software refuses to do anything. So I continue with the old release. Apparently, this is a common problem. Yet Firefox staff continues to ignore the situation.

HOW DOES ONE UPDATE THE FIREFOX SOFTWARE?????

macOS Tahoe, Firefox 152.0.3 macOS settings include "Appearance - Auto"; i.e. system switches from light to dark at sunset. While the "top area" (tabs, address bar, bookmarks bar) of Firefox follows this - some of the pages themselves do NOT???

I found this website which was at top of the search results. I tried to follow it, but it seems to be badly outdated in certain key respects: esp wrt a setting called "ui.systemUsesDarkTheme" in about:config. I set this to "True", but may have screwed this up!! First question: Should I "reset" this somehow?

Finally: To get at the primary question, there are two "sub-questions" that may explain my confusion more clearly:

1. Is there no ***simple way*** to get Firefox & webpages I view to follow macOS Light/Dark appearance?? What are the CORRECT steps?

2. Do individual webpages have the ability to "decide for themselves" whether or not they will adhere to the system light/dark settings. This may well be an officially "stupid question", but while "most" webpages remain "Light" (including this Support page), a few pages appear dark.

Thanks, ~S

I have Windows 10 a decent Lenovo laptop

I am fed up having to update firefox every single day !! Is it not completing the update or is there some glitch that keeps occurring ??

I have used FF for quite a while and ignored MicroSoft Edge... but I dont know how much longer I can carry on with this slowdown !!

Why am I suddenly receiving this error message when signing onto explore.org live camera feed. Error message is "Playback isn't supported on this device". i am able to play other videos on you tube,etc. How can I fix this?

Hello Firefox Support Team/Forum

I am writing to request guidance on a hardware video acceleration issue that I have been unable to resolve despite extensive troubleshooting. Firefox appears to be blocking VA-API hardware decoding on my system even though the VA-API stack is confirmed working at the system level. — SYSTEM SPECIFICATIONS — OS: Arch Linux (rolling), kernel 7.0.13-arch1-1 Desktop: Hyprland 0.55.4 (Wayland, DRM backend) CPU: AMD A9-9425 (2 cores, 3.1GHz, Excavator architecture) RAM: 8GB Firefox: installed via pacman (native, not Flatpak) Mesa: 26.1.3-arch1.2 GPU setup (dual): • card0 / renderD128: AMD Stoney R5 Graphics (iGPU) — VA-API confirmed working here • card1 / renderD129: AMD Hainan R5 M435 (dGPU) — used by Hyprland for display output — CONFIRMED WORKING AT SYSTEM LEVEL — Running ‘vainfo’ on the integrated GPU (renderD128) confirms the following profiles are available: VAProfileH264ConstrainedBaseline, VAProfileH264Main, VAProfileH264High (VLD + EncSlice) VAProfileHEVCMain, VAProfileHEVCMain10 (VLD) VAProfileMPEG2Simple, VAProfileMPEG2Main, VAProfileVC1 (VLD) VAProfileJPEGBaseline (VLD) MPV with ‘–hwdec=vaapi-copy’ successfully hardware-decodes H264 locally, confirmed by ‘nv12’ pixel format output and reduced CPU usage. radeontop monitoring card0 (stoney, bus 00) during Firefox video playback shows: • Graphics pipe: ~53% (compositing activity) • UVD row: absent / 0% (no hardware video decode activity) • Memory clock: near 0.00G This confirms Firefox is NOT using the hardware decoder despite VA-API being functional. — FIREFOX DECISION LOG (from about:support) — HARDWARE_VIDEO_DECODING: default available / user force_enabled H264_HW_DECODE: default available (no blocklist) HEVC_HW_DECODE: default available VP8_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING VP9_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING AV1_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING DMABUF_SURFACE_EXPORT: env blocked — FEATURE_FAILURE_BROKEN_DRIVER WEBRENDER_COMPOSITOR: env blocklisted — FEATURE_FAILURE_WEBRENDER_COMPOSITOR_DISABLED Note: VP8/VP9/AV1 being missing is expected and correct for this GPU generation. The concern is that H264, which IS in the vainfo profile list and shows as ‘available’ in the decision log, is still not being routed to the hardware decoder in practice. — ENVIRONMENT VARIABLES IN USE — MOZ_ENABLE_WAYLAND=1 LIBVA_DRIVER_NAME=radeonsi LIBVA_DRM_DEVICE=/dev/dri/renderD128 MOZ_DISABLE_RDD_SANDBOX=1 — about:config SETTINGS CURRENTLY SET — media.ffmpeg.vaapi.enabled = true media.hardware-video-decoding.force-enabled = true media.hardware-video-decoding-vulkan.enabled = false media.rdd-process.enabled = true — WHAT WAS TRIED — 1. Installed full Mesa stack: mesa, libva-mesa-driver, libva-utils, ffmpeg, vulkan-radeon (64-bit and 32-bit variants via multilib). 2. Set LIBVA_DRM_DEVICE=/dev/dri/renderD128 to hardcode VA-API to the stoney iGPU and prevent it from accidentally targeting the hainan dGPU (which fails Firefox’s internal VA-API test with FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED). 3. Enabled media.ffmpeg.vaapi.enabled and media.hardware-video-decoding.force-enabled in about:config. 4. Disabled MOZ_DISABLE_RDD_SANDBOX via both ~/.bash_profile and hl.env() in the Hyprland Lua config to allow Firefox’s RDD process to access /dev/dri/renderD128. 5. Installed enhancedH264ify extension with VP9 and AV1 blocking enabled. YouTube confirms H264 (avc1.64002a) is being served. Despite this, over 1100 frames out of ~4200 are dropped during 1080p60 playback. 6. Verified with radeontop -b 0 (stoney, bus 00) during active 1080p H264 playback: the UVD block shows no activity whatsoever, confirming the CPU is doing all decoding. 7. Tested with and without gfx.webrender.all = true. Enabling it caused severe visual corruption (texture artifacts, split UI elements), so it was reset to default. 8. Did NOT disable media.rdd-process.enabled (correctly kept at true, as RDD is the process Firefox uses for VA-API decoding). 9. Confirmed Firefox is installed via pacman (not Flatpak), so there is no Flatpak sandbox layer involved. — THE CORE QUESTION — Given that: • vainfo confirms H264 hardware decode is available on renderD128 • H264_HW_DECODE shows as ‘default available’ in Firefox’s own decision log with no blocklist entry • media.hardware-video-decoding.force-enabled is set to true • MOZ_DISABLE_RDD_SANDBOX=1 is set • LIBVA_DRM_DEVICE explicitly points to the correct render node • MPV successfully uses vaapi on the same system …why is Firefox’s RDD process still not routing H264 decoding through VA-API, and what additional steps or logs would help identify the specific internal failure point?

Any guidance on enabling verbose VA-API logging within Firefox’s RDD process, or any known issues with AMD Stoney + Hainan dual-GPU setups on Wayland that might explain the DMABUF_SURFACE_EXPORT FEATURE_FAILURE_BROKEN_DRIVER blocklist, would be greatly appreciated.

Thank you.

Firefox suddenly stopped autofilling my password on a frequently used website and nothing I do fixes the issue. I've tried all the options and followed instructions offered on the firefox help pages and nothing works. Please advise?

When I click on the Mozilla VPN app icon in the Mozilla Browser it requests that I download something rather than just turning it on. This is recent and I've never experienced it before... I have tried everything I can think of, but cannot get it to work properly...

So Firefox total changed my browser design. It has taken over my full screen. My tabs are on the side now. There is no back or forward arrows to go back to the previous web page. The add-ons are no longer visible or accessible. And there is no way to close the browser without using the task manager.

Windows 11 Pro

I recently opened this 'bug' which may involve my inadvertent use/misuse of Profiles. https://bugzilla.mozilla.org/show_bug.cgi?id=2052294

How can I locate other (older) Profiles in the Mozilla Firefox structure and use this to run an older version of Firefox ie: 132 or other Version that I consider to be more stable.

(I have already seen where it is not recommended to go to an older version, once a profile has been used on an updated version. At this time - I feel any damage has ALREADY been done & cannot make things much worse.)

In the previous version of Firefox, there was a location to save current tabs in the "Home" section is that still available? Where is it?

I've attached a photo of the current page, and there does not appear to be a "save current tabs" option