Since it seems #Google has decided to uni-laterally force through their new anti-#adblock #DRM euphemistically named "Web environment integrity", I decided to add a little bit of code to my website that blanks out the page and displays a protest message with a link to the firefox download page when ...
Since it seems #Google has decided to uni-laterally force through their new anti-#adblock #DRM euphemistically named "Web environment integrity", I decided to add a little bit of code to my website that blanks out the page and displays a protest message with a link to the firefox download page when you visit it from a browser with this DRM feature. Here's the source inside one toot, feel free to copy and put it at the end of your website's before the closing tag:
If Firefox is using an unexpected amount of RAM, report a bug by following the steps below:
- Open
about:memoryin a new tab. - Click Measure and save...
- Attach the memory report to a new bug
- Paste your
about:supportinfo (Click Copy text to clipboard) to your bug.
If you prefer not to open a bug, you can instead reduce the number of content processes used by Firefox to a lower amount by going to about:config and changing dom.ipc.processCount.webIsolated to a lower number.
With Firefox 115, users on Windows 7, Windows 8 and Windows 8.1 will automatically be moved to the Firefox Extended Support Release (ESR).
With Firefox 115, users on Windows 7, Windows 8 and Windows 8.1 will automatically be moved to the Firefox Extended Support Release (ESR).
Please help, I cant watch videos!
You could always disable hardware video decode acceleration and continue to watch videos.
I just compared the behavior in both Chromium and Firefox on my machine, and as far as I can tell, they act the same.
Steps to reproduce:
- Open a video: https://www.youtube.com/watch?v=erQ_9yEz0ls
- Play the last 10 seconds
- Click "replay" button in the YouTube player
What happens:
The buffer is cleared in both browsers.
What are you seeing that is different?
On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵
On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵