Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 84.0

mozilla.org

Post reply on HN
Print view View original

211–220 of 328 posts

Re: Firefox 84.0

#211

Post by corty »

jackewiehose wrote: post #123
CJefferson wrote: post #51

Is anyone else worried Firefox on Android is becoming increasingly unusable? How well supported is it my Mozilla I wonder. I often find pages render as blank pages until I refresh, and scrolling will often hang for multiple seconds. I was playing "Jackbox Games" (which is played via the web and PC), and I found those of us on Firefox found the text boxes were broken. Just downloading PDFs was broken for several weeks…

I'm very unhappy with the new FF mobile. The user interface is worse than before in every(!) aspect. There's not a single improvement. And everything feels slower. And there is no offline browsing. On a mobile browser! WTF?! And there is no way to save websites. On a mobile browser, which has very limited connectivity due to its nature. This is just sad. There was a time when I was happy to read about a new FF versio…

I agree. The Tab interface is unusable. new FF opens lots more new tabs than the old one. But the list is less readable, less usable, and closing tabs is a chore (!) because there is a list-slide-animation that makes you miss the next X to close and you have to wait for the f-ing animation to finish. Bookmarks are inaccessible, you only see a few on the new-tab-page or in an unordered mess as search results when typing something in the address bar. A loading indicator is missing and loading often hangs for a long time or clicks don't register. I'm seriously researching alternatives, the status quo is hell.

Re: Firefox 84.0

#212

Post by [deleted] »

bzbarsky wrote: post #176
cesarb wrote: post #105

Earlier quoted context omitted.

> Firefox won't even ask the DNS stack for the IP, assuming loopback instead. Which loopback, 127.0.0.1, ::1, or both?

Looking at the code in the DNS service in Firefox, it kinda looks like this for localhost: 1) If IPv6 disabled in prefs or caller explicitly requested IPv4 only, 127.0.0.1. 2) If localhost explicitly listed in the IPv4-only domains list in prefs, 127.0.0.1. 3) If caller explicitly requested IPv6 only, ::1. 4) Otherwise both 127.0.0.1 and ::1. See nsHostResolver::InitLoopbackRecord in https://searchfox.org/mozilla-cen…

[deleted]

Re: Firefox 84.0

#213

Post by JoshTriplett »

cortic wrote: post #179

My advice; stop reinventing the wheel, and if you must reinvent the wheel, make sure its at least as round as the last one. I've been using FF since Netscape, and it used to be a few settings and we're off. Now, you have to edit policies.json to get updates stopped, autoconfig.js and firefox.cfg to disable telemetry, legacyUserProfileCustomizations to use userChrome.css to get anything like a proper menu system. 'Loc…

> autoconfig.js and firefox.cfg to disable telemetry

You can change this in the configuration dialog, and once disabled, that setting will be preserved through Firefox upgrades. You shouldn't need to change this repeatedly.

> legacyUserProfileCustomizations to use userChrome.css to get anything like a proper menu system.

By "proper menu system", do you mean having the menu bar always visible? You can enable that with View->Toolbars->Menu Bar.

> you have to edit policies.json to get updates stopped

Doing so would result in running an outdated and potentially insecure browser.

Re: Firefox 84.0

#214

Post by dmix »

slenk wrote: post #158
blindm wrote: post #3

Earlier quoted context omitted.

And if you sorely miss Flash, you can run it with Ruffle: https://ruffle.rs/

I will have to keep that in mind. A lot of old management interfaces for rack-mount servers run flash for their web interface :S

Poor, poor `seink2`.

Re: Firefox 84.0

#215

Post by dmix »

bzb6 wrote: post #77
blindm wrote: post #3

Earlier quoted context omitted.

And if you sorely miss Flash, you can run it with Ruffle: https://ruffle.rs/

I tried it on archive.org and it’s not that good. https://archive.org/details/flash_badger On Chrome the animation starts lagging behind after a few loops so audio and video desync badly. On Firefox it’s much worse, since Firefox is naturally slower than Chrome so even the first loop is desynced already.

Didn't not experience this on Chromium/MacOS Big Sur/MBP.

In fact it ran perfectly.

Re: Firefox 84.0

#216

Post by randomsearch »

akmittal wrote: post #166
bryanlarsen wrote: post #44

Earlier quoted context omitted.

Firefox is way too valuable as a hedge against Google hegemony to let die. If they ever lose the Google search money hose and become threatened I do expect a Google competitor to realize that and step in with some funding. Microsoft basing Edge on Chromium was a really stupid move on their part for this reason, and I suspect they are starting to realize it. That being said, I only expect it to be maintained at a hedg…

>Microsoft basing Edge on Chromium was a really stupid move on their part for this reason, It is not true at all. After a long time Microsoft's browser share in increasing. They probably are quite happy about it,.

You’re both right I think: short term needed users so adopt chrome... long term Firefox essential so MS would step in as a supporter (and potentially adopt it too should google become a problem).

Re: Firefox 84.0

#217

Post by cortic »

JoshTriplett wrote: post #213
cortic wrote: post #179

My advice; stop reinventing the wheel, and if you must reinvent the wheel, make sure its at least as round as the last one. I've been using FF since Netscape, and it used to be a few settings and we're off. Now, you have to edit policies.json to get updates stopped, autoconfig.js and firefox.cfg to disable telemetry, legacyUserProfileCustomizations to use userChrome.css to get anything like a proper menu system. 'Loc…

> autoconfig.js and firefox.cfg to disable telemetry You can change this in the configuration dialog, and once disabled, that setting will be preserved through Firefox upgrades. You shouldn't need to change this repeatedly. > legacyUserProfileCustomizations to use userChrome.css to get anything like a proper menu system. By "proper menu system", do you mean having the menu bar always visible? You can enable that with…

> can change this in the configuration dialog,

The options in config were greyed out in 83.

> "proper menu system", do you mean..

The ability to make multi tier menu with icons or text instead of both

>Doing so would result in running an outdated

Doing so would result in a stable system that wouldn't just randomly disable all addons from working, security related addons at that.

Re: Firefox 84.0

#218

Post by jakub_g »

chinhodado wrote: post #11

I love Firefox, I use it everyday, I can't imagine using a browser without Tree Style Tab, or all the things that I can do in about:config. At the same time, I can't shake off the dreadful feeling that it will eventually die one day. The market share keeps falling year by year. What is the most realistic future for Firefox?

I don't have the numbers, but I've read somewhere recently that while market share in % drops each year, the overall absolute numbers (millions of users) are somehow stable.

It's the pie that is expanding (especially on mobile, where Firefox has hard time competing).

Re: Firefox 84.0

#219

Post by bigbubba »

macspoofing wrote: post #37
jefftk wrote: post #9

And for developers: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel... The biggest change from my perspective is "Firefox now ensures that localhost URLs — such as http://localhost/ and http://dev.localhost/ — refer to the local host's loopback interface (e.g. http://127.0.0.1 ). As a result, resources loaded from localhost are now assumed to have been delivered securely (see Secure contexts), and also w…

>This is great for local development. Not just. There is a niche for mixed web/native apps whereby the page is loaded from the web, but interacts (at least in part) with a locally hosted web-server.

I hate this shit, I've only seen the sketchiest sort of spyware, like discord, do it. Browsers should forbid it, since it's a blatant end-run around the limitations a 'web app' would normally have.

Furthermore, browsers even having this ability facilitates inter-protocol exploitation. It's not only local webservers that are put at risk by this, other sorts of local servers can be attacked as well. See CVE-2016-8606 for an example of a browser being used to attack a guile repl.

Post reply on HN