Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 58

mozilla.org

Post reply on HN
Print view View original

181–190 of 197 posts

Re: Firefox 58

#181

Post by Yizahi »

51Cards wrote: post #55
eropple wrote: post #24

Earlier quoted context omitted.

Yeah, it positively was , and it would lock the browser up with misbehaving tabs. I managed to use Fx50 (or so, I forget the exact release) for about a day before going "nope, back to Chrome, it might chew batteries like crazy but at least it's fast." Firefox has significantly improved and deserves praise for it. Rewriting history to always be at war with Eastchromea is unnecessary.

I have had the opposite experience. While individual page loads were a bit quicker in Chrome after a number of tabs were open it bogged down so badly (coupled with the lack of customization) I ran back to Firefox every time. A few months later I would try again with similar results. I agree that when a tab would crash FF would die in spectacular ways but this was perhaps a once a month experience? Tab restore brought…

This. I tried Chrome two or three times for several months a few years ago. Yes, it was fast but had issues with loading pages I usually used, e.g. I click on a link and shows me white page for some time, long enough to be annoying. On the other hand FF since pre 1.x versions is always about the same. I don't see big improvements in speed and I don't see big degradation too. The only problem I had is with Atlassian web pages that tend to memory leak when left open for days. At home where I never open them FF is very stable.

Re: Firefox 58

#182

Post by DiThi »

kovrik wrote: post #27
tdumitrescu wrote: post #22

Earlier quoted context omitted.

Yeah, the browser has gotten snappier. But then I pop open the dev tools and they're unbearably slow - like I simply can't do real dev work in FF anymore, have to use Chrome. It may be that I tend to do a lot of development with Web Components, which FF still doesn't have natively (though Custom Elements are live in 59/nightly, right?!), but either way it seems like a failing of the tooling that it beachballs for 5-1…

This! If I have at least one tab with Dev Tools open, then FF becomes unbearably slow. Will check if it is fixed in FF58 though.

When FF 57 came out I was surprised at the new debugger, much better than the old one. But turns out it's still useless. I can't put a breakpoint in the middle of a WebGL game and expect it to work like in Chrome.

The last dev version is even more useless, the "break on exception" button is missing.

Re: Firefox 58

#183

Post by DiThi »

samirm wrote: post #121
tdumitrescu wrote: post #22

Earlier quoted context omitted.

Yeah, the browser has gotten snappier. But then I pop open the dev tools and they're unbearably slow - like I simply can't do real dev work in FF anymore, have to use Chrome. It may be that I tend to do a lot of development with Web Components, which FF still doesn't have natively (though Custom Elements are live in 59/nightly, right?!), but either way it seems like a failing of the tooling that it beachballs for 5-1…

Have you tried the developer edition? https://www.mozilla.org/en-US/firefox/developer/

The "break on exception" button is missing in that one.

Re: Firefox 58

#184

Post by lucb1e »

callahad wrote: post #158
lucb1e wrote: post #155

Earlier quoted context omitted.

I was happy to find it, only to notice the top tab bar would always still be there. And I've seen with classmates (who saw my tab list and wanted to try it) that it sometimes bugs as well. No such issues with the good ol' Tab Center. (Good ol', yeah, the thing is what, less than two years old now?)

We're actively working on APIs to hide individual tabs, and the entire tab bar, which will bring that functionality back to Firefox. Individual tab hiding is already implemented in Firefox 59 (Beta / Developer Edition), but currently behind the "extensions.webextensions.tabhide.enabled" pref as we iron out final UX / security / privacy concerns. Still, tangible progress is happening.

> tangible progress is happening.

It's just too bad that it's afterwards. I don't see why it was necessary to toss an old system before the new one is finished. It's not as if they can't coexist.

Sorry if this is a little harsh. The hard work is appreciated and as a developer myself, I know about technical debt and stuff. This is a huge project with loads of people to please. I just hope in the future we can build the new house before tearing down the old.

Re: Firefox 58

#185

Post by phaylon »

andrepd wrote: post #13

Still on Firefox 56. My crucial addons still don't work. Still wishing Mozilla made FF56 into an ESR.

At this point, I have basically given up on the extensions I care about working correctly in the future.

These addons (tree style tabs, tab open/close control) already have webextension versions, but are extremely buggy for me, and I believe that is unfixable because the asynchronous nature of webextensions is fundamentally incompatible with changing browser behavior on that level.

It's now up to a point where I dread opening a new page, and it takes a couple of tries before a tab is in the right position in the tree, if it works at all. Sometimes they just land wherever, not even forming a correct tree anymore, old tabs reappear, and on an extension restart the whole tree is jumbled up.

So, to me, the whole Quantum era has been kind of a big disappointment.

Re: Firefox 58

#186

Post by hidden_sheepman »

The dev tools are still way to slow. Especially when debugging javascript. Sometimes there is a 40+ second wait when your trying to go from an error in the console to the line of js in debugger.

Re: Firefox 58

#187

Post by ronjouch »

Someone1234 wrote: post #56

I've been happily using Firefox since 57 shipped. Loving the overall experience. I feel a bit petty for bringing this up, but what is up with Firefox's spellchecker? I came from Chrome so the spellcheck had a web-service which kept the word list current (slang and technical terms), but even ignoring that the Firefox spellcheck doesn't do a good job with the "basics." For example "That" misspelt as "Taht" (a & h trans…

Also, hoping works someday happens on a Multiple language friendly spellchecker [1]. That design -which is the one used in Chrome- is much more pleasant to use when frequently switching between languages (at the occasional cost of a bit of leniency, but to m(an)y eyes it's a very desirable tradeoff).

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=69687

Re: Firefox 58

#188

Post by rs999gti »

adpirz wrote: post #52

FF 57 was much snappier on my Mac than on Chrome, but it occasionally turned into a CPU hog and got the fans spinning full blast. Did anyone else experience that?

I was looking for this part of the thread. I'm on Windows 10 on an i7-6600U laptop with 16GB RAM and a SSD.

FF57 spiked my cpu to 100% most of the time and Netflix was really laggy. I went back to Chrome because it only uses 10-20% CPU with regular usage.

In FF57, I was using default performance and browser settings.

Re: Firefox 58

#190

Post by godelski »

callahad wrote: post #106
godelski wrote: post #45

Earlier quoted context omitted.

Does anyone else get videos that show as like a pink or green screen and can still hear audio? I've experienced this on multiple machines with both Linux and Windows. Edit: Experienced this under FF57, unknown under 58 because I just updated it. This also usually happens with things like Facebook videos, but would less often happen with Youtube.

We've seen this on select AMD ( https://bugzil.la/1417442 ) and Nvidia ( https://bugzil.la/1422850 ) video cards. What GPU and driver version are you running?

Too late to make an edit, but I am still experiencing the issue on the Windows version and FF58

https://screenshots.firefox.com/5GyCe8xjvqM7XVYj/www.faceboo...

Post reply on HN