Live data from Hacker News

Firefox Quantum

daniel.haxx.se

191–200 of 206 posts

Re: Firefox Quantum

#191

Earlier quoted context omitted.

I use ctrl+tab and ctrl+shift+tab to cycle tabs. Good to know that there are other options. I also don't see how people have the RAM to have 50 tabs open. If I can't read part of the title of my tab, it's being moved to a new window or closed.

Actually having 50 tabs should not be an issue RAM-wise. The problem is that chrome (and firefox quantum) open many many processes and therefore consume a lot of ram. Quantum is expected to be much better than current Chrome in Ram consumption. Because chromium allegedly opens seperate processes for each tab(?), quantum uses the same process for a couple of tabs and thus allows resource sharing. In a single processed…

With light pages + efficient ad blocking, 50 tabs seem actually light on memory. This may be less true with video pages or many heavy online newspaper websites.

Since I got a 32 GiB RAM computer, I don't know what is the memory usage of Firefox anymore.

Re: Firefox Quantum

#192

Earlier quoted context omitted.

I have always just used ctrl + pgup/pgdown in Chromium for tab switching (same in Sublime). I am guessing OP is referencing the fixed min-width of the tabs though? I know it is completely insane, but I have a strong compulsion to keep my tab count low. Once it starts approaching 7 or so, it is time to evaluated which 3 or 4 have to go. Meanwhile I go look at someone else's monitor and they have 25 open all the time,…

tab groups! that is the way to live. Grouping tabs based on theme keeps the bar clean and makes it easy for theme based workflow

I love them at times. Do you know if a Firefox 57+ compatible extension exists for that?

Re: Firefox Quantum

#193

Earlier quoted context omitted.

I'd be happy, but beside a context and a list of tabs I have no precise info to give. Would it still be useful ?

Possibly, yes. Even just some idea of which urls are involved and of which operations are being slow would be useful.

Okay, then. Could you give me a few pointers on how to submit (a bugzilla ticket I suppose) ?

Found out the troubleshooting and health report menus in the mean time.

Re: Firefox Quantum

#194

I still use the Firefox ESR for the dev tools, the new dev tools are missing things like the network response preview, the debugger is not working right for me, and the Chrome look does not appeal to me, I prefer the old dev tools. Other then this as a user I like the fact the Firefox is moving again and in a right direction most of the time. I hope they respect the user privacy more and the new privacy invading feat…

> the new dev tools are missing things like the network response preview Do you mean the content of the response or something else? Because I'm on FDE and they're definitely there ("Response" tab when selecting a network entry)

I can see the response as plain text but before there was a PReview tab too that showed the response as rendered html, there is a ticket opened for this issue https://bugzilla.mozilla.org/show_bug.cgi?id=1353319

Re: Firefox Quantum

#195
post #33

I still use the Firefox ESR for the dev tools, the new dev tools are missing things like the network response preview, the debugger is not working right for me, and the Chrome look does not appeal to me, I prefer the old dev tools. Other then this as a user I like the fact the Firefox is moving again and in a right direction most of the time. I hope they respect the user privacy more and the new privacy invading feat…

The old devtools were amazingly slow and heavy. The new ones are much much better. Almost as fast as Chrome's.

For me the tools worked fine, I prefer the Firefox ESR layout, I prefer FF ESR Network tab, Chrome network tab is too much for my usual tasks, 99% of the time I want to see the response code and the exact response and I do not care about profiling, so Ff way worked fine for me. The JS debugger layout makes more sense for me how it was in Ff, call stack on left side, variables on right side, Chrome call stack view is weird. So I use ESR for dev, hopefully the bugs that affect me will be fixed and the UI changes I could get used to. https://bugzilla.mozilla.org/show_bug.cgi?id=1353319

Re: Firefox Quantum

#196
post #166

I still use the Firefox ESR for the dev tools, the new dev tools are missing things like the network response preview, the debugger is not working right for me, and the Chrome look does not appeal to me, I prefer the old dev tools. Other then this as a user I like the fact the Firefox is moving again and in a right direction most of the time. I hope they respect the user privacy more and the new privacy invading feat…

> the new privacy invading feature should be opt in. I agree. The new features, however, are not. They even ("temporarily") collect IP addresses by default when FF calls home.( https://www.mozilla.org/en-US/privacy/firefox/ ) And, naturally, they also intend comply with the law. In other words, they hand over data to governments. ( https://www.mozilla.org/en-US/privacy/ ) What Mozilla are doing here is despicable.

The users that used Firefox despite the lower performance had good reaspons to use Ff like privacy and the extensions, now this new performance updates are cool but the updates that affect privacy and extensions hit the loyal users, I think this is a huge, mistake and I understand that extensions need to be updated but privacy should be the first reason someone would use Ff over chrome, if Mozilla needs statistics then they can prompt the user and ask permissions.

Re: Firefox Quantum

#197
post #105

Earlier quoted context omitted.

> I'm surprised more tech people don't use it, considering the tech communities love for power and the ability to customise things. I used to be pretty fanatical about Firefox. But when it got so slow that simple scrolling started dropping frames, I had to switch.

That is because of smooth scrolling. I had to reduce the time for smooth scrolling to complete. I forget the key I modified in about:config.

Some people do perceive smooth scrolling as annoying, but for the most part what he's referring to was because of JavaScript ScrollEventHandlers being run in between the user moving their mouse wheel and the page actually scrolling.

This was fixed with Asynchronous Panning and Zooming (APZ) which moves the webpage and runs the ScrollEvents in parallel on different processes.

Re: Firefox Quantum

#198
post #48

Earlier quoted context omitted.

I wondered the same thing a while ago and I would think this is to ease dragging the window with the mouse, which you may want to do easily when the window is not maximized. I'd really like Firefox on Linux to hide the window title bar (at least when maximized) and put the close / maximize / reduce buttons in the tab bar (or make it an option). The tab bar does already allow one to move the window, at least on KDE. T…

Last mont Fedora had a release in which you could use CSD to merge the title and the tab bars. You only had to set a variable(maybe widget.allow-client-side-decoration?) in about:config to true. They took that option away because some bugs but it may arrive for the next firefox release. Here is how it looks like https://twitter.com/Sesivany/status/908628645299748865

This is great. I didn't expect this to happen so soon.

When we will have this and pixel-perfect scrolling enabled by default, the Firefox UI will be close to ideal for me.

To get pixel scrolling now, the solution is easy:

  #!/usr/bin/env sh
  MOZ_USE_XINPUT2=1 exec /usr/bin/firefox "$@"

Re: Firefox Quantum

#199

Earlier quoted context omitted.

Possibly, yes. Even just some idea of which urls are involved and of which operations are being slow would be useful.

Okay, then. Could you give me a few pointers on how to submit (a bugzilla ticket I suppose) ? Found out the troubleshooting and health report menus in the mean time.

https://bugzilla.mozilla.org/enter_bug.cgi if you're willing to create a bugzilla account. Though I guess we also have sign-in with a github account now...

Re: Firefox Quantum

#200
post #185

Earlier quoted context omitted.

> I've never understood why the feature hasn't been added, it seems pretty minor. I don't want it. I don't like Firefox's approach, I much prefer the shrinking tabs paradigm.

Firefox tabs do shrink. Then, once they get to a width where shrinking any more would start negatively impacting the ability to use the UI, they start to scroll. Until you reach this point, the tab scrolling UI is hidden, so there's no concern for anyone who doesn't use tabs heavily.

> Until you reach this point, the tab scrolling UI is hidden, so there's no concern for anyone who doesn't use tabs heavily.

Which is me. :-)

Post reply on HN