Live data from Hacker News

Firefox 57.0 Released

mozilla.org

151–160 of 836 posts

Re: Firefox 57.0 Released

#151
post #123

Earlier quoted context omitted.

You can change the theme to "light" in preferences. If should get rid of the black bar. This has been a common complaint from osx users.

Can't seem to find where it is in firefox preferences. Could you please extend your solution?

This got me too. It's not in preferences, you have to use the hamburger menu thingy. Then, it's shoved randomly at the bottom.

The overall design is really a mess in 57, although browsing does seem faster.

Re: Firefox 57.0 Released

#152
post #106

Anyone know how the new FireFox compares on battery-life? Safari crushes Chrome on this front currently, but I'm curious how FireFox compares now.

None of the Firefox Quantum work has looked at power usage, so don't expect any changes on that front.

Well... new renderer and JS engine are faster and use less memory, which means less CPU cycles are used for the same thing and less information is stored in RAM, there are improvements for Windows and Linux hardware acceleration. This all summed-up means reduction of power consumption.

Re: Firefox 57.0 Released

#153
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.

There's only so much an extension author can do if WebExtensions doesn't expose an API corresponding to one which was critical in the XUL extension.

I'm in that position myself right now, having volunteered to take over Firemacs development before I found that there is no way to listen for keypress events in browser chrome. You can only do that in injected content scripts, which don't work except in web content and are also affected by CSP. Until that changes, there's nothing that I, or the Vimperator developers for example, can do to provide an acceptable user experience.

It's super frustrating, and I don't blame users of such extensions for being angry about the indefinite lack of a future for them. But I also don't really blame Mozilla for prioritizing the implementation of the necessary APIs below other tasks which are important to a larger fraction of the Firefox user base.

Re: Firefox 57.0 Released

#154

This is so close to great but can a mac snob ask how to get a more consistent UI experience out of firefox? I'm totally happy with how everything behaves inside the web panel but: 1. At a minimum I'd be happy with a toolbar icon set that was a little more in step with OS X design (but willing to hear if I just have misunderstanding of design :D) 2. As a reach, os-native menus or at least more native-style menus for t…

If only they'd put all the effort spent into trying to imitate macOS into actually building an AppKit version... I guess that's never going to happen due to the cross platform nature of Firefox, but it also means (among other reasons) I'll never use it as my primary browser.

Re: Firefox 57.0 Released

#155
post #51
post #7

Hopefully most of the missing extensions will be developed sooner rather than later. I have 15 extensions installed, 14 of which are "Legacy". The most critical one, Tree Style Tabs, has been converted. That was the key blocker that prevented me from seriously using Chrome. But many more remain; Cookie Controller, RefControl, some kind of Classic Theme Restorer equivalent (to get a menu bar back for Bookmarks, at a m…

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.

Same for me, there’s no VimFX or Keysnail equivalent. I’ll just stay on firefox 57-0a1 (that’s an old alpha release, where (strangely) VimFX and the good old Tree Style Tab still work) for a long time.

Re: Firefox 57.0 Released

#156

At last LastPass has released a new version! (FF Developer Edition has passed beyond the grace period so only allows modern extensions. I've been using Chrome just for lastpass for months!)

This is what's holding me back from changing mostly. Honestly, lastpass is great for me but I almost wish built in browser password managers were better. I used to use Google Chrome's password manager but one time I synced with another computer or phone and everything got erased and there was no undoing it. I lost everything. Maybe syncing is better now but after that sync that thought "hey let's make sure everything…

High time that passwords management was integrated into the OS, where it belongs. These days its not just sites, but hundreds of apps too that want your passwords, and browser based extensions can't interface with other apps. On the other hand a standalone password manager has at best a flaky interaction with web pages inside a browser window, and often has to be supported by an in-broswer extension, adding to complexity of code and interaction.

We need the OS to store credentials and expose a well-defined, OS independent API for apps/sites to identify themselves securely and request for the user's authentication. This will go a long way towards mitigating exploits like cross-site scripting attacks, phishing, software keyloggers, clipboard sniffers and so on.

I really find it amazing that this is something none of the major OS creators have tackled in a standarised manner.

Re: Firefox 57.0 Released

#157
post #128

Earlier quoted context omitted.

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)

If they don't exist, sure, but most of the bickering is "I want XUL and nothing else".

And how many of those lamenting the absence of some API have actually told Mozilla what they need?

By all accounts Mozilla has been very responsive and helpful. Not everything was possible, but the problem lies mostly not on their side.

Re: Firefox 57.0 Released

#158
post #38

Earlier quoted context omitted.

Android will get Quantum with 58, in approximately 6 weeks time. https://www.ghacks.net/2017/10/31/firefox-58-for-android-ena... But even without Quantum Firefox on Android is way faster than Chrome because it supports ad blocking plugins.

Yeah, I can't wait for FF58 on Android. TBH FF on Android has felt a little choppy, even with ublock origin enabled. The Chromium-based Firefox Focus feels faster, but too bad it doesn't support extensions. Hopefully FF58 will be the best of both worlds on Android soon.

I am curios. Are you using FF Beta on Android or regular FF?

Re: Firefox 57.0 Released

#159
since 56.0 google maps went black on me and nothing seems to matter. really confused how something so simple just breaks; I am on OS X fwiw.

I end up swapping to safari for some functions and then using firefox for others. throw in 57 changes the look for no reason. I don't need dark tabs as default, updates should not change the user experience without permission

Re: Firefox 57.0 Released

#160
post #141
post #60

Earlier quoted context omitted.

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

> Open a new window: the tabs are not there by default

It's not ideal but not a showstopper for me. I mostly use one window, where the toolbar is restored by default, and when I open a new window I got used to clicking the toolbar button (which I moved to the left) or pressing F1.

> You need a css hack to hide the standard bar

> There’s an ugly title thingy at the top of the tab pane

I just copied the "css hack" once and forgot. The last item is solved the same way. For those who don't know:

Inside the profile folder (with a name like "xxxxxxxx.default"), create a folder called "chrome", and a file inside called "userChrome.css" with the following content:

    #TabsToolbar, #sidebar-header {visibility: collapse !important;}
    #TabsToolbar {margin-bottom: -21px !important;}
IMHO It's quick enough to do and I believe this won't be needed in a few months.
Post reply on HN