Live data from Hacker News

Firefox 76

mozilla.org

61–70 of 274 posts

Re: Firefox 76

#61
post #39

Earlier quoted context omitted.

I've been using it since it was introduced. I no longer think about my passwords. Everytime I register in a new website, I just right-click -> generate secure password, it auto-fills and saves it. One password for every website. Yes, they are stored remotely with Firefox Sync. I just love this browser more and more

Can you use it as a password manager for things that are not websites as well? And is there a way to associate additional data together with the passwords, such as answers to security questions? Those were the two main things that made me use a separate password manager app in the first place.

No to both of these. There are only three fields, and they must all be filled in: URL, username, password. But suppose your bank is HSBC, you could, make up something like "securityquestion://www.hsbc.com", "mom's name", "Jane Doe".

Re: Firefox 76

#62
post #45

Whenever I start up Firefox it tells me to wait a few moments while it updates. The browser obviously doesn't care about me. It has its own agenda. This is why I won't use it.

That's very clearly because you don't open it very often. This is a once a month "issue".

Re: Firefox 76

#63

> The shadow around the address bar field is reduced in width when a new tab is opened; I mean, at least they're trying, I guess. Still seems to me like lipstick on a pig. I'm still trying to figure out what UX problem the expanding bar was intended to address.

Is it really such an issue? It really doesn't bother me at all.

Re: Firefox 76

#64

Earlier quoted context omitted.

I like it!

Seconded. I prefer it to the old design. But we seem to be the minority.

It's just the HN effect; complain about the most minute details. Firefox simply wanted it to be more obvious that the address bar is in focus the moment you open a new tab.

Re: Firefox 76

#65
post #46

Earlier quoted context omitted.

You always want to be on the latest one, because that's where the security fixes are. And if you care about what's in it just read the release notes.

You are aware of the long term support firefox esr, right? Because the existence of that invalidates the "only the latest gets security fixes!!!" argument.

looks like v68.8 is ESR... not far behind, i was hoping for v10

Re: Firefox 76

#66
i just want to say, Firefox is seriously fast now, while Chrome continues to get slower [1].

my 10M datapoint uPlot benchmark runs in half the time, for both pure js (fake data gen) and canvas workloads (chart rendering). check out the console in [2].

however, i'm still waiting for the performance assessment in devtools to improve so i can get an easy summary as i can in Chrome.

also, better default form input styling would be nice. it's so...Windows 98....but i'm on Windows 10. :\

[1] https://github.com/krausest/js-framework-benchmark/issues/68...

[2] https://leeoniya.github.io/uPlot/bench/uPlot-10M.html

Re: Firefox 76

#67

Earlier quoted context omitted.

I like it!

Seconded. I prefer it to the old design. But we seem to be the minority.

I mean, anything related to aesthetics is going to have some difference of opinion. Mozilla appears to have concluded it's the people who dislike the address bar who are a verbal minority, or they wouldn't have gone with it.

And who knows, maybe Mozilla is right—but I wonder if they've actually done large-scale feedback gathering. This isn't the sort of thing you can suss out just from looking at analytics.

Re: Firefox 76

#68
post #55

Earlier quoted context omitted.

I don't use Firefox often because of the constant updating that prevents me from using it right away. Chrome and Brave don't seem to do that, at least not in the same obvious way that Firefox does.

Ironically though, I wonder if not using Firefox much is the cause of that annoyance. In other words, Firefox usually waits for an opportune time to update, but if it's been closed for a long time, it likely decides that it's too out of date, and updating asap is critical for security. I'll reiterate my recommendation for ESR, it's Firefox but for people who want less frequent updates. :)

Firefox ESR updates on the same frequency as the mainline release, they're just more limited in scope (i.e. mostly just security & stability fixes).

Re: Firefox 76

#69
I really want to use Firefox, but they’re just stuck with so many issues, then suddenly out of nowhere they make the address bar massive.

My personal annoyance, on macOS:

Cmd+Click a link: - Safari, opens in tab in background - Chrome, opens in tab in background - Firefox, opens in tab in background

Shift+Cmd+Click a link: - Safari, opens in tab in foreground - Chrome, opens in tab in foreground - Firefox, opens in tab in foreground

Cmd+Click a bookmark: - Safari, opens in tab in background - Chrome, opens in tab in background - Firefox, opens in tab in foreground

Shift+Cmd+Click a link: - Safari, opens in tab in foreground - Chrome, opens in tab in foreground - Firefox, opens in tab in background

For some reason it’s different for the bookmarks. I opened an issue https://bugzilla.mozilla.org/show_bug.cgi?id=1597910, because really there is no actual reason to make them different, but it was closed on the basis that it might disturb the muscle memory of some users. But changing the entire menu bar is completely fine?

Re: Firefox 76

#70
post #11

Firefox made a huge mistake following in Chrome's trail with the version numbering scheme. I just don't care about Firefox 76, is it a big change? Is there some new feature I would want to try? Who knows, I'm sure Firefox 77 will be out soon though!

How is that addressed by a more traditional version number? There are many examples of major software upgrades reflected by a change in minor version number, minor software updates reflected by a change in major version number, or a major new release having less functionality than the previous version (e.g. Final Cut Pro X). With mature software like Firefox, what even is a "major change"? Calling it Firefox 13.17.6…

Firefox and Chrome already release on a fixed date schedule instead of a feature based schedule. The proposal is to simply use the date in the version directly instead of indirectly.
Post reply on HN