Installing the Go European extension gives me the nudges I need to, well... go European.

Installing the Go European extension gives me the nudges I need to, well... go European.
bizarre problem with #firefox -- my right click menu suddenly has like 100 broken options, including random unused spaces and dividers. video options for no video. nothing works anymore when i click it, either, not even "open in new tab." two "copy" and two "paste" sure yep
The Joy of Coding returns today with Episode 398! Come join me while I #livehack on #firefox !
Yes, after a few weeks of planned and unplanned absences, I'm back - we're going to continue our exploration of building a Rust component that we can share between Firefox Desktop, Firefox for Android and Firefox for iOS. Exciting!
Even more exciting is that I'm still very much a Rust novice.
Come watch me stumble through it! Starts at 1PM ET:
Plus ça va, plus je travaille quasi-intégralement au sein d'un navigateur web. Pas le seul j'imagine.
Tout ça pour dire que le gain de productivité apporté par les onglets horizontaux, le partage entre équipements et surtout les conteneurs (
#firefox
It's a bit annoying that none of the main web browsers out there (tried Firefox, Epiphany, Chromium) respect "canonical" link elements (RFC 6596) to get the official page URL (without all the decorative or tracking garbage) for proper bookmarking without duplication.
My enhancement request in #GNOMEWeb: https://gitlab.gnome.org/GNOME/epiphany/-/issues/2379
In #Firefox, to work around https://bugzilla.mozilla.org/show_bug.cgi?id=502418 I had to install an extension: https://addons.mozilla.org/firefox/addon/canonical-link/
@sjmulder : door verschillende browsers te gebruiken heb ik daar minder last van. Vooral Firefox met NoScript (meestal op mijn Android smartphone) geeft mij enorm veel rust. Soms kan ik pagina's met paywall geheel of grotendeels lezen (zie screenshot).
Je hebt wel een leercurve voor NoScript en Firefox heeft ook nadelen (zie bijv. https://infosec.exchange/@ErikvanStraten/114341143568071368 en de follow-up toot over NoScript).
Vaak werkt het als je de primaire partij toestemming geeft om JavaScript uit te voeren, maar derde partijen niet toestaat (waaronder 3rd parties met namen waar "cookiebot" in vóórkomt).
Firefox Focus ondersteunt geen NoScript, maar is het meest privacy-vriendelijk doordat alle geschiedenis gewist wordt bij het sluiten van de browser. Sowieso belangrijk, maar in deze browser helemaal (omdat HSTS niet werkt): zet "https only" aan. Dat betekent dat je *gewaarschuwd* wordt bij onveilige http-verbindingen, die je vervolgens wél kunt toestaan.
Wat ook helpt is als tooters geen "URL-verkorters" gebruiken, zodat je kunt zien naar welke website de link leidt.
Ten slotte probeer ik vaak het m.i. belangrijkste stuk te quoten, of een screenshot te plaatsen (zo mogelijk mét Alt tekst). Dan HOEVEN lezers niet op links te klikken/drukken.
(whispering) apparently #firefox's english dictionary doesn't know that "taekwondo" is a real word, it suggests changing it to "wonderland" for some reason
(still whispering) don't let it find out i said that, i don't want it to get mad at me, after all it still knows "karate", "judo" and "jujitsu"
#Phoenix #Firefox 2025.04.15.1 is now available - go update! :)
https://codeberg.org/celenity/Phoenix/releases/tag/2025.04.15.1
I just solved (but not yet fixed) a really "fun" rendering bug.
I'm working on a web game engine, with a focus on "per-pixel" rendering (think PICO-8). So, to load a spritesheet or a font, it reads the .png file, draw it on a canvas, and fetch the pixel data from that canvas. This is the most straightforward way to read an image pixel per pixel.
Except that when I use that image data to draw sprites or print some text, there are stray pixels all over (image 1). This bug only happens in Firefox; the rendering is perfect on Edge. With that information, you might already have solved the case.
When debugging, I find that it is indeed the `context.getImageData()` that is returning slightly different values in Firefox. The stray pixel on the cursor is supposed to be a perfect black (0, 0, 0, 255), but it is actually (2, 0, 0, 255)
So while I'm banging my head and cursing Firefox, I also notice - in a totally unrelated way - that the hot reloading of my game is much faster on Edge. I try an incognito window in Firefox, and surprise! the rendering is different (image 2).
Found it yet? Is it a plugin? Nope, it's the built-in anti-tracking feature from Firefox. It messes with the canvas rendering to reduce fingerprinting. It's imperceptible for the human eye, but totally breaks your code if you rely on some expected precise values.
Guess I'll have to find another way to read my images
Y'all, did you see that *a single volunteer* contributed the entire Temporal implementation to #Firefox?
Temporal is a huge spec. Amazing work by André Bargull.
https://spidermonkey.dev/blog/2025/04/11/shipping-temporal.html
Mozilla veröffentlicht neue Firefox-Versionen
Die Entwickler des Mozilla Firefox haben die neue Version 137.0.2 und die Version ESR 128.9.0 veröffentlicht und darin auch wieder Sicherheitslücken behoben. Wie immer sind in diese Updates auch viele Veränderungen eingeflossen. https://kantel.github.io/posts/2025041501_firefox_updates/ #Mozilla #Firefox #Update #Security
I am very stressed at the moment, so I will go ahead and organize my bookmarks.
#New webpages that offer lite versions, with no images, are great. I prefer #CanadianNews whenever possible. I rank my 3 lite news page sources as
1. #CNN
2. #NPR
3. #CBC
CNN offers a nice long list of news to read, their page is ugly but works so nice with #FireFox reader view.
NPR has less news is great layout on its own and good in reader view.
CBC is my preferred news source, and it is the most flexible but, it does not work in reader view.
www.cbc.ca/lite
www.lite.cnn.com
www.text.npr.org
Mozilla released #Firefox version 137.0.2. https://www.mozilla.org/en-US/firefox/all/
Ich wollte mir gerade die Webseite von #minisforum ansehen. Das klappte mit #firefox nur, wenn ich alle möglichen Script- und Tracking-Detektoren deaktiviert hätte. Puh ...
Dann habe ich #google #chrome gestartet und siehe da, die Webseite wurde (natürlich!) ohne Murren dargestellt. Mit allen möglichen Scripten im Hintergrund. Dann habe ich den Browser gleich noch aktualisiert.
Eines muss man Chrome ja lassen. Der Browser ist im Vergleich zu allen anderen schon sehr schnell. Und sammelt Daten