I just updated my wish regarding cool PDF like website zooming
http://bugs.kde.org/show_bug.cgi?id=100284#c3and was wondering: how does KHTML render sites anyways? Could someone please explain to me which steps a HTML is piped
through? Because Konqui uses a lot of memory (absolute, not relative..) for f.e. if you open a bunch of screenshots...
Each tab can take some MB, while the displayed files are often much smaller in size.. how comes this, how exactly is a
tab stored in memory? And where do f.e. image tabs reside in memory? The X server? Or is only the current image
transferred?
Why I am asking this:
I thought it would maybe improve performance and memory consumption if all loaded sites/images are stored in memory, but
not the rendered result, and no images in the X server.. so Konqui would need to rerender each document on each tab
change, but I think it can do that fast enough..?! Or am I misunderstanding things grossly here?
Problem remains with active content like those nagging flash adverts. No clue what to do with those.
Damn, a web browser is some complicated piece of technology. Woahh.
regards folks
