Live data from Hacker News

Firefox 57.0 Released

mozilla.org

141–150 of 836 posts

Re: Firefox 57.0 Released

#141
post #60
post #51

Earlier quoted context omitted.

The WebEx Tree Style Tabs is markedly inferior to the "Legacy" version. It is simply an integral and indispensable part of my workflow, so much that I can't even fathom browsing without it. I guess I'll stay on 56 for a while.

What problems do you have with the new version?

- Open a new window: the tabs are not there by default - You need a css hack to hide the standard bar - There’s an ugly title thingy at the top of the tab pane

Re: Firefox 57.0 Released

#142

I'd feel a little better if the words "secure" or "security" appeared at least once in the marketing material: https://www.mozilla.org/en-US/firefox/57.0/whatsnew/ , https://www.mozilla.org/en-US/firefox/ .

Fixed: "various security fixes"

(which is a link to details)

Re: Firefox 57.0 Released

#143
post #128
post #98

Earlier quoted context omitted.

The right thing to do would have been to work on those extensions BEFORE breaking users' experience.

Mozilla doesn't create all those extensions. And the extensions' authors had, what, two years advance warning or so? Criticize the real culpits, not Mozilla.

If the required WebExtension APIs don't exist (per nicoburns' comment) I'm not sure what you want the extension authors to do about it.

"Complain loudly" was the strategy that got Mozilla to implement Tree Style Tabs as a WebExtension feature so that the addon could be rewritten for FF57, but there are presumably still legacy extension capabilities that haven't gotten that treatment.

Re: Firefox 57.0 Released

#144
post #128
post #98

Earlier quoted context omitted.

The right thing to do would have been to work on those extensions BEFORE breaking users' experience.

Mozilla doesn't create all those extensions. And the extensions' authors had, what, two years advance warning or so? Criticize the real culpits, not Mozilla.

If required APIs don't exist any more, how is that extension author's fault? (Tab Groups user here)

Re: Firefox 57.0 Released

#145
post #128
post #98

Earlier quoted context omitted.

The right thing to do would have been to work on those extensions BEFORE breaking users' experience.

Mozilla doesn't create all those extensions. And the extensions' authors had, what, two years advance warning or so? Criticize the real culpits, not Mozilla.

Two years without the APIs making a port possible.

Re: Firefox 57.0 Released

#146

I'd feel a little better if the words "secure" or "security" appeared at least once in the marketing material: https://www.mozilla.org/en-US/firefox/57.0/whatsnew/ , https://www.mozilla.org/en-US/firefox/ .

what concerns do you have regarding firefox’s security?

Re: Firefox 57.0 Released

#148
Congrats to the Firefox developers and team in general. I've stuck with Firefox as my primary browser since version 2 or 3, even as it became very frustratingly slow or resource inefficient compared to Chrome. Version 57 is tremendous.

Re: Firefox 57.0 Released

#149
post #39

Earlier quoted context omitted.

Tree Style Tabs was the only blocker for me, and I was amazed that it was possible to recreate under the new API. I use both Firefox and Chrome, but for very different purposes. In Chrome, I have 20-50 tabs spread across two windows. In Firefox, 400+. Tree Style Tabs is necessary for how I use Firefox. My backup plan was staying on an older version, possibly indefinitely.

400 tabs? 400 ? I'm sorry if I sound a little condescending, but have you considered using bookmarks instead? I cannot even imagine a workflow where four flippin' hundred active tabs are needed.

I just learned this recently: https://en.wikipedia.org/wiki/Divine_fallacy

Re: Firefox 57.0 Released

#150
post #71

Earlier quoted context omitted.

A developer answered in another post > The point of parallelization is to harness the full power of the CPU. If you don’t want that try reducing the content process limit near the bottom of general options. [ https://hacks.mozilla.org/2017/11/entering-the-quantum-era-h... ]

It's not murdering battery because it's "harnessing the full power of the CPU", it's chomping through almost 1% battery a minute on Mac while doing virtually nothing. Apparently "vibrance" is one of the culprits and switching to the light or dark themes can help a lot. But yes, it's destroying battery compared to Safari for me. Which is a shame, as it's already my default on Windows.

Sounds like you should definitely file a bug.
Post reply on HN