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

101–110 of 328 posts

Re: Firefox 84.0

#101

Post by danielEM »

ducktective wrote: post #15
jansan wrote: post #13

Earlier quoted context omitted.

GPU acceleration is not a magic bullet it seems. In our case drawing large SVGs suddenly becomes really slow when GPU rasterization is enabled. Chrome has the same problem. I really hope we will see more polishing in this area and maybe a cooperation between Chrome and Firefox developers?

Thing is, when I play the same video with VLC which uses HW decoding, it doesn't even break a sweat. So I think there might be something wrong on the browser part...

There could be something related to FAN thresholds that resides in BIOS directly thus starting using GPU just slightly over some minimal limit might raise FAN speeds significantly and not be related to temperature raise as there is some inertia between temperature readings and real temperature inside GPU core.

I'm also experiencing FAN noise raise on my Ryzen APU based laptop.

Re: Firefox 84.0

#102

Post by coldpie »

mormegil wrote: post #90
coldpie wrote: post #21

Earlier quoted context omitted.

I'm in the same boat and have the same worries. I give them a monthly donation to support the company, in hopes of showing that there are paying customers they may be able to fall back on in the future. I can't think of anything else I can do to turn back the tide of the advertiser-developed browser. (Yes, I already know the money doesn't go directly to Firefox development today, thanks.)

Thank you for this inspiration, I've created my monthly payment now. I cannot imagine being forced to use anything else than Firefox... (Even though the Android version is barely usable after the rework...)

It is working well for me, although I'm not a heavy user and the week or two I had to go without NoScript was quite painful :)

Re: Firefox 84.0

#104

Post by IshKebab »

bryanlarsen wrote: post #44
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?

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…

Do you expect a Google competitor to step in with $400m/year of funding though?

Re: Firefox 84.0

#105

Post by cesarb »

bzbarsky wrote: post #91
nerdponx wrote: post #68

Earlier quoted context omitted.

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?

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?

Re: Firefox 84.0

#106

Post by penguin_booze »

ducktective wrote: post #10
antouank wrote: post #4

> Additionally we'll ship an accelerated rendering pipeline for Linux/GNOME/X11 users for the first time, ever!

I'm seeing high CPU usage on YouTube after recent updates on Xubuntu. I think it started when they enabled GPU acceleration by default. Previously I could watch even FHD videos without much fan noise, but after recent updates, fans spin at the max speed by playing even 480p quality vids. Anyone else?

I'm on Linux. I stubled on webrender from a blog yesterday, and enabled it. My observation was the same - high CPU usage, so I then disabled. Got 84.0 today, and gave it another go. It appears to be behaving well so far. So I'm guessing there was some fix in 84.0 that made it work for me.

Re: Firefox 84.0

#107

Post by est31 »

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 think it's a problem from a security point of view to allow websites to do this. Often the server that runs on localhost is poorly secured and may even expose "Access-Control-Allow-Origin: *" headers. And even if it doesn't, the browser still has to run a request to find out whether such a header is present, so some attacker controlled data does end up in these services. This in turn can be used for attacks.

Maybe these services were coded assuming that an URL can only be 1 kb long? What if you overrun that buffer?

For example did you know that cups runs a web server at http://localhost:631 ?

TLDR: not a fan of this.

Re: Firefox 84.0

#108

Post by arp242 »

cesarb wrote: post #105
bzbarsky wrote: post #91

Earlier 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?

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.

Re: Firefox 84.0

#109

Post by [deleted] »

bryanlarsen wrote: post #44
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?

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…

[deleted]
Post reply on HN