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

221–230 of 328 posts

Re: Firefox 84.0

#221

Post by edoceo »

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.

Yes, I have a localhost running python script to communicate with serial devices and printers, so this makes it a bit easier. (I currently slide in a self-signed cert)

Re: Firefox 84.0

#222

Post by hutzlibu »

JoshTriplett wrote: post #207
IshKebab wrote: post #104

Earlier quoted context omitted.

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

Yahoo outbid Google one year, and Firefox duly changed the default search engine for a while.

FFs market share was a bit higher back then, though.

I see the main asset of firefox as being

a) not google tech

b) mobile browser with ublock

c) tech nerds with tons of custom FF addons, never wanting to switch

So I don't see them go away anytime soon, but I also see nothing to stop the decrease of their marketshare. That means, unless mozilla would focus on their core values again. They lost much trust with quite some shady actions now, over the years.

Re: Firefox 84.0

#223

Post by mdoms »

nine_k wrote: post #205
mdoms wrote: post #198

Earlier quoted context omitted.

What could I possibly mean by not native other than not native? Bugs from a quick play-around (comparing with Microsoft Edge): * The zoom with touch pad has a weird latency not present in Edge. * Zoom on touchscreen is janky and jumps around. * Zooming in and then out often (but not consistently) stops working half way through the gesture. * Scrolling behaviour while zoomed is wildly different to native apps like Edg…

Cannot confirm any of these points (Win 10 pro, Thinkpad T490p). Everything is buttery smooth, and does exactly what I would expect it to do, both zooming and scrolling. (I only tied the touch screen, though.) Maybe check your touchpad and touchscreen drivers.

It works perfectly in literally every piece of software I use other than Firefox (which I don't use, for this reason).

Re: Firefox 84.0

#224

Post by mdoms »

jamienicol wrote: post #201
mdoms wrote: post #194

Earlier quoted context omitted.

It no longer jumps in big increments but it's still janky and very much non-native.

Why do you mean by non-native? If it's janky it might "just" be a performance issue. If you could grab a profile from profiler.firefox.com that would be much appreciated

By non-native I mean non-native. I am definitely not going to do that, I will simply keep using Edge.

Re: Firefox 84.0

#225

Post by bigbubba »

pimterry wrote: post #150
est31 wrote: post #107

Earlier quoted context omitted.

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…

Yes, it's possible localhost servers can have security issues, but: * This only affects servers that do indeed serve the "anybody can talk to me" CORS headers. For anything else, standard cross-origin restrictions apply. A simple localhost server that has ignored this issue and isn't aware of CORS at all is generally not vulnerable. * This change doesn't actually increase this risk, it decreases it! Localhost request…

> This only affects servers that do indeed serve the "anybody can talk to me" CORS headers.

That's simply not true, it can effect things that aren't even web servers at all: https://en.wikipedia.org/wiki/Inter-protocol_exploitation

Re: Firefox 84.0

#226

Post by pt_PT_guy »

I truly love Firefox for what it (should) mean: an opensource browser that fights for open and diverse web. Specially now that everything is Chromium based.

However I'm very disappointed with the corporate way it is managed. Lot's of money for the CEO and cutting development funds.

Things I would absolutely buy from Mozilla: private internet services

- Something like Zoho: Calendar/Mail/Notes replacement for Google services!

- VPN server if available in my country

I want to ditch google/apple/microsoft for something "encrypted/private" first. And self-hosting is just a hassle. Provide me easy, "self-hosted"-like services please.

Re: Firefox 84.0

#227

Post by endemic »

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,.

Plus Google can't intentionally cripple Edge without shooting themselves in the foot.

Re: Firefox 84.0

#228

Post by frongpik »

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 should sign a deal with EU and get funding from them. Their selling point could be "Unlike other browsers, Firefox won't send data to the US and will enforce GDPR even on sites that arent compliant". Otherwise Firefox will be an expense account of some google exec and be treated as such.

Re: Firefox 84.0

#229

Post by matsemann »

mdoms wrote: post #198
muizelaar wrote: post #186

Earlier quoted context omitted.

What do you mean by not native? What bugs do you see?

What could I possibly mean by not native other than not native? Bugs from a quick play-around (comparing with Microsoft Edge): * The zoom with touch pad has a weird latency not present in Edge. * Zoom on touchscreen is janky and jumps around. * Zooming in and then out often (but not consistently) stops working half way through the gesture. * Scrolling behaviour while zoomed is wildly different to native apps like Edg…

Drop the snark. Drop the dismissive tone. You have had Fx people replying to you directly. Saying they don't care is shitty behavior from you.

Re: Firefox 84.0

#230

Post by mdoms »

matsemann wrote: post #229
mdoms wrote: post #198

Earlier quoted context omitted.

What could I possibly mean by not native other than not native? Bugs from a quick play-around (comparing with Microsoft Edge): * The zoom with touch pad has a weird latency not present in Edge. * Zoom on touchscreen is janky and jumps around. * Zooming in and then out often (but not consistently) stops working half way through the gesture. * Scrolling behaviour while zoomed is wildly different to native apps like Edg…

Drop the snark. Drop the dismissive tone. You have had Fx people replying to you directly. Saying they don't care is shitty behavior from you.

The bug report is 8 years old and they have finally implemented a "solution" that does not work properly.

https://bugzilla.mozilla.org/show_bug.cgi?id=789906

Post reply on HN