Live data from Hacker News

Firefox 57.0 Released

mozilla.org

331–340 of 836 posts

Re: Firefox 57.0 Released

#331

If you'd like to disable pocket, here are instructions: https://help.getpocket.com/article/1025-disabling-pocket-in-...

Unfortunately that doesn't disable the "Recommended by Pocket" crap on the New Tab Window. I have Firefox installed on 8 different machines and the option to remove "Recommended by Pocket" in the New Tab Preferences only appears in half of them.

If you're missing the option then you can open about:config and set "browser.newtabpage.activity-stream.feeds.section.topstories" to false to get rid of it. I also blew away the "browser.newtabpage.activity-stream.feeds.section.topstories.options" key that contains all of the configuration crap for pocket.

Unfortunately non of this is or the op's settings are synced in your Profile so you have to change it on all of your machines. :(

Re: Firefox 57.0 Released

#332

Just updated it on Android... and I wish I hadn't. The very first thing I was greeted with on the "top sites" page was a bunch of "Recommended by Pocket" links, and no way to disable that. I can't find anything in about:config to disable this either. How about NO, goddammit? Shame on you, Mozilla.

Those can be disabled from the new tab page itself.

Re: Firefox 57.0 Released

#333
post #93

I trashtalked Firefox being slow forever, I just tried it out and I must say it's definitely very fast. Great work to the Firefox team.

It's been fast, faster than Chrome in my experience, for at least a year. Now it's extremely fast.

Re: Firefox 57.0 Released

#334
post #325

Earlier quoted context omitted.

I'd say that the most sensible choice in the absence of any payment, considering FF sensibility and message, (i.e. according to me) DDG would be the most sensible default. (edit : clarify)

When has any proof ever been given that they’re any more privacy conscious than any other search engine?

Their privacy statement is pretty clear. That's a legally binding document and lying in that will get you pretty high fines even in the US.

Re: Firefox 57.0 Released

#337
post #242
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.

As a Mozilla dev, I fully support the move to WebExtensions, but I also disagree with you. Porting an add-on to a whole new architecture is lots of work. People who do this on their spare time, or small companies, or companies relying on contractors, may not have the time/resources/will to do it, even within two years. Also, in some case, the APIs are simply not available. As for why I believe that the move to WebExt…

Sure, but what I'm arguing against here in this thread is the pervasive "Mozilla is evil, they only killed XUL extensions for fun". Just read this thread.

When actually millions of users get a vastly superior Firefox. Many, many extensions have been updated. And some extensions – mostly niche ones haven't. I love that trade-off.

Re: Firefox 57.0 Released

#338
post #204
post #65

I just upgraded. It completely changes the chrome of the browser on OSX and it is _absolutely hideous_. There are a lots of unnecessary animations that I find very jarring. I don't know if there's a way to change it back yet. UPDATE: There is a "Customize Firefox" button which allows modifying the theme, which fixes the colors, but not the shape of the tabs or the animations. UPDATE: In about:config, you can disable…

I think it looks and feels much better than before.

I think the new design is absolutely horrible.

Re: Firefox 57.0 Released

#339
post #132

Is there some super-compelling reason why FF doesn't let you inspect websocket frames? I was taking FF for a drive yesterday, based on the earlier thread, and it was nice until I started debugging my web app. I'm not interested in trusting a third party extension with all my network data either, so the plug-in to do this isn't an option. It's weird, but this really is a blocker for me for general use.

Sorry about that inconvenience. The current plan is to revisit WebSocket debugging in Q1 next year, per https://bugzilla.mozilla.org/show_bug.cgi?id=885508 . Part of the delay is the complete rewrite that most of the DevTools are undergoing. As we move from legacy, in-house solutions (XUL) to standard web technology (HTML/JS, React/Redux, etc.) as part of the "devtools.html" project: https://github.com/devtools-html/

I see the tracking issue has been in bugzilla for years. I get that it is a tricky map from the raw packets to these frames, but relying on a 3rd party extension to the point of deprioritizing work on this is a pretty iffy call - I wasn't excited about trusting an extension at all; that the extension seems to have been broken in 57 entirely (foreseeably too) just feels meh.

I guess I'm part of a minority of people who does a lot of websockets work? Well, that's guaranteed to be true - a random feature deep inside the devtools is probably a deal-breaker for like four people.

Re: Firefox 57.0 Released

#340

Earlier quoted context omitted.

You can change it to "light" in the prefs :)

Yeah I just tried that and it changes the private window to light as well. I guess it doesn't matter much cause i don't use private much, but it's weird they have removed that distinction now.

In Firefox private mode you will always see a purple icon with a white face mask in the top right corner
Post reply on HN