Firefox — Fora społeczności

I saved and closed a few tab groups about a month ago and now they're no where to be seen. Nothing is in the down arrow on the right and I don't see any groups searching through history. The text when I closed them said I could re-open them at any time. Where are they?

Until the most recent version(s) (at least through 148), if I have multiple windows open, the restore tab hotkey (control + shift + t) would open a closed tab in the previous window it had been closed in. Now, it opens the tab in whichever window I currently have focus on. It also used to remember the tab's previous location with regards to order among other tabs; now it opens it at the end of all tabs.

Example: I have two windows open, window A and window B. Window A has 5 tabs; window B has 10 tabs. I close tab 3 of Window B.

Old behavior: Pressing restore tab hotkey (control + shift + t) would cause the closed tab to always open in window B regardless of which window currently had focus, and would open it between tabs 2 and 4, as tab 3 again.

New behavior: Pressing restore tab hotkey (control + shift + t) will now cause the closed tab to open in whichever window has focus, A or B, and open as the last tab; for instance, if I am in window A, it will open as tab 6, if I am in window B, it will now open as tab 10, instead of tab 3.

Is there any way to restore the old behavior? At the very least, to get the windows to separate out the restore tab lists? I don't want tabs restoring to incorrect windows.

I am no longer able to pay accounts using Firefox, such as my supermarket and Govt motor vehicle registration, so I have to do that bit through another browser. It used to be okay, until recently. Supermarket is through direct debit, and car reg is by credit card. I can do the order without any problems, until the actual payment is tried, at which time I have to go to another browser and copy the URL at that stage, and pay it. What may be causing that? Thanks in anticipation. Cheers, Keith.

When I try to login with my Firefox account to configure Sync, I get a message that says that I am logged on to a different profile and asks if I want to switch. If I switch, I get the same result with the other profile. There is only one profile folder in the Profiles directory, there are no other files or folders. What should I do?

The summary says it all. Some time in the pas few days, my saved payment methods disappeared. If I try to use Add new payment method, enter my information and then save, the same things happens. It just disappears as if I hadn't done anything. Any suggestions on why it's suddenly refusing to remember my payment info?

Since the last two updates, Not including the current update as I have not downloaded it because I am sick of them, I cannot see any images on Sky news articles. There is just a white box where the images should be.

Also the back/forward buttons are useless. I do a search on Bing and click through the pages then when I , say get to page six and retype for another article the previous search doesn't exist when I use the back button. I have to remember and retype the name of the article I am looking for.

What's with all the updates recently? It is getting annoying having to update almost every week and most updates are useless and not needed for my operating system. If things were done right in the first place then all these updates would not be needed.

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.

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?????

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.