Firefox: форум сообщества

While playing chess at lichess.org, browser power management inhibit messaging to the system gets stuck on its current status. That is, if power management is inhibited by media playing on another tab while I play a game, it will get stuck in the inhibited state. If power management is uninhibited while I play (no media playing), it will get stuck in the uninhibited state. This persists until the browser is restarted even if all tabs are closed.

I don't believe it to be a system issue, as the problem clears as soon as the browser is closed. Chrome based browsers do not exhibit the behavior for me, but I tried a Firefox fork (LibreWolf) and it has the same issue. I don't experience this issue at any other website I visit.

Only certain areas of lichess.org cause this behavior, primarily playing a game against a human opponent. I tried progressively blocking media and script requests to narrow down offenders, but I always break site functionality before I can pinpoint anything.

I'm not so much looking for a solution (although that would be great) as I am troubleshooting advice. Is there any way to narrow down exactly what it is about this specific website that is causing the issue?

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!

I am using 147 ESR and when I go to permissions and block all cookies for the site plex.tv the cookies are not blocked. If I go to the URL field and select the lock, it shows "clear cookies and site data" which means the cookies have being accepted.

Why are the cookies accepted from the site when I have set cookies "blocked"

at present it is 32bit Llnux Firefox ChaletOS. It appears it wants 64bit Linux but every time it only allows me access to 32bit version which tells me is out of date. What is happening?

this is nice feature

what if this translation could be run a standalone tool, command, or you call an api to translate something locally?

then we would be able to translate documents, mail, .. maybe just in html and plain text (with or without markup) format

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

In a thread discussion about the flag, "browser.tabs.unloadOnLowMemory" dated 23-Nov-2022 (https://news.ycombinator.com/item?id=33706117) it was mentioned that we've disabled tab unloading on Linux because low-memory detection just didn't work.

Has the issue been fixed? Does the low-memory detection work in Linux? Can it be enabled now?

Does it get triggered when SWAP is being used? Or when system free RAM falls say to about 25% of total physical RAM?