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

Firefox 70

hacks.mozilla.org

Post reply on HN
Print view View original

341–350 of 468 posts

Re: Firefox 70

#341

Post by tass »

vrodic wrote: post #334
tass wrote: post #294

Earlier quoted context omitted.

Does HTML video need to catch up based on the most recent keyframe? If they don't render while backgrounded, how do they do that without being noticeable?

Chrome does this for a long time now and I don't consider it an issue. You see a frozen version of the last decoded keyframe until the next one is decoded. Elegant solution IMO.

That makes sense, it seems I haven’t looked closely enough to notice.

I couldn’t find info on how often a keyframe is expected from YouTube, but I’m recalling the bad old divx days where you sometimes had a frame per scene and skipping was very slow.

Re: Firefox 70

#342

Post by pfundstein »

geraltofrivia wrote: post #46
theodorejb wrote: post #17

Wow, blown away by how much better the new password manager is! If they add support for custom fields on each login, this could almost completely replace my need for a 3rd party solution.

Agreed. I'm thinking of cancelling my Dashlane subscription and moving to this Password Manager now. Firefox's Lockwise App (on android) leaves a lot demanding though.

Wow, a subscription password manager.

Re: Firefox 70

#343

Post by jangid »

> hard to tell which script changed the page and caused the issue when you run into a problem

Firefox 70 is developer's delight. Breakpoints on DOM changes is the one of the most difficult parts. FF70 solves this. Great.

Re: Firefox 70

#344

Post by ripdog »

dwaite wrote: post #236
pmontra wrote: post #230

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

My understanding is that most video websites like Youtube use Media Source Extensions, a standard which allows javascript to download and assemble video streams in non-standard ways. This work is done by page JS and passed to the browser to decode and render. AFAIK youtube uses this to implement DASH streaming.

Presumably there is no easy way to disable page JS but keep your youtube video downloading.

Re: Firefox 70

#345

Post by CamperBob2 »

marius_k wrote: post #26

I noticed that firefox (dev edition) got rid of possibility to disable update notifications. I prefer my browser to be updated from repository rather than by itself. Did anyone has the same issue or found some workaround?

Wow. With attitudes like this:

"The discussion about the method for disabling updates has been had over and over already, there is nothing left to say about it, and the change will not be reverted. You've been given workarounds for your problem. Please do not reopen this bug or file any others asking the same thing."

... who needs Microsoft?

Re: Firefox 70

#346

Post by theonemind »

freddie_mercury wrote: post #335
tomaskafka wrote: post #219

Earlier quoted context omitted.

> 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…

Classic HackerNews " This is so easy and I, a software developer with no actual experience in that area, know the obvious solution that eludes that hundreds of developers with actual experience in the area. Meanwhile, I take umbrage when my product manager tells me that implementing the next feature will be easy and I'm exaggerating how complicated it is."

Perhaps so. But,

if (not_visible) { suspend_wait_and_stop_consuming_resources }

I can imagine that it gets massively more complicated. However, as, say, an executive, this probably indicates that you can lean on your sw dev staff to approach the asymptotic ideal that looks so simple if you really care about the goal.

Re: Firefox 70

#347

Post by perditus »

Scarbutt wrote: post #199
chrischen wrote: post #63

Earlier quoted context omitted.

Battery life is my primary concern, and unless they release battery life benchmarks I’d be hard pressed to switch off of Safari.

Safari means no ublock, the web without is annoying.

Disconnect works well enough.

Re: Firefox 70

#348

Post by chenster »

needle0 wrote: post #336
chenster wrote: post #69

Earlier quoted context omitted.

You can also use Brave browser, it's basically Chrome with the ad tracking removed. With that, almost no reason to switch to another browser.

You’re still contributing to the Chromium engine monoculture, though.

Guess we are dealing with purists here. Mind you that Chromium is free and open-source just like MySQL. A strategical move by the community to fork MySQL to MariaDB to ensure it remained free and open from the tech giant after it was acquired by Oracle. How Brave is any different? It made a similar move. Some people hate crypto. Fine. Personally I've never used the Brave crypto. Perhaps FF 70 has completely fixed its performance problem, sure, happy to switch. But before that really happens Brave is still a viable interim solution.

Re: Firefox 70

#349

Post by deaddodo »

saagarjha wrote: post #291
deaddodo wrote: post #289

Earlier quoted context omitted.

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

No, I'm not; I'm actually typing this from WebKit on Linux. I'd actually guess that WebKit runs on more platforms than Blink does…

I didn't say it didn't run on other OSes. But the big ones are mostly iOS and it shows in the targeting of the development. Blink is what's on most (non-gecko/servo) browsers people use now (chrome, chromium, Opera, the new Edge browser, etc).

> I'd actually guess that WebKit runs on more platforms than Blink does…

I'd say they're probably at parity, if not a small edge given to Blink since an entire OS is built around it. Which would be the only exclusive case of the two I can think of.

I'm actually curious which WebKit browser you're using. GNOME Web?

Re: Firefox 70

#350

Post by deaddodo »

ekianjo wrote: post #297
deaddodo wrote: post #289

Earlier quoted context omitted.

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

No, Webkit used to be a cross platform renderer which work started on Linux in the first place, so it is definitely not MacOS only.

I never said it was Mac only. I said it's development now was mostly focused on iOS browsers. You can obviously use GNOME Web and the like, but most big browsers (especially cross-platform) that aren't Gecko-based are Blink-based (Chrome/Chromium, Opera, Edge beta)
Post reply on HN