Live data from Hacker News

Firefox 59 released

mozilla.org

31–40 of 233 posts

Re: Firefox 59 released

#32
post #6

"Added settings in about:preferences to stop websites from asking to send notifications" Been waiting for this one.

Instead of obtruding modal, there should be just a little icon in address bar notifying that notifications are available, like some browsers used to notify about available RSS feed.

By now, you can have almost it by clicking on the (i) icon before the URL in the address bar. It lists permissions, if any, including notifications.

Re: Firefox 59 released

#33
I'm sad to say that Firefox Quantum will remain useless to me until proper session management is restored. But without even the necessary API to enable features that were provided by the "Session Manager" add-on for many years, this still seems to be a long way off.

Re: Firefox 59 released

#34
Sadly, still unusable for me since the Quantum update.

A clean install and profile, no add-ons, and google.com/maps (for example) will max out my cpu. There must be some bug related to old hardware and OS (Macbook Pro 2009 + 10.11.x) or more people would be experiencing this.

Re: Firefox 59 released

#35
Switched to FF Nightly from Chrome about 6 months ago because Chrome's memory usage was awful. Firefox has been much better, especially since I modified the following in about:config:

    browser.sessionhistory.max_total_viewers => 0
    dom.ipc.processCount                     => 1

Re: Firefox 59 released

#37

Still no proper Yukikey 2FA support. Github kinda works, Gmail still completely broken. I would love to switch from Chrome for the privacy benefits, but this is an absolute deal-breaker. Edit: There is hope for Firefox 60 or 61 -> https://bugzilla.mozilla.org/show_bug.cgi?id=1409573

IIRC it's the problem of Gmail specifically, and how they implemented 2FA. Spec-compliant sites, like Giithub, work.

Re: Firefox 59 released

#39
Firefox 59 is the first Firefox release to support SameSite cookie attribute, joining Chrome.

> Same-site cookies ("First-Party-Only" or "First-Party") allow servers to mitigate the risk of CSRF and information leakage attacks by asserting that a particular cookie should only be sent with requests initiated from the same registrable domain.

I like this one!

Post reply on HN