Inside look at modern web browser

Re:Inside look at modern web browser – part 4 by pcwalton on Friday September 21, 2018 @10:03PM (#18044062)

I like the writeup and drawings, but I have to mention that this is a bit too specific to browsers as they work right now, specifically Chrome. Having to pay attention to the paint/compositor distinction and layer count is something that newer renderers like WebRender make obsolete. You don't have to worry about layer count causing needless overdraw if you have a unified system so that occluded content is culled, for example.

WebRender is already turned on by default for many users in Firefox Nightly…

[ Parent | on HN ]

Re:Inside look at modern web browser – part 4 by lwansbrough on Saturday September 22, 2018 @04:43AM (#18045134)

Unfortunately for Firefox this concept doesn’t work very well on the CPU it seems. Every time I open Firefox on my (slightly older but still very capable) MBP the fans go nuts and the CPU could fry an egg. Probably has something to do with my integrated graphics chip.

And yeah I’m going to keep posting this anecdote until Mozilla acknowledges the problem.

[ Parent | on HN ]

Re:Inside look at modern web browser – part 4 by mccr8 on Saturday September 22, 2018 @09:57AM (#18045969)

Do you have scaled resolution enabled? If so, that sounds like this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042

I think there's been a little bit of progress on that issue, but not much, unfortunately.

[ Parent | on HN ]

Re:Inside look at modern web browser – part 4 by pcwalton on Saturday September 22, 2018 @11:17AM (#18046301)

Sounds like Core Animation could fix that issue? I have a patch for that almost ready to go (mstange is testing it as we speak).

[ Parent | on HN ]

Re:Inside look at modern web browser – part 4 by minitech on Saturday September 22, 2018 @05:19AM (#18045222)

> WebRender is already turned on by default for many users in Firefox Nightly…

Are you using Nightly?

[ Parent | on HN ]