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:memory
in a new tab. - Click Measure and save...
- Attach the memory report to a new bug
- Paste your
about:support
info (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).
Please help, I cant watch videos!
You could always disable hardware video decode acceleration and continue to watch videos.
Please report issues: https://firefox-source-docs.mozilla.org/performance/reporting_a_performance_problem.html
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?
Maybe you are already a Firefox user, we are part of a minority on the web today, and think that this text is not for you. You’re probably right, but I’d like to make a few points here and ask for your help in taking the web back before it’s too late. And if you don’t use Firefox, you’ve been using ...
![Take Back the Web](https://lemmy.blahaj.zone/pictrs/image/NKXCQuMznR.webp?format=webp&thumbnail=256)
Maybe you are already a Firefox user, we are part of a minority on the web today, and think that this text is not for you. You’re probably right, but I’d like to make a few points here and ask for your help in taking the web back before it’s too late. And if you don’t use Firefox, you’ve been using some version of Chromium (Chrome, Edge, Opera, Brave or Vivaldi) a few years ago this wouldn’t necessarily be a bad thing, but today it’s bad for the health and freedom of an web that respect privacy and is not controlled by capitalist corporations, the so-called Big Techs.
Attached: 1 image May and June were good months for Firefox's Speedometer performance compared to Chrome. We're closing in while Chrome seems fairly static. In this visualization, lower in the graph is better. From https://arewefastyet.com/win10/benchmarks/overview?numDays=60.
![Mike Conley (:mconley) ⚙️ (@mconley@mozilla.social)](https://lemmy.blahaj.zone/pictrs/image/IsTbppbV8M.png?format=webp&thumbnail=256)
May and June were good months for Firefox's Speedometer performance compared to Chrome. We're closing in while Chrome seems fairly static. In this visualization, lower in the graph is better. From https://arewefastyet.com/win10/benchmarks/overview?numDays=60.
21 years ago this summer Firefox got real. For some months it was mostly just tinkering, but with Blake's internship and collabs with Hyatt, PCH contributing, Hewitt getting more involved, Kerz, myself and a couple others working on theme stuff, things were getting serious.
MDN is launching a code Playground. Users can prototype ideas and expand all live samples into an interactive experience.
![Introducing the MDN Playground: Bring your code to life! | MDN Blog](https://lemmy.blahaj.zone/pictrs/image/fsvQvI0jyi.png?format=webp&thumbnail=256)
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 - Firefox - Fedia](https://lemmy.ml/pictrs/image/ef7c59c2-65f1-481f-b567-c93204dc22c0.png?format=webp&thumbnail=256)
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 - Firefox - Fedia](https://lemmy.ml/pictrs/image/41a59cf1-8f6a-4252-bcd8-ca8912f3027f.png?format=webp&thumbnail=256)
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 ...