Firefox 59 released • Hacker News Board

Re: Firefox 59 released

#81

Post by odabaxok » Tue, Mar 13, 2018, 3:21 PM UTC

rebelwebmaster wrote: post #75

odabaxok wrote: post #49

Earlier quoted context omitted.

I cannot see it there. https://postimg.org/image/59fqo4pfx/

Did screenshots somehow get disabled? In about:config, check the value of the extensions.screenshots.disabled pref.

No it was never disabled. Also, I have tried to disable it and enable it again and restart the browser and similar things...

Re: Firefox 59 released

#82

Post by mikepurvis » Tue, Mar 13, 2018, 3:21 PM UTC

sutoor wrote: post #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.

I think I must be hitting something like this too— Mid 2014 MBP running 10.11.6. I tried Quantum when it came out and used it exclusively for about a week, but there were just a myriad of small problems around performance. It would eat CPU and RAM, input would lag especially text entry, Hangouts didn't work, etc. And then on top of that a bunch of annoying interop issues like problems with the 1password extension ("the add-on could not be downloaded because of a connection failure"), not being able to right-click selected text and access the Services menu.

I really want to love Firefox, and I'm giving it another try with 59, but at the end of the day I need my computer to work for me. :(

Re: Firefox 59 released

#83

Post by Kliment » Tue, Mar 13, 2018, 3:22 PM UTC

proaralyst wrote: post #65

childintime wrote: post #45

Sadly no news on the Web-extensions front. Several of my extensions continue broken.

What news are you looking for? I'm fairly sure extensions targeting the older APIs will not be supported in any future release.

We're waiting for the webextensions API to be extended with a bunch of missing functionality so that extension authors can reimplement things that were made impossible when the older APIs were deprecated. This is something that ideally should have been done before or shortly after the quantum release but was not seen as a priority.

Re: Firefox 59 released

#84

Post by Silhouette » Tue, Mar 13, 2018, 3:24 PM UTC

childintime wrote: post #45

Sadly no news on the Web-extensions front. Several of my extensions continue broken.

That's unfortunate. I finally gave up on Firefox as my main browser when 57 came out, and one of the big reasons was that so many of the useful extensions that had set Firefox above other browsers for me were broken and didn't have good replacements. In some of those cases, my understanding is that you can't currently write a direct replacement because the new API doesn't support the required functionality. I was really hoping that by two releases later these kinds of issues would have been addressed and new Firefox would at least not be worse than old Firefox in this respect. :-(

Re: Firefox 59 released

#85

Post by purerandomness » Tue, Mar 13, 2018, 3:24 PM UTC

the_grue wrote: post #67

John_KZ wrote: post #52

Firefox is dead to me ever since they killed their addons and marketed it as a step forward. If I wanted to use Chrome I'd use fucking Chrome.

I don't know why you are being downvoted. I have the same problem. I'm still stuck with Firefox 56 and no upgrade path in sight. I wish Mozilla declared FF 56 a LTS release for those of us who value their addons more than performance benefits of Quantum. Right now I'm still using an out-of-date release that doesn't receive critical security updates, and I have to choose between either downgrading 4 releases down to F…

Which are the addons you're missing?

Do they have a GitHub site?

Re: Firefox 59 released

#86

Post by Crespyl » Tue, Mar 13, 2018, 3:24 PM UTC

proaralyst wrote: post #65

childintime wrote: post #45

Sadly no news on the Web-extensions front. Several of my extensions continue broken.

What news are you looking for? I'm fairly sure extensions targeting the older APIs will not be supported in any future release.

Old extensions won't ever really work again, but part of me is still kind of holding out hope for WebExtensions API features for things like "allow extension on 'system' pages (new tab, settings, etc)", "focus addressbar", "hide/replace address/tab bars", etc.

Some of those are coming or pretty much ready (tab hiding, addressbar focus), and others I've almost given up on, given how Mozilla seems to have changed their philosophy.

Re: Firefox 59 released

#87

Post by andrepd » Tue, Mar 13, 2018, 3:25 PM UTC

Still on 56, sadly. The addons crucial for my workflow have stopped working. Shame these concerns were not properly addressed, even after months of clamour about breaking changes like these.

Re: Firefox 59 released

#88

Post by CoffeeDregs » Tue, Mar 13, 2018, 3:26 PM UTC

jadbox wrote: post #42

CoffeeDregs wrote: post #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

Isn't limiting the ipc processes severely capping (CPU) performance?

I haven't really noticed much of a difference in performance but memory usage is much lower.

Re: Firefox 59 released

#89

Post by Silhouette » Tue, Mar 13, 2018, 3:26 PM UTC

MikkoFinell wrote: post #78

ppbutt wrote: post #64

Does this include the forced collection of the user's usage data?

Better stay away from the evil Mozilla corporation, and instead use one of those other, more privacy-aware, browsers like Google Chrome or Microsoft Edge.

That did not answer the question, and in light of discussions just a few weeks ago on this subject, the question was fair.

Re: Firefox 59 released

#90

Post by youseecomrade » Tue, Mar 13, 2018, 3:27 PM UTC

grok2 wrote: post #79

After I switched to Firefox 59 beta on Windows (7 upgraded to 10), I see the following issue all the time. When accessing finance.google.com in one tab and etrade.com (internal page) in another, if I am on finance.google.com and if it refreshes and is slow for some reason I start seeing a blank page with a spinner on that tab and while this is happening, if I switch to the etrade.com tab, I see that page is blank too…

Not sure it's related but a lot of Google's sites are terrible on Firefox and Edge. IIRC they are using polyfills for some heavy stuff (if you assume no malice, that's probably the cause of many problems).

https://www.reddit.com/r/firefox https://support.mozilla.org/

Try using safe-mode https://support.mozilla.org/en-US/kb/troubleshoot-firefox-is... or maybe creating a new profile. The beta versions, just like Chromium or Chrome, occasionally have some weird bugs. At least for me most of them are always hardware acceleration related.