Φόρουμ κοινότητας «Firefox»

I need to have a telecon from the provider meet.goto.com using Firefox on my PC running Linux Mint mint-001-1.0 147.0.1 (64 bit) but I get an error message browser not supported. What can I do? Thanks

After tinkering with about:config (shouldn't have...) the background of every page that does not specify a body background color turns the color of my theme background color.

Using the firefox color pipette says its white, but it clearly isn't.

The theme i have is dark, making any page that expects the background to be white unreadable (without DevTools -> Body -> background-color: white)

I haven't been able to find the config that fixes it.

I often hit ^T (control-T) in firefox without meaning to, because I use that chord in other applications a lot. In firefox it opens a new tab, which is almost never what I want. I'd like to suppress that keyboard shortcut. I tried doing it using vimium (unmap <c-t>) but that has no effect.

Thank you, Silvio

Hi Mozilla,

i stumbled upon an extension called 'unhook' which allows to hide a wide selection of content from my view on youtube. This is amazing! Now I can watch my favourite channels without annoying stuff on every side. I would really appreciate to have something of this kind as a native feature in Firefox. So please consider this a suggestion right away or point me towards the place where I can suggest this feature correctly - if there is such.

Thanks a lot for Firefox!

After many years of using Firefox and then trying other browsers I decided to stick with Firefox now, and immediately I encounter a persistent flaw.

Mainly I browse on chess.com, I mention this because there the thing occurs and I can imagine it is quite a 'complicated' website. Stick with me. I administrate clubs and play chess there so open pages regularly, in new tabs, still generally only three simultaneously.

Every 1 in 5 times the page just gets stuck loading. Only parts appear and the little refresh icon up there doesn't show because the X stays (the one to stop loading the page). This is quite annoying. Simply by refreshing it immediately loads properly. But it is ridiculous to keep having to press F5 every couple of minutes before one can get on. As I also used Beta channel on my win11 machine I figured maybe it's that but after several updates it persisted. Now I am using the Normal channel and a Linux Mint OS and exactly the same keeps happening. I have tried a dozen remedies. Like adding an exception to the enhanced tracking in Firefox and several others and nothing fixed this. Does anyone knows how this happens?

And will Mozilla fix this? Or is it completely at the bottom of priorities because it is site specific?

Thanks for any replies (OS most recent Linux Mint Cinnamon. browser version mint-001 1.0 firefox 147.2) (Happened on Windows 11, Firefox Beta as well)

I am unable to sign in to my yahoo mail account. It gives me a fault that "something went wrong, please try another device". I can use brave as my browser and sign in with no problem but not with firefox. Any idea why?

The latest versions of Firefox (and Tor) are still fixed and work successfully in Windows 7, and this is still relevant.

After all, the Firefox team can also release updated versions, right?

https://github.com/Blaukovitch/Mozilla_Firefox_Windows_7/releases

NB - For the past half a year I have to sometimes right click to interact with them, anyway

Effectively, I will interact with the extension at the most basic, normal level on something that has interactive elements like a dropdown menu, or basic options.

I will click / right click on the icon and the highlight will appear, then that's it ... the browser then crashes and does not recover. :(

What's worse is that I have to Force Quit and when I restart there is no crash report to send to Moz.

I am just wondering if other Linux users have experienced similar issues.

The attached image is taken at the moment before the 'Force Quit' dialogue opens up in Debian 12 Gnome (Wayland) ...

I have Hardware Acceleration on.

I am about to start testing with it off, but I work from the browser, and do not want performance compromises. So that is (at best) a work-around, and certainly is not a fix.

I'm on version 147.0.2 (64-bit) which would appear to be from the Mozilla Firefox Debian Package mozilla-deb - 1.0 install/repo/whatever ... and the PC specs are: Processor: Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz Memory: 32705MB (11893MB used) Resolution: 7680x2358 pixels OpenGL Renderer: Quadro RTX 3000/PCIe/SSE2

These are my media. prefs ... but ... I doubt that it is relevant: media.ffmpeg.allow-openh264 true media.ffmpeg.customized-buffer-allocation true media.ffmpeg.disable-software-fallback false media.ffmpeg.enabled true media.ffmpeg.encoder.cpu-used 7 media.ffmpeg.encoder.enabled true media.ffmpeg.encoder.quantizer-max 35 media.ffmpeg.encoder.quantizer-min 10 media.ffmpeg.vaapi.force-surface-zero-copy 2

They play for a couple of seconds, then the panel they are playing in goes black. They used to work a month or two ago. Videos play fine in YouTube. They also play fine in apps like VideoPlayer and VLC. They play fine in Chromium based browsers Opera, Brave and Vivaldi. My graphics card requires switching acceleration off. I can’t find a switch for that in Firefox.

Problem Videos start playing, then after a few seconds the video panel turns black. Audio may continue. Refreshing does not help.

Environment

   OS: Fedora Linux 43
   Firefox 147.0.1 (also tested Firefox Flatpak)
   Display server: Wayland and X11 (both tested)
   Hardware acceleration: on and off (tested)
   Media Source Extensions: enabled (disabling MSE triggers an “unsupported device” error)

What works

   BBC News videos play correctly in Chromium-based browsers (Brave, Vivaldi)
   Videos play correctly in mpv/VLC
   Other video sites (e.g., YouTube) play correctly in Firefox

What I’ve tried in Firefox

   Disabling hardware acceleration
   Disabling VA-API
   Disabling WebRender
   Disabling RDD sandbox
   Running Firefox under X11
   Using the Firefox Flatpak build

None of these measures help. This suggests the issue is related to Firefox’s interaction with BBC’s player on Linux. Has anyone else seen this, or is there a known workaround?