Dear Firefox developers, please fix vsync one day.
Downvotes? Ok, here's another one.. dear Firefox developers, in Google Meet captioning does not display, but does in other browsers.
Firefox 84.0
171–180 of 328 posts
Re: Firefox 84.0
#172Is 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've had issues with blank pages and scroll hanging occasionally in the years I've used Firefox on Android, but it seems like those issues have become less common for me lately with the last couple updates. Though I also did a big purge of my tabs lately (getting down to 10 from over 200) and I wonder if that decreased the amount of issues.
Re: Firefox 84.0
#173Does anyone know what increasing compatibility with docker means? Is this for headlessly running firefox for testing?
Re: Firefox 84.0
#174What's the best way to support the browser directly with money? Pay for the VPN?
Donations will increase Mitchell Baker compensation even further, and won't help the browser. I think at this moment donation will corrupt Mozilla even further. Better keep money until they fix the management.
Re: Firefox 84.0
#175Earlier quoted context omitted.
It would be complicated due to Mozilla's structure. Mozilla Foundation is a non-profit that owns the for-profit Mozilla Corporation. You can donate to the foundation but they can't use the money for Firefox. But the fundamental reason is that donations are only ever going to be a drop in the ocean. Google gives them $400m/year. Mozilla Foundation donations are like $3m/year. Even Wikipedia donations are only about $1…
What's preventing the Mozilla Corporation from selling "e-merchandise", like a sequence of themes for $1, $5, $10, $100, etc, to raise money?
Probably nothing, but again I suspect they don't bother because it would be a drop in the ocean and certainly not worth the "Mozilla is selling out!" backlash you'd get from the sort of people that use Firefox.
Re: Firefox 84.0
#176Earlier quoted context omitted.
The latter. You can always set your /etc/hosts or equivalent to map "localhost" to some random IP that is not loopback. Or a proxy could proxy that hostname, etc. In the new setup proxies can't proxy localhost unless you set a pref to explicitly let them do that, and for "localhost" and hostnames ending in ".localhost" Firefox won't even ask the DNS stack for the IP, assuming loopback instead.
> 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-central/source/netwerk/dns/nsH... and nsDNSService::GetAFForLookup in https://searchfox.org/mozilla-central/source/netwerk/dns/nsD... for the key.af calculation that goes into that, as far as I can tell.
Re: Firefox 84.0
#177And 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…
Am I incompetent if I thought all browsers all did this already by default? Or was this typically enforced at the OS/networking-stack level, and now Firefox is adding an additional guarantee that it will happen directly in the browser, even if the networking stack would say otherwise?
It's just /etc/hosts, "localhost" is a hostname like any other. It can be changed to whatever IP address you want.
Re: Firefox 84.0
#178Earlier 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?
You have all of 127.0.0.0/8 as a loopback; I hope it doesn't hard-code 127.0.0.1 as I use some other addresses as well.
"localhost" is hardcoded to resolve to "127.0.0.1" (ignoring IPv6 for now).
The "is secure context" state applies to 127.0.0.0/8 (again ignoring IPv6). See NetAddr::IsLoopBackAddressWithoutIPv6Mapping in https://searchfox.org/mozilla-central/source/netwerk/dns/DNS...
I'm pretty sure all of this is clearly specified at this point, so browsers should end up all aligning on a common behavior here at some point, if they haven't yet.
Re: Firefox 84.0
#179My 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.
'Lockwise' has dumbed down the login system so much you can't even change field names, making many sites incompatible. Nor can you import logins from file or even point to installations to import. The add-ons system is like traveling back in time ten years, bugs and fewer alternatives than ever, still can't figure out how to stop Tree Style Tabs from stealing mouse focus from the page onmouseover like a widget. -And these are problems that were fixed before they were reinvented.
For the first time in 16 years I'm seriously trying alternatives.
-these were my views on 83, i hope to hell 84 fixes some of them.
Re: Firefox 84.0
#180And 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…
Does this mean Firefox will ignore my hosts file entry? 127.0.1.12 dev.localhost
Based on code inspection, I believe so, yes. It will map "dev.localhost" to 127.0.0.1.