Live data from Hacker News

Firefox 70

hacks.mozilla.org

301–310 of 468 posts

Re: Firefox 70

#302

Still has serious bugs with certificates that I don't think will ever be fixed. On Mac, loading all the appropriate DoD certs and trying to log into OWA causes an unrecoverable hang. Loading only DOD ID SW CA-37 will allow login to numerous sites. However, after closing those tabs, all other sites time out while "Performing a TLS handshake..." Lastly, quitting Firefox after a PIV/CAC login causes an unrecoverable han…

Have you filed a bug report on their bugzilla? Is there a way they can test test certs? Are there public facing websites or are these all going to be internal/government?

Re: Firefox 70

#303
post #142
post #68

Earlier quoted context omitted.

I installed it, but this should be solved at the native level and not on JS.

What difference does it make?

One aspect is having to maintain double dictionaries. Back in the early Mac OS X days the system-wide dictionary was one of the little features that made me happy.

Re: Firefox 70

#304

Love the new mission statement: `Firefox is tech that fights for your online privacy.` Apple has demonstrated that privacy is a very effective value proposition. Maybe Apple should look into investing in Mozilla/Firefox.

But they ship their own browser?

Yea and they don't allow Firefox on iOS, even though Google allows it on Android and they too have their own browser!

Re: Firefox 70

#305

Still has serious bugs with certificates that I don't think will ever be fixed. On Mac, loading all the appropriate DoD certs and trying to log into OWA causes an unrecoverable hang. Loading only DOD ID SW CA-37 will allow login to numerous sites. However, after closing those tabs, all other sites time out while "Performing a TLS handshake..." Lastly, quitting Firefox after a PIV/CAC login causes an unrecoverable han…

Have you filed a bug report on their bugzilla? Is there a way they can test test certs? Are there public facing websites or are these all going to be internal/government?

I've filed some bug reports but not others. The issue is it's such weird behavior it's hard to isolate.

The issue seems to be related to PIV/CAC cards specifically, which obviously increases the difficulty of anyone on the team replicating the bug.

Re: Firefox 70

#306

Earlier quoted context omitted.

WebKit also works on other platforms.

You're thinking of Blink. WebKit is pretty exclusive to macOS and iOS these days.

Even back in 2014, I was developing my own browser with webkit:

https://austingwalters.com/simple-web-browser-in-cpp-using-q...

Works on any OS I've tried.

Re: Firefox 70

#307

Earlier quoted context omitted.

But they ship their own browser?

Yea and they don't allow Firefox on iOS, even though Google allows it on Android and they too have their own browser!

firefox (and lockwise) are very much on iOS and very well integrated with the system.

Re: Firefox 70

#308
post #236

Earlier quoted context omitted.

YouTube music video running in another tab. Should it stop render the video and keep playing the audio? Maybe feasible but it should keep receiving both the video and audio data. Stop all of it? Not what I wish to happen.

The javascript engine and rendering engines are what are generally affected by being backgrounded. So yes, generally the media library will continue receiving the combined video/audio stream and not bother rendering the video frames

Youtube uses the Media Source Extensions API, which means that JS is responsible for fetching compressed video data and feeding it into the decoder, so it can implement adaptive streaming. Pause JS for more than a few seconds and the video will stop playing.

Re: Firefox 70

#309

I am not a Firefox user but know that matching Webkit performance on macOS is going to be very hard. So just fired a test on my Macbook Air - Safari 13 vs Firefox 70. Opened top 10 links from techmeme. Both windows in background. Firefox 70: Energy use 30-200; CPU 20-25%; Threads 82 Safari 13: Energy use 0.1-5; CPU 2-5%; Threads 11 If this is to celebrate I can only imagine what the things looked like before this rel…

IIRC Safari achieves this by suspending the processes in background tabs, which could be running inefficient JavaScript (polling for new ads etc). There's no cross-platform way to do this, but I think Mozilla absolutely need to try and find a way to address this. Web sites cannot be trusted to write efficient well-behaved JavaScript and so the burden of taming it falls upon the browser. There is probably some throttl…

Firefox can and does aggressively throttle JS in background tabs. However, it's not easy to do this in a way that doesn't break sites. Sometimes background tabs have JS doing actually useful work --- playing audio, running a simulation, receiving notifications, stuff like that.

I don't know what Safari is doing differently to Firefox, and no doubt Firefox can improve here, but when people say "it's easy, just completely stop running JS in background tabs" they have no idea what tradeoffs that entails. (Just as when people said "browsers should just refuse to autoplay videos" had no idea what they were talking about.)

Re: Firefox 70

#310

Earlier quoted context omitted.

> this means that my battery is going to last 4-5x longer with Safari Well it might last 4-5x longer if you run safari in the background, since that is what you tested. But wouldn't the real test be running both browsers as the active window and comparing those results? One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and w…

> One thing that Safari is incredibly good at (and its' engineers are proud of) is the ability to reduce resource consumption for non-active tabs and windows to nearly zero. I understand this is rare, but I just have a very very hard time understanding what is so hard about this. Page not visible? Just stop it. Stop the layout engine, stop the javascript VM. If there was a transfer in progress, let it finish, a page…

How can the browser distinguish between useful background Javascript (e.g. web based chat) and harmful background Javascript (e.g. advertising)?
Post reply on HN