LWN: Comments on "Firefox 98 released" https://lwn.net/Articles/887162/ This is a special feed containing comments posted to the individual LWN article titled "Firefox 98 released". en-us Fri, 17 Oct 2025 16:20:24 +0000 Fri, 17 Oct 2025 16:20:24 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Firefox 98 released https://lwn.net/Articles/920265/ https://lwn.net/Articles/920265/ galens <div class="FormattedComment"> Thought I'd post this here in the hope that it might help others.<br> <p> I recall reading about this issue when it showed up here at lwn.net, but it really didn't register at the time. In the past few days I noticed that my Downloads directory was cluttered with *many* pdfs that I had no intention of keeping around. This caused me to investigate further, and I stumbled upon this *huge* discussion under a mozilla bug.<br> <p> &lt;<a rel="nofollow" href="https://bugzilla.mozilla.org/show_bug.cgi?id=1738574">https://bugzilla.mozilla.org/show_bug.cgi?id=1738574</a>&gt;<br> <p> To summarize, many longtime users were not pleased with the new behavior. After much back and forth, the developers relented and added an about:config setting to allow for the old workflow. If you are like me and want the old behavior, I recommend reading comment 133, where the new config setting is explained. I believe this new setting was added in version 102.<br> <p> TL;DR, set browser.download.start_downloads_in_tmp_dir to true to get the old behavior.<br> <p> </div> Tue, 17 Jan 2023 22:45:43 +0000 Firefox 98 released https://lwn.net/Articles/888195/ https://lwn.net/Articles/888195/ mathstuf <div class="FormattedComment"> My understanding is that the XUL APIs basically blocked much of the multi-process improvements because XUL extensions could &quot;bridge&quot; them and live in &quot;both&quot;. One could set up pipes and locks in such places, but I suspect that would tank performance really hard. Not to mention that multi-process lock-mediated code sounds like a nightmare to handle. I can&#x27;t say I blame them.<br> <p> However, Google is digging their own grave with the next API that hamstrings what uBlock and the like are able to do (even compared to the current extension API). AFAIK, only Edge has committed to using the change though how long the Chrome-forks can maintain it against Google&#x27;s wishes remains to be seen.<br> </div> Thu, 17 Mar 2022 08:51:59 +0000 Firefox 98 released https://lwn.net/Articles/887758/ https://lwn.net/Articles/887758/ cypherpunks2 <div class="FormattedComment"> I&#x27;m surprised that this is the first change that you have a serious problem with. I think the removal of XUL for plugins was the worst thing they could have done. It abandoned Firefox&#x27;s status as having the most powerful customization capabilities of any browser. One of my biggest criticisms of Chrome was their limited extension API, but now that Firefox invented WebExtensions, Chrome doesn&#x27;t look so bad. Many great plugins like NoScript are now empty shells of their former selves due to switching to the inferior &quot;more secure&quot; API.<br> <p> With that said, I still prefer Firefox, but only because their development model better suites me.<br> </div> Mon, 14 Mar 2022 01:35:23 +0000 Firefox 98 released https://lwn.net/Articles/887579/ https://lwn.net/Articles/887579/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; All that said, if there had been a free BSD system in 1991, Linux would not have happened, and if it had happened, it would not have gained the rapid popularity that it did. </font><br> <p> Maybe. As I have noted before and as you have adequately illustrated yourself, there is a lot of factors involved so if any or combination of them would have made enough of a difference to outpace is hard to say. I will leave it at that.<br> </div> Fri, 11 Mar 2022 10:33:58 +0000 Firefox 98 released https://lwn.net/Articles/887570/ https://lwn.net/Articles/887570/ rsidd <div class="FormattedComment"> Why didn&#x27;t FreeBSD succeed? It&#x27;s complicated but I would give several reasons (I used FreeBSD for a while in late 1990s/early 2000s on my laptop and work desktop). <br> <p> 1. As a desktop OS it was simply inferior to Linux, in terms of hardware support and also stability. It had a bug for years where you could panic the system by pulling out a mounted USB drive (or just jiggling it accidentally). Such bugs were simply not priorities for FreeBSD folks. On the server side with high-end hardware, FreeBSD is still a good choice. <br> <p> 2. The online community tended to be a bit hostile to new users, especially those who had Linux experience (&quot;eww stop the linuxisms&quot;) which probably limited their developer pool. They also fetishized &quot;real Unix&quot; despite the GNU versions of many tools being much better/nicer/more user-friendly. <br> <p> 3. The fragmentation with NetBSD, OpenBSD, and later Dragonfly BSD (a direct result of FreeBSD&#x27;s alienation of one of their most brilliant developers, Matt Dillon)<br> <p> 4. I think the Linux funnel-type model, where patches get piped via subsystem maintainers upstream eventually to a single point (Linus), has proved to actually be better than the FreeBSD collaborative model where dozens or hundreds have &quot;commit bits&quot; and can contribute directly. This resulted in less, not more, thorough vetting and inferior quality for FreeBSD. The recent FreeBSD Wireguard fiasco was evidence of it. <br> <p> All that said, if there had been a free BSD system in 1991, Linux would not have happened, and if it had happened, it would not have gained the rapid popularity that it did. <br> </div> Fri, 11 Mar 2022 01:57:42 +0000 Firefox 98 released https://lwn.net/Articles/887506/ https://lwn.net/Articles/887506/ karkhaz <div class="FormattedComment"> <font class="QuotedText">&gt; The same issue when opening in an external viewer: instead of downloading the file to a transient temporary location where it&#x27;ll get cleaned up after a while, it&#x27;s silently downloaded to ~/Downloads (even if you have configured Firefox to always ask where to save downloaded files).</font><br> <font class="QuotedText">&gt; That is: they are now treating ~/Downloads as if it was a temporary directory managed by the browser, instead of letting the user manage it.</font><br> <p> Confirmed, I get the same behavior. This annoying but at least you can choose the directory---it doesn&#x27;t have to be ~/Downloads. I&#x27;ve made it ~/tmp, which on some of my computers is mounted on a tmpfs and others not. (I also long ago deleted ~/Downloads and `chmod a-w ~`, so programs that don&#x27;t respect XDG can&#x27;t write to my home directory anyway).<br> </div> Thu, 10 Mar 2022 15:51:02 +0000 Firefox 98 released https://lwn.net/Articles/887505/ https://lwn.net/Articles/887505/ sionescu <div class="FormattedComment"> It&#x27;s sad to see how after the rollout of this feature has turned up to be a complete and utter fuckup, they keep closing the bug reports.<br> </div> Thu, 10 Mar 2022 15:41:40 +0000 Firefox 98 released https://lwn.net/Articles/887452/ https://lwn.net/Articles/887452/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; Well, the BSDs *are* &quot;the same but (arguably) better&quot; than Linux, and they couldn&#x27;t compete. So I can only conclude they are a very good example.</font><br> <p> I can look at Linux and say Linux is the same but better (part of the better is the licensing aspect - GPL (not just any permissive license) but not limited to that, plenty of other differences including the model of development) than Unix, so it serves a great counter example. So I conclude that they are a very good counter example. See my point? That&#x27;s the problem with oversimplifying things and say imitating something isn&#x27;t a competitive strategy.<br> </div> Thu, 10 Mar 2022 14:07:30 +0000 Firefox 98 released https://lwn.net/Articles/887448/ https://lwn.net/Articles/887448/ rschroev <div class="FormattedComment"> Well, the BSDs *are* &quot;the same but (arguably) better&quot; than Linux, and they couldn&#x27;t compete. So I can only conclude they are a very good example.<br> <p> Linux on the other hand was also more or less the same as the existing Unixes, but it was free while the others weren&#x27;t and that was enough of an advantage for it to succeed.<br> </div> Thu, 10 Mar 2022 14:00:24 +0000 Firefox 98 released https://lwn.net/Articles/887447/ https://lwn.net/Articles/887447/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; You make it sound like the lawsuit is an argument against rsidd&#x27;s reasoning, but as I understand it it&#x27;s rather an argument in favor.</font><br> <p> What I don&#x27;t buy his notion that &quot;BSDs are examples of why you can&#x27;t compete by just being &quot;the same but better&quot; <br> </div> Thu, 10 Mar 2022 13:52:41 +0000 Firefox 98 released https://lwn.net/Articles/887446/ https://lwn.net/Articles/887446/ rschroev <div class="FormattedComment"> Yes, the lawsuit was the major reason (or at least a very important) for the success of Linux: the practical consequence of the lawsuit was that there was no free Unix in 1991, as rsidd said. You make it sound like the lawsuit is an argument against rsidd&#x27;s reasoning, but as I understand it it&#x27;s rather an argument in favor.<br> <p> The lack of a free Unix allowed Linux to succeed, and the success of Linux made it difficult for other free Unix-y systems to flourish. The BSD&#x27;s tried, after the lawsuit was over, but by then the segment of free unix-y systems was already filled.<br> </div> Thu, 10 Mar 2022 13:35:36 +0000 Firefox 98 released https://lwn.net/Articles/887440/ https://lwn.net/Articles/887440/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; Here&#x27;s the difference: there was no free Unix in 1991</font><br> <p> So imitation can be a competitive strategy depending on context. It is so wildly successful that it is used repeatedly.<br> <p> <font class="QuotedText">&gt; And the BSDs are examples of why you can&#x27;t compete by just being &quot;the same but better. OpenBSD distinguished itself with its focus on security; but that wasn&#x27;t really enough.&quot;</font><br> <p> Let&#x27;s not kid ourselves, the lawsuit was far the major reason. If not, you will have to find an explanation of why FreeBSD didn&#x27;t succeed.<br> <p> <font class="QuotedText">&gt; If the UI is a clone of Chrome, I may as well use Chrome.</font><br> <p> Two things a) It isn&#x27;t a clone 2) If UI is the only reason holding back, you might as well as switch and move on.<br> </div> Thu, 10 Mar 2022 10:27:48 +0000 Firefox 98 released https://lwn.net/Articles/887422/ https://lwn.net/Articles/887422/ rsidd <div class="FormattedComment"> Here&#x27;s the difference: there was no free Unix in 1991. 386BSD came out in 1992, NetBSD in 1993, by that time Linux already had significant mindshare; and the BSDs were further hamstrung by the AT&amp;T lawsuit as well as their own infighting. Linux is actually a great example of how a free but (at the time) technically inferior alternative can be preferable to a horrendously expensive proprietary system. And the BSDs are examples of why you can&#x27;t compete by just being &quot;the same but better&quot;. OpenBSD distinguished itself with its focus on security; but that wasn&#x27;t really enough. <br> <p> Firefox is competing with free-beer Chrome and free-speech Chromium. Many Firefox users, including me, use it because we like its UI better, and we put up with minor incompatibilities. If the UI is a clone of Chrome, I may as well use Chrome. <br> </div> Thu, 10 Mar 2022 08:39:04 +0000 Firefox 98 released https://lwn.net/Articles/887421/ https://lwn.net/Articles/887421/ oldtomas <div class="FormattedComment"> Your snark is very clever. But useless, perhaps even contraproductive.<br> <p> Of course, &quot;they use Chrome&quot; could be characterized as hyperbola. Perhaps it is even unfair, I don&#x27;t know.<br> <p> But it points at a real problem [1]. And you contribute to hiding it with your snark.<br> <p> C&#x27;mon. You are smarter than this.<br> <p> [1] I think Firefox losing &quot;market share&quot; is a symptom of that problem.<br> </div> Thu, 10 Mar 2022 08:32:37 +0000 Firefox 98 released https://lwn.net/Articles/887413/ https://lwn.net/Articles/887413/ sionescu <div class="FormattedComment"> I opened <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1758844.">https://bugzilla.mozilla.org/show_bug.cgi?id=1758844.</a><br> </div> Thu, 10 Mar 2022 04:46:53 +0000 Firefox 98 released https://lwn.net/Articles/887382/ https://lwn.net/Articles/887382/ dskoll <p>I actually prefer this download flow, though it did take a bit of time to get used to it. Wed, 09 Mar 2022 22:05:53 +0000 Firefox 98 released https://lwn.net/Articles/887373/ https://lwn.net/Articles/887373/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; Linux&#x27;s strategy was NOT to imitate Unix.</font><br> <p> I will still stick with it did largely imitate Unix. A few exceptions doesn&#x27;t change that<br> </div> Wed, 09 Mar 2022 20:27:59 +0000 Firefox 98 released https://lwn.net/Articles/887366/ https://lwn.net/Articles/887366/ milesrout <div class="FormattedComment"> Linux&#x27;s strategy was NOT to imitate Unix. For example, Linux could have scored some easy compatibility points by implementing the STREAMS API. However, that API was rubbish for performance and Linus famously refused to have it in his tree.<br> </div> Wed, 09 Mar 2022 19:47:56 +0000 Firefox 98 released https://lwn.net/Articles/887355/ https://lwn.net/Articles/887355/ flussence <div class="FormattedComment"> Limited space in /home/ is one problem, limited tmpfs space is a problem too (Firefox treats /tmp and /dev/shm like infinite free scratch space and it goes off the rails when they&#x27;re reasonably sized).<br> <p> There are a few good (technical, security) reasons to want to keep all data in the user&#x27;s homedir, but I get the feeling those weren&#x27;t a factor in this change.<br> </div> Wed, 09 Mar 2022 18:42:08 +0000 Firefox 98 released https://lwn.net/Articles/887344/ https://lwn.net/Articles/887344/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; It can be that people just don&#x27;t recognize that imitating the competition is not a winning strategy</font><br> <p> Hmm, I guess that is why Linux&#x27;s strategy of largely imitating Unix lost so heavily. If only there was more to a web browser than the UI, the chrome if you will. <br> </div> Wed, 09 Mar 2022 17:21:23 +0000 Firefox 98 released https://lwn.net/Articles/887327/ https://lwn.net/Articles/887327/ rsidd <div class="FormattedComment"> It can be that people just don&#x27;t recognize that imitating the competition is not a winning strategy. If you are catering to people who want chrome-like features, well, they&#x27;re already using chrome and it&#x27;s more compatible with most of the web. Why drive away those who like firefox for what it is?<br> </div> Wed, 09 Mar 2022 16:19:53 +0000 Firefox 98 released https://lwn.net/Articles/887310/ https://lwn.net/Articles/887310/ rahulsundaram <div class="FormattedComment"> <font class="QuotedText">&gt; Of course they don&#x27;t. They use Chrome. That&#x27;s the only explanation that makes sense for me for why they seem to want to turn Firefox into Chrome.</font><br> <p> Yes indeed, it just can&#x27;t be that people have strong and differing UI preferences, that feels too pedestrian, it must be that they are secretly Chrome lovers who happen to be working on Firefox. Perhaps they work for Mozilla in the day and Google in the night. Given the inflation hikes, that would be a good economical decision.<br> </div> Wed, 09 Mar 2022 14:35:10 +0000 Firefox 98 released https://lwn.net/Articles/887268/ https://lwn.net/Articles/887268/ cesarb <div class="FormattedComment"> Unfortunately, there&#x27;s no way to get the old behavior back. I tested it yesterday.<br> <p> If you configure PDF files to &quot;always ask&quot;, and when it asks you answer to &quot;open it in Firefox&quot; this time, it&#x27;ll silently download the file to ~/Downloads (even if you have configured Firefox to always ask where to save downloaded files!), and then open it in a new tab. This is different from what happens when you configure PDF files to &quot;open it in Firefox&quot;, since in that case it opens the built-in PDF viewer and loads the file in it without saving it to ~/Downloads.<br> <p> The same issue when opening in an external viewer: instead of downloading the file to a transient temporary location where it&#x27;ll get cleaned up after a while, it&#x27;s silently downloaded to ~/Downloads (even if you have configured Firefox to always ask where to save downloaded files).<br> <p> In the end, this will lead to ~/Downloads becoming full of random junk (which would normally end up on /tmp, but at least /tmp is automatically cleaned).<br> <p> It&#x27;s even worse if the reason you set up Firefox to always ask where to save is because you don&#x27;t want anything to end up in ~/Downloads unless you explicitly put it there, either because you&#x27;re afraid of it silently overwriting files there with the same name (which IIRC had been an issue some time in the past), or because just placing files there could lead to a security vulnerability (less of an issue on Linux, but on Windows where the DLL search path includes &quot;the directory where the EXE file is located&quot;, this could easily be a problem), or because you have limited disk space on your /home partition (for instance, it&#x27;s mounted via NFS from a file server with strict quotas, which was the case on the computer lab at the university I studied at).<br> <p> That is: they are now treating ~/Downloads as if it was a temporary directory managed by the browser, instead of letting the user manage it.<br> <p> I won&#x27;t stop using Firefox as my main browser, but this is probably the first change in all the time since it was still called Netscape Navigator that made me reconsider.<br> </div> Wed, 09 Mar 2022 14:34:31 +0000 Firefox 98 released https://lwn.net/Articles/887264/ https://lwn.net/Articles/887264/ milesrout <div class="FormattedComment"> <font class="QuotedText">&gt;wondering if those who invent these &quot;improvements&quot; ever use the browser they develop</font><br> <p> Of course they don&#x27;t. They use Chrome. That&#x27;s the only explanation that makes sense for me for why they seem to want to turn Firefox into Chrome. <br> <p> What they don&#x27;t seem to understand is that if they turn Firefox into Chrome, nobody will use Firefox, because if they wanted to use Chrome, they&#x27;d just use Chrome...<br> </div> Wed, 09 Mar 2022 11:32:09 +0000 Firefox 98 released https://lwn.net/Articles/887256/ https://lwn.net/Articles/887256/ wtarreau <div class="FormattedComment"> I&#x27;m scared already. *Every* single time they announced an improved user experience, for me it was a painful regression, to the point that I&#x27;ve always been seriously wondering if those who invent these &quot;improvements&quot; ever use the browser they develop (honestly I don&#x27;t think so, or that would indicate some form of masochism). <br> <p> I find it amazing that seeing how their market share drops doesn&#x27;t ring a bell somewhere that maybe they&#x27;ve caused this themselves by trying to constantly imitate competition instead of continuing to focus on what users *want*. Nowadays I&#x27;m spending most of my time trying to figure what tab is active because they seem to find it funny to make important stuff as invisible as possible. After every upgrade I&#x27;m wondering if it&#x27;s still worth using that browser or if they crossed the point of no return.<br> <p> Well, let&#x27;s not start to fear the update again, we&#x27;ll see...<br> <p> </div> Wed, 09 Mar 2022 07:42:36 +0000 Firefox 98 released https://lwn.net/Articles/887253/ https://lwn.net/Articles/887253/ rsidd <div class="FormattedComment"> I have not yet upgraded, so hopefully you are correct. <br> </div> Wed, 09 Mar 2022 06:34:27 +0000 Firefox 98 released https://lwn.net/Articles/887252/ https://lwn.net/Articles/887252/ firasha &gt; Apparently there is no way to get the old behaviour back.<p> I don't think that's true, at least according to Mozilla's <a href="https://support.mozilla.org/en-US/kb/manage-downloads-preferences-using-downloads-menu">Manage Downloads preferences using the Downloads menu panel</a> page. See the section <b>I want to configure a different behavior for some files. How do I do that without the dialog?</b>: "<i>This is where you can customize download actions for different file types as before, such as having Firefox always ask what to do when you download that type of file</i>." Wed, 09 Mar 2022 06:33:14 +0000 Firefox 98 released https://lwn.net/Articles/887249/ https://lwn.net/Articles/887249/ rsidd <div class="FormattedComment"> The old download flow was a significant plus point of firefox vs chrome for me. Sometimes I want to save a PDF, sometimes open it in firefox, sometimes open it in another program. I don&#x27;t want firefox to assume that what I last did is what I always want. Apparently there is no way to get the old behaviour back. This is not user-friendly. <br> </div> Wed, 09 Mar 2022 05:52:24 +0000