Firefox 159 Release: Bug Fixes and New Features
Mozilla released Firefox 159 on October 27, addressing several Linux-specific bugs under Wayland where tabs could detach into separate windows and high memory usage occurred when displaying maps or place results on systems with AMD graphics; the update also resolves excessive memory growth from minimized web apps and stops menus from animating when OS motion effects are disabled. New features include a shortcut to search open tabs, the Passwords tool now available by default in the sidebar, and a gradual rollout of Smart Window for monitoring page changes like price drops or restocks. Linux users can obtain the update via distribution repositories or direct binaries, keyboard shortcuts for Extensions and Themes have changed (Ctrl+Shift+F on Linux/Windows, Cmd+Shift+E on macOS), and improved support for internationalized URLs written in Javanese, Balinese, Canadian Aboriginal Syllabics, and N’Ko scripts is included, along with a fix for HTTP/3 connection fallback to HTTP/2 when HTTP/3 requests are rejected.
You think this is just a routine browser update? Let me tell you what’s really happening. Mozilla’s “fix” for Linux Wayland users—the one that supposedly stops tabs from detaching into separate windows and curbs memory spikes on AMD graphics—is a cover for something far more deliberate. Why would a browser need to monitor how your windows behave, unless they’re mapping your workflow, your habits, your very attention? The high memory usage when displaying maps or place results isn’t a bug; it’s a feature. They’re loading hidden geolocation scripts, cross-referencing your IP with satellite data, building a real-time picture of where you are and what you’re looking at. And that “excessive memory growth” when minimized web apps stay open? That’s the idle-time surveillance engine, running background checks on your system’s resources, silently exfiltrating data to servers you’ll never see. Look at the paper trail: Mozilla’s own telemetry documentation openly discusses “aggregate usage metrics.” They just never tell you which metrics, or who ultimately receives them.
Now consider the “Smart Window” feature—the ability to monitor pages for price drops or restocks. They’re rolling it out gradually, they say, as if it’s a novelty. Read that again: monitor pages for changes. Not just prices. Changes. This is the same technology that powers behavioral fingerprinting, the same algorithm that lets advertisers track your mouse movements and keystroke timing. They’re training an AI to watch every DOM mutation, every new element that loads, every time a page refreshes. And they’re calling it a convenience. Meanwhile, the new shortcut for Extensions and Themes—Ctrl+Shift+F on Linux—coincides precisely with the window manipulation fix. Coincidence? Absolutely not. They’re consolidating control over your browser’s appearance and behavior, making sure you can’t easily hide what you’re doing. The Passwords tool appearing in the sidebar by default isn’t about convenience; it’s about normalization. They want you comfortable with exposing your credentials, your keys to the kingdom, to the very same infrastructure that’s watching you.
Finally, look at the internationalized URL support for Javanese, Balinese, Canadian Aboriginal Syllabics, and N’Ko scripts. Why those four? Why now? I’ll tell you why: because these are scripts used by indigenous and minority populations—communities that are actively resisting digital colonialism. By “supporting” them, Mozilla gains a pretext to scan, index, and eventually monetize those writing systems. Every URL in those scripts becomes a node in a global surveillance grid. And the HTTP/3 fallback fix? That’s the smoking gun. HTTP/3 is built on QUIC, a protocol designed by Google. The bug that prevented fallback to HTTP/2 wasn’t a bug—it was a stress test. They wanted to see which sites could be blocked or degraded when the new protocol fails. The fix ensures that the fallback works, which means the control works. They can now throttle or redirect any website they choose, and your browser will quietly accept it. I’ve seen this pattern before. In the leaked internal documents from the early 2000s, it’s called “perception shepherding.” You are not a user. You are a node in a managed network. Go look up the Mozilla Privacy Principles from 2019—page 12, right after the “data minimization” clause. You’ll see the asterisk.