Live data from Hacker News

Firefox 57.0 Released

mozilla.org

271–280 of 836 posts

Re: Firefox 57.0 Released

#271
post #226

Earlier quoted context omitted.

It needs an entry for RamBack[0]. Before installing RamBack, FF was very frustrating and I was seriously considering chrome [0] https://addons.mozilla.org/en-US/firefox/addon/ramback/?src=...

Given the performance and memory usage improvements in FF57, it might not be necessary any more (I note that extension was last updated in 2007)

Hopefully it won't be necessary in FF57. Though I can attest that it is necessary in FF 54 and FF55

Re: Firefox 57.0 Released

#272
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…

You don't need a plugin to get the menu bar back, you can just do (tap alt) View->Toolbars->Menu Bar, at least in FF56. I don't know for certain if that option still exists in FF57, but I hope it does.

I've been turning the menubar back on in Firefox for ages now. It's really dumb to hide it IMHO because they never used that space for anything else. It was just useless blank space.

Re: Firefox 57.0 Released

#273
To chime in with some of the others, I decided to try out Firefox again [0] when the FF57 beta/nightly/whatever was first released and am very happy that I did!

Looks like that was ~48 days ago and I think I've opened up Chromium maybe two or three times since then.

(WRT extensions, LastPass was the only thing I "missed" (we have Enterprise for $work) although I normally use the CLI utility instead anyways. They came out with a beta a few weeks ago and it was actually working great until about two days ago when it suddenly broke for me. The other extensions I use -- uBlock Origin, Vimium -- have been working just fine.)

[0]: https://news.ycombinator.com/item?id=15344018

Re: Firefox 57.0 Released

#275
post #260

Feels GREAT! Happy to be using this in addition to Safari. I also added uBlock Origin as an adblocker but would still love if FF eventually included native, declarative content blocking like Safari (probably less likely given how much money they get from Google).

I don’t want necessarily want an adblocker built into my web browser. It creates too much centralized risk and power for the kinds of shenanigans pulled by ABP or ghostery, and it would hurt adoption of good add-ons like ublock.

What I DO want to see is something like ublock matrix become a standard feature. Matrix is an incredible add-on that has made the web more useable and more debuggable for me. If it was built-in, the defaults would have to be toned-down or turned off, because it breaks too much of the web, but a simple “privacy mode” toggle to step up restrictions would be welcome in a private browsing window.

Call it “War Mode” or “Paranoid Window” when using a private window with maxed out Matrix.

Re: Firefox 57.0 Released

#277

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…

Interesting. I'm on mac, and I'd say I'm usually pretty sensitive to native widgets, but for whatever reason the toolbar and the menus don't bother me at all. Overall it has a very clean feeling to me. Maybe just because I've gotten so used to browsers being their own little world.

What does drive me crazy is

1. not having bounce scrolling

2. not live-panning the page when using a swipe gesture to go back

Bounce scrolling, especially, I think is table stakes if you want to take the Mac seriously.

Re: Firefox 57.0 Released

#278
post #73

Earlier quoted context omitted.

It's a very nice feature. But note that a consequence of this is that you'll loose data if you desync all devices. The private key is only transferred from device to device, without being stored in any server.

We actually fixed that failure mode three years ago with the release of Firefox Sync 1.5. The encryption key can now be re-derived from your password, so you can always recover your data as long as you remember your password. Even if you lose all of your devices.

Ah, good to know. Ideally it should also derive another key when logging into Sync, so it's never sent verbatim even through a secure channel.

Re: Firefox 57.0 Released

#279

Earlier quoted context omitted.

Tried this. It was too complicated and slow enabling every subdomain by hand.

It is a little fiddly to set up at first, certainly. There are a few tools to make it easier though: if you're dealing with a site that uses a lot of semi-random subdomains (like googlevideo or cloudflare), it's possible to just whitelist the whole domain and get all the subdomains automatically (and then block individual subdomains if you want). It might be defeating the purpose, but you can also change the "scope"…

> sync my black/whitelists through Firefox Sync

It's technically possible, although UX is terrible. Go to uMatrix settings, make sure to "enable cloud storage" option is set in the "settings" tab, then manually upload and download rules in the "my rules" tab.

No automatic sync (won't be implemented[1]) and, no merges at the moment (button's broken[2]).

[1] https://github.com/gorhill/uMatrix/issues/467

[2] https://github.com/gorhill/uMatrix/issues/807

Re: Firefox 57.0 Released

#280
post #238

Earlier quoted context omitted.

Unfortunately, this would have meant no Firefox Quantum. As a Firefox dev (I'm still working at Mozilla, although not much on Firefox atm), I have seen many, many occurrences in which I couldn't optimize codepaths, or even in some case fix bugs, because the old extension mechanism made it impossible. Consider the necessary steps: 1. realize that an internal API is broken; 2. come up with a new non-broken API; 3. port…

I'm sure you'll hear a zillion complaints, but I really appreciate you folks doing this. I've been using a beta version for the last few months on one of my computers and it's so very much better. I can't wait to have it everywhere. As long as you're here: I was told that the old extension API was way too broad, locking in a lot of design choices that were not really considered from the "do we want to maintain this f…

Oh yes! It very much is :)
Post reply on HN