Firefox 82
mozilla.org
mozilla.org
For Windows users, Firefox now uses DirectComposition for hardware decoded video, which will improve CPU and GPU usage during video playback, improving battery life.
neato. Websites that use flexbox-based layouts load 20% faster than before.
I haven't noticed this yet but it sounds promising.The rest of it doesn't really interest me. Picture in picture is a great feature but I don't use it because I just throw videos on a different screen to keep working.
0:https://addons.mozilla.org/en-GB/firefox/addon/twitch_5/?utm...
1. It not longer forces to restart my entire browser for an update, where every new tab I open says "restart before you can use your browser." I am not going to use a browser that closes my various windows full of API documentation once a week. I know I can disable auto-updates, but that is also not what I want: it should update when it is finally closed (like Chrome), but not update and then break my browser until I close it.
2. Individual threads can crash without taking the browser down. This feature, individually, is why most people switched and did not look back. As with the problem above. It has been requested since 2008 (http://forums.mozillazine.org/viewtopic.php?f=8&t=890085), and again in 2015 (https://support.mozilla.org/bm/questions/1092836).
Really, it's the same thing: closing my entire browser solution is an inhibitive inconvenience in my modern workflow, and Chrome never forces this action. Instead, it does everything it can to keep my tabs alive and usable. I will reconsider Firefox when they integrate this (IMO very obvious and critical) requirement. I don't care if it's faster, or uses less battery---if it regularly forces me to close all my tabs, it's unusable.
Are you on Linux? My understanding is that the distro packages exacerbate this problem, and it is less of an issue if you use the builds direct from Mozilla.
If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart.
As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one.
Frankly, and don't take this wrong way, I don't care. I'm working on other problems, and don't want to worry about what my browser is doing. I just want it to work.
> If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart.
Have you ever tried restarting it with 60 tabs open? It doesn't work on my machine.
> As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one.
I don't care if it's multithreaded to separate rendering from management for performance purposes. What I care about is keeping my remaining tabs when one crashes.
> we're hard at work on the Fission project which will move individual website domains into their own process
When this occurs, I will once again consider switching back. Though this means if one API tab breaks, they all do---it's still a massive problem.
Sounds like the current Firefox situation only because 1. Google deliberately ignores Firefox support and 2. Firefox does not support some standard APIs that even Safari supports.
The former is only Google’s bad politics while the latter is just Firefox playing catch up. Neither attributable to the monopoly.
Even if I don’t use Chrome, it’s currently the best browser by far from a user’s standpoint. This was not the case for IE6.
It's kinda like chrome all over. IE6 was faster than other browsers and supported the APIs site developers were using. From the user's standpoint it was the best browser by far.
IE6’ advantage was the ActiveX features, which were not documented nor a standard, unlike Chrome’s features.
A big feature of how chrome, firefox, and edge work today is that everyone updates to the latest version usually within days of their releases.
IE6 was still in use when IE7, IE8, and IE9 had been deployed for years with better rendering, CSS, and javascript support. Primarily because a lot of websites and internal applications had stupid things like "activex" plugins required for proper usage.
To say that chrome is the new IE6 really misses out on how horrible the internet was during the heyday of IE6. It's fairly hard to come up with a website that works well in Chrome and not so well in Firefox. Unless you are pulling out brand new CSS or JS features, you are very likely to get relatively consistent rendering between the two.
Such as?
Some people did. I complained -- at the time -- that the monoculture was harmful, and I used Firefox as my primary browser for that reason (but there were lots of sites that would only work on IE). I loved Chrome when it first showed up: a new entrant increasing the diversity and bring lots of new technical and UI innovations. But once Chrome reached the point where it dominated the browser ecosystem I returned to Firefox because I really DO think that diversity is important.
Specifically, I believe that when the largest player in the market has no more than ~40-50% market share AND there are at least 4-5 different widely-used tools, that producers of content (as well as the tool providers) will feel compelled to focus on delivering a compatible experience. But when the largest player in the market has 75% of all users, it's advantageous for content producers to focus on delivering for that platform AND it starts to be advantageous for the producer of that tool to become incompatible with other tools.
To keep the ecosystem healthy, I want to see more diversity than we have today.
There are plenty. People are just coding to Chrome instead of standards, just like they coded to IE instead of standards.
> This was not the case for IE6.
It sure was. For years. IE6 was a _much_ better browser than the contemporary Netscape versions, for example.
Like what? If there’s a standard, Chrome follows it. If there’s no standard, they propose one. They used to have a lot of custom features with prefixes, but that rarely happens anymore.
That happens to not be true all the time. Some examples off the top of my head:
* https://bugs.chromium.org/p/chromium/issues/detail?id=102719... points to various places where Chrome's security checks don't match the spec and therefore can allow things that other browsers and the spec don't.
* https://bugs.chromium.org/p/chromium/issues/detail?id=878491 -- non-spec implemetation of document.close (shared with WebKit)
* https://bugs.chromium.org/p/chromium/issues/detail?id=100027... -- broken .complete attribute behavior, broken since forking from WebKit.
Those were all found due to sites coding to Chrome instead of the standard and therefore not working correctly in Firefox.
If you want something more long-standing, https://bugs.chromium.org/p/chromium/issues/detail?id=286670 is a clear bug in selector-matching optimization that leads to incorrect behavior and just turned 7 years old.
Or you could look at https://bugs.chromium.org/p/chromium/issues/detail?id=340414
Or https://bugs.chromium.org/p/chromium/issues/detail?id=352144
There have also been multiple cases in which everyone just gave up, and changed the standard and all other browsers to match Chrome's behavior in cases where it was causing serious compat problems for everyone else.
I had a huge retail client who's customer base was largely on Win 2000/XP equipment, so they insisted on it until usage dropped off enough. Sorry I can't be more specific.
Luckily, it's not actually quite that bad yet, but I've built PWAs and some of the bugs are truly awful.
I think it was iOS 11 where the camera didn't even work in PWAs for months- we had to get people to use the website through the actual Safari browser on their phone. It wasn't actually fixed until 11.3. It was brutal.
Chrome is a good browser. When it works better than Firefox, that's because it really works better, not because it has a weird nonstandard quirk that everyone designed for because it is the dominant browser. Chrome/Blink has some quirks but it is nothing compared to IE6.
The problem with Chrome/Blink is different: is is essentially a way for Google to push whatever standard they want. Emphasis on "standard". Microsoft wanted to control the web on the client side. They made IE, and therefore Windows a near-requirement to access the web, the whole embrace, extend and extinguish thing. What Google want is the opposite, they want every machine to use Google services, and the meaning of Chrome is "here is how a web browser should be, please copy me".
Unlike Microsoft with IE, Google wants Firefox to implement every feature Chrome supports, and for that reason, these new features are much less quirky. The problem is: what Google wants Firefox to implement may not be in the user best interest.
Monopolies and monocultures are bad news anywhere, like in my city of Winnipeg where we have one of the largest elm canopies in the world which is expected to disappear in the next 10 years due to disease and infection.
Yes, during IE6's heyday, we designed for its quirks. When we moved on, we built standards-based code and then broke it to run in the lingering IE6, 7, 8...
I'm not really sure exactly what you're getting it. None of what you say is false, but if Google gets a certain share of the market, they won't care at all if Firefox goes along with it or not.
That's what I'm afraid of.
[0] https://addons.mozilla.org/en-US/firefox/addon/container-def...
For other sites yes, often just cache/cookie invalidation is enough.
It's a chicken-egg problem, basically.
The worst is when sites serve a crap version of their page to any non-chrome useragent. Many sites do this, Google being the worst offender (nearly every Google app)
I fake my user agent to recent Chrome to avoid these shenanigans. But you will get Capchas all the time because sites think you're a bot
As a Safari user on a MacBook Pro, I disagree. Safari sucks ass. I use it only because it offers the best battery longevity, but that's it.
The devtools are horrendous, the text selection is extremely bad (example: https://i.imgur.com/qC7amU1.png), extension support is awful (I only use AdGuard and LastPass and both are bad, I needed to install apps just to use them, and they frequently don't autostart).
It's also the only remaining browser that sometimes has plain wrong rendering of elements.
- Hulu app on iPad: black rectangle
- Hulu site on Safari on macOS: black rectangle
- Hulu site on Firefox on macOS: works
Now, I prefer Apple's products because they've been historically been more accessible / high performance. But Apple's recent user-hostile behavior is slowly pushing me to switch.
Would someone please shed more light on this? I work on BMC’s Remedy ecosystem and server side logging something that needs to be turned on separately.
Does FF 82 help me capture it just like that or I need to do some configuration changes on the server?
Pardon my simplistic question.
The Network DevTools already showed standard AJAX requests, and support for showing messages sent over websockets was recently added.
This adds support for another mechanism that was not previously displayed:
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
> Traditionally, a web page has to send a request to the server to receive new data; that is, the page requests data from the server. With server-sent events, it's possible for a server to send new data to a web page at any time, by pushing messages to the web page. These incoming messages can be treated as Events + data inside the web page.
Push-based server->client messaging. Exciting stuff.
Meanwhile something has got to pay for the bills. I don't think advertising for their own VPN service is too bad.
i would have, even $50. but not after they've laid off most of their servo engineers to focus the company on more idiotic moneygrabs.
there was never a way to pay for firefox. only some black hole foundation contrib that probably went to their many failed, poorly-conceived initiatives.
If I were richer, I'd pay more, and I totally understand the millions of people who don't want to pay a penny.
From having read lots of posts over the years - here and elsewhere - I get the sense it would at least be worth their while opening up some kind of donate/subscription function, for people who feel they want to help.
If I paid for Firefox, I'd perhaps be a little irked, but given I've never given Firefox a penny, I'm happy for them to try and get me to spend money on their things (even though as a Euro, I can't yet - I think the VPN's US only?).
If anyone from Firefox is reading this - please hurry up and allow me to pay for your product. I'd dearly like to!
- ed: typos
Because people want to use their browser to browse. They don't want to be advertised to while they're trying to work or otherwise get on with their hectic lives.
They also don't want to hear about silly TV shows while they're browsing.
All things Mozilla needs to learn.
Lol and Coca-Cola is delicious and refreshing so it's arguably in line to put it on the side of a bus when it goes past people who are thirsty.
I don't want your product shoved in my face, no matter how awesome you think I should find it.
I just don't get the irritation here.
My web browser is my single-most used application and I've never paid Firefox a bean for it. If they want to promote an extension to their service that they presumably feel is relevant to a percentage of their userbase, then they should go for it - even if the likes of you or I don't really care for it.
The Mr. Robot promotion was a screw up, no denying it.
Considering that was nearly 3 years ago, I think they learned.
Mozilla: not everyone watches the same TV shows as you... not everyone wants a VPN like you. Is it a diversity problem? Do they need to hire people outside their bubble?
Because ads suck.
There is no markup, it's actually about 15% cheaper.
That's one of the ridiculous parts of this: They're just reselling Swedish VPN provider Mullvad's [1] product. That product (which also supports Wireguard, yay!) is available worldwide for €5/month. You can even pay by "anonymized identifier string and cash in an envelope" if you are so inclined.
Come on, Mozilla – just keep on making the world's best browser (and the world's last free browser). Stop paying your CEO millions. Stop making bookmarking services. Stop reselling VPN services. Just act as a shovel for money to go into the pockets of talented browser developers!
So, I can finally give Firefox 50p a month! (Or whatever their share of the charge is - not a heck of a lot, I imagine).
People hate Mozilla for taking money from Google. People also seem to hate Mozilla for trying to earn money from somebody other than Google.
How do you recommend they pay for browser+engine development?
Current funding levels would go a lot further if the organization cut everything that isn't a mechanism to support the browser developers. Why does Mozilla need a CEO making millions? Why do they need a bay area HQ?
Said differently: I have no problem with how Mozilla raises money (although I do have some doubts about how much they'll make by reselling a €5 VPN service for $5, even taking into account discounts), I have a problem with how Mozilla spends money.
So you just need this sentence: "Come on, Mozilla – just keep on making the world's best browser (and the world's last free browser). Stop paying your CEO millions."
You don't need: "Stop making bookmarking services. Stop reselling VPN services."
I'm still puzzled why Moz haven't tried a paid-for Firefox option. They've gone to the bother of creating entire new paid-for products - with all the budget and product/market fit uncertainty that involves. Surely a paid-for FF option would have been a less expensive experiment?
Perhaps the terms of the Google "donation" prevent/constrain that. I wouldn't be surprised if so. Which does lead to an interesting - if probably fanciful - scenario from the anti-trust investigation announced today...
...charactertise the browser as a "utility" and require G to (a) transfer it into Mozilla's stewardship and (b) force them to license from there.
(I know: unrealistic, unworkable, lots of other "just no"s. But a fun idea nonetheless).
And sometimes without being at fault really. I remember a key moment when firefox was bleeding users was when google decided that H264 would be the standard after switching for a while and mozilla having to run after it trying to get implementations going and then still having a laggy af experience on youtube and the like because the implementation google went with was proprietary.
>I'm still puzzled why Moz haven't tried a paid-for Firefox option.
and what functionality would the paid version of firefox have? Chances are it would cause an outrage and user-loss due to cries that functionality would be premium only tbh. It would also probably make not much of a dent in the budget.
Maybe it's what it _doesn't_ have. No ads for Pocket/VPN/whatever. Maybe it comes with DDG as the default search engine. Or maybe it's pre-configured with a set of tested privacy-focused extensions.
Pro-privacy advocates might be in the minority, but it's a growing and generally vociferous minority. Mozilla's VPN offering suggests they see privacy as a market. FF is still by far their most popular offering; so I'm simply wondering why there's been no effort I'm aware of to explore the intersection of FF, privacy and revenue.
Recognising Google would most likey challenge that.
Firefox is a decent product that you get for FREE, the output of all these groups' work is free and reproducible, but you don't like a once-in-six-weeks underwriting message when a new version comes out.
This is awesome as I need to use the Total Suspender add-on to keep obnoxious web apps (like anything Google) from cranking up my CPU utilization when I am not looking at them. I am seeing a noticeable improvement.
To be fair it runs very nicely when not excessively tabbing everything, but that's just how I prefer to use the web.
And I still hate the "many tab handling" in ff where it makes me scroll.
I find this more useful than the ever shrinking tabs on Chrome. I have a hard time find a tab in Chrome once the number of tabs gets large.
It doesn't work in exactly the same way - you don't by default get a different window per-profile. Instead, tabs get a different colour for each.
You can also use Firefox's about:profiles page can to open and manage different profiles in different windows in one running instance of Firefox.
They have a years old bug they can't / won't fix that causes stock Firefox to be at 100% CPU constantly, regardless of what you are running.
I finally switched to Brave and amazingly, it manages to run basic websites at minimal CPU. And it isn't like I am running some rinky-dink computer. I have 32GB of RAM and a Ryzen 9 3900x.
EDIT: Single tab of the front page of reddit, no add-ons, nothing loading, Firefox goes between 7% and 21% CPU. Meanwhile I have 20 tabs open in Brave and it is sipping between 0.7% - 3%.
I may work on fixing this locally, but I may just stick with Brave since it works just fine.
I looked at the bug again with fresh eyes and it seems like there is a deeper issue that may be my fault.
I am running i3-wm and it seems like Firefox gets stuck in a loop if you don't have all the fonts it expects. I had a previous issue where I was crashing my terminal when a program tried to show emojis, which was a legitimately a fun issue to figure out.
https://bugzilla.mozilla.org/show_bug.cgi?id=1495900
https://bugzilla.mozilla.org/show_bug.cgi?id=1499385 (not sure if this was the one I saw before giving up + installing Brave, but the fact there are _tons_ of "Firefox hitting 100% cpu" is telling)
Is there a bug with more details on this?
I have noticed there are some websites that tend to make it both consume CPU and prevent my machine from screen-blanking, but I find them easily enough with the the diagnostics tool in ff. I don't recall having that problem with Chromium, but I feel like I've given it up for good now.
Not surprising, considering the (new) reddit website has the most bloated, sluggish UI I've ever used. And the only change they made recently made it worse as it added autoplaying livestreams.
google.com was bouncing around 1 and 3%. Firefox becomes unusable for me to do webdev on with multiple tabs if each tab is doing 5%+ each.
Chromium startup to empty page: 7 seconds. Firefox startup to page populated with tabs: 3 seconds.
It's worse though - since I don't often reboot and I have Firefox running almost all the time the effective start up time for Firefox for me might as well be zero.
Perhaps oddly, I've never perceived Firefox as slow - but I'd be the first to admit that I use it only for rather mundane purposes, so maybe there are use cases where it would be deficient.
That sounds like it's likely to be a performance issue within one or more of the add-ons. Which add-ons are you using? There may be better alternatives that don't cause performance issues.
If Firefox is fast enough for you now with your add-ons, it would be even faster with a more optimal set of add-ons.
EDIT: I see the firefox brigade is out in full force.
What was different for you that made switching permanently to Firefox acceptable this time?
I agree. I tried to switch several times since 2016. A couple of months ago, Firefox finally performed well enough I could do it. I'm the type of person who has five windows open with twenty tabs each, and it handles that now.
I also added Container Tabs Sidebar, DuckDuckGo Privacy Essentials, Firefox Multi-Account Containers (this thing is amazing for keeping sites separate!), and uBlock Origin. I like it now more than Chrome.
Ever since the Quantum updates Firefox has become faster but it wasn't very slow to begin with. Maybe it was a bit slower on some netbooks bit it hasn't been an issue on my PC.
"CVE-2020-15254: Undefined behavior in bounded channel of crossbeam rust crate" marked as high.
Once an alternative Rust compiler comes onto the scene, the language will necessarily fragment too.
> Documenting an operation as undefined behavior allows compilers to assume that this operation will never happen in a conforming program. This gives the compiler more information about the code and this information can lead to more optimization opportunities.
You refer to the ill formed code itself that violates the language specification. That's not what I meant. Yes, the fact that this code becomes garbage is a side effect of the optimizer's assumption that code is always well formed, instead of some arcane idea of punishing people who don't follow an arbitrary specification. I think we both agree.
I don't think Rust will "get to where C++ is" (whatever that means), because (outside of compiler bugs) you will not have undefined behavior unless you use "unsafe", and most Rust code doesn't use "unsafe"; the pieces that do use "unsafe" can be carefully audited (instead of auditing the whole code).
Though I do have a lot of tabs in four windows, I've set prefs so it only loads tabs when I click on them. So in reality I have a lot fewer tabs "active" on any given day. Yet I regulary see memory use grow from an initial 600MB to 4 or 5GB. FF seems not to properly release memory back, in particular after new tabs with video are closed. I might live with it were it not for the eventual slowdowns.
This might partly be due to the "one tab, one process" architecture. Of course, if you are experiencing a memory leak in Firefox, that's another story... But I can usually trace that to a memory leak in some heavy javascript "application" I have open.
With site isolation/"Fission" it looks like this isn't going to get any better in Firefox, either, as they'll have to move to "one domain/origin, one process", which could be even worse in terms of memory overhead due to the number of separate processes required.
I actually wouldn't mind if they throttled this a bit. I keep a tab or two (dozen) open to Hacker News posts I haven't gotten around to reading yet. I dread restarting the browser, as several tabs inevitably end up displaying the "Sorry, we're not able to serve your requests this quickly" page.
Someone nontechnical wrote these notes - it's Server Sent Events.
That was confusing me how the browser was seeing server events.
I just took a look at https://hn.algolia.com/?query=%22server-side%20events%22&sor..., it’s mostly (though certainly not entirely) people making this error.
/me checks what is this... then, from the draft (https://w3c.github.io/mediasession/#security-privacy-conside...):
> The API introduced in this specification has very low impact with regards to security and privacy.
Ok... my concept of privacy, may not be the same as your concept of privacy...
It's not sending anything back to the server.