Live data from Hacker News

Firefox 60 released

mozilla.org

201–210 of 265 posts

Re: Firefox 60 released

#201
post #14

I'm glad that they have released support for the Web Authentication API. Hopefully I won't need to use Chrome for websites I choose to be more secure with. Although, with a quick look it seems like I still can't use U2F with Google on Firefox.

Me neither (FastMail and Gmail). sigh But just yesterday people tried to "educate" me that it works with 60 and for 59 I had to toggle an about:config switch. It's great that they support the proper web standard. It would be useful if all those web sites supported it. This is a long-known issue, and nobody cares about non-Chrome browsers.

I’m probably the one that will implement the Web Authentication API for FastMail and Topicbox, though it’s a some way down my list of things to do at present. I looked into it a couple of months back (I would have liked us to get it out before browsers enabled it by default), but documentation was very scarce, and so it wasn’t particularly clear what we’d need to do to migrate from u2f.js to webauthn (especially while still supporting both), and then other things came up. Since then, https://www.imperialviolet.org/2018/03/27/webauthn.html has been written, which will help, but it’d still be nice to have a concise “here’s what to do, backend and frontend, to migrate from u2f.js to webauthn” guide. If no one has by the time we support webauthn, I’ll probably write such a guide.

For now, it’s not as high a priority as it could be, because the functionality it provides is already available in Chrome (for that matter, I don’t believe Chrome’s webauthn implementation hits stable until the next release), Firefox can get it by enabling security.webauth.u2f which is good enough as a short-term measure when it’s always been required in the past anyway, and Edge doesn’t have many users (and few of them currently do 2FA). It’s pragmatism, sadly.

Re: Firefox 60 released

#202

Unfortunately, looks like the CPU spikes are still a problem on OS X for me. I check this every time a new version is released as I'd love to make the switch from Chrome, but Firefox with one blank tab and no extensions uses more CPU than Chrome with 15 actual tabs. When I actually throw activity at Firefox it hogs the CPU even more. Here's hoping v61 addresses it.

Yep, regardless of whose "fault" it is — and I totally buy that it's macOS's fault, considering how much effort my startup Cyph has to spend on working around Safari/iOS bugs — at the end of the day Firefox is unusable for me if my battery won't last for any reasonable amount of time and I have to deal with a kernel panic every other day.

Really hoping this gets sorted out soon, because on most other counts I prefer the current Firefox to Chrome. (The other thing keeping me on Chrome is pinch-to-zoom support.)

Re: Firefox 60 released

#203

I've been using Firefox Nightly as my daily browser for a while and I am beginning to notice more and more websites breaking on it - mostly Google services, although Facebook as well, recently, too. I know it's complicated by the fact that I'm on the Nightly channel, but has anyone else noticed an increase in sites that are incompatible with FF?

Nightly has been my daily driver for years, with a couple of brief interludes. There’s the very occasional possibly serious breakage, but I haven’t noticed any compatibility troubles for a long time. (But I don’t use Facebook, and of Google I only ever use Maps.)

Actually, I suppose there are a couple of sites which Tracking Protection completely broke, but that’s not Nightly-specific.

Re: Firefox 60 released

#204

Did anyone else lose the ability to scroll by clicking the middle mouse button in the 57 (Quantum) upgrade? Still missing for me in this version.

Go to Preferences > scroll down to Browsing at the bottom > check "Use autoscrolling".

Ah, that’s what autoscrolling is, is it? I wish it had some explanation of what non-obvious preferences are, at least a link to a document explaining it.

Re: Firefox 60 released

#205

The enterprise part is great to see (though it was something that seemed long overdue). I recently noticed on a Firefox mailing list that Mike Kaply (of Kaply Consulting, a company that helped with enterprise deployment and configuration of Firefox) had officially joined the Firefox team. Mike's presence is going to make Firefox in the enterprise much better. On Firefox 60, I'm still not on board with the newest vers…

It will definitely improve enterprise adoption. We're a G Suite shop, but I wouldn't mind giving our users another web browser to use if they want to.

Re: Firefox 60 released

#206
post #182

From the comparison of the lists, looks like desktop is still their focus, which points to a sad level of navel gazing for an internet company in 2018. Makes me question whether they are focused on competing with Chrome or whether they just want to make cool tech.

Desktop is where nearly all Firefox users are, all of whom immediately get the benefits of improvements to Firefox, and whose use of Firefox funds all Mozilla.

Re: Firefox 60 released

#207
post #29

Earlier quoted context omitted.

I'm unsure if this is actually Firefox fault. I'm running Linux (arch and Ubuntu), Windows and macOS, and Firefox is only slow on macOS, while my macOS machine is the second most powerful machine I have. Running Firefox in a Ubuntu VM on macOS is faster than running it natively on macOS.

Regardless who is technically at fault, the Firefox team is best placed to resolve the issue. It kind of surprises me that this is an issue at all. I was under the impression a large number of FF devs use Macbooks.

They do use a lot of Macbooks but Windows users get priority care since they're the meat of their market.

Re: Firefox 60 released

#208
post #33

Earlier quoted context omitted.

No, they could innovate by making a web browser that browses the web. Search is a prime candidate for extension functionality.

Search has been a basic part of using the web for years now. All browsers support the OpenSearch standard. Now, you may feel it would be better for a user to have to manually add Google to their search bar, but relegating search entirely to an extension is an odd suggestion.

And having installed Linux Mint a lot of times, I can tell you that having to switch from a non-google default search in Firefox is really annoying.

Re: Firefox 60 released

#209
post #53

But did they fix the weird scrolling friction on Android? Seriously, it's the main reason I don't use Firefox.

I'm using Firefox on Android - not sure what friction you're referring to here, but the lack of 'reload on pull down when scrolled to top' feature is seriously annoying for me. Despite this, I stick with Firefox because I want to use it - I can imagine that the vast, vast majority of users who have no opinion on which browser they use simply don't/won't put up with this and just go back to the easier to use Chrome. I…

These users would never install Firefox in the first place.

Re: Firefox 60 released

#210
post #7

Pocket Sponsored Stories will appear for a percentage of users in the US. Read about our privacy-conscious approach to sponsored content If you can't roll out a feature without violating EU privacy laws, you're not employing a "privacy-conscious approach."

Where does it say it's because of EU privacy laws? Could just be that they test the feature on one market first or am I mistaken?

As kibwen has commented, in Mozilla's official statement (which is legally binding), they say that they don't collect anything, so yeah.
Post reply on HN