> It is difficult currently. Once the page is drawn, its just a long bunch
> of pixels. A scrollbar for showing the position in the long bunch of
> pixels needs to be calculated also, which would require doing the
> calculations anyways. If you have an answer though, by all means pass it
> along, it would provide functionality for a copy text also.
Right now, the height of the displayed page is recalculated when you
scroll up or down using the chevrons on the scrollbar as I understand it (to
account for cases where you turn on different features, turn off images,
etc.). That's something we have to be careful of as well, when we disable
images, change the font size/height, and so on. All of these factors change
the height of the displayed page, and hence the amount by which it can be
scrolled.
What if we just "cache" a calculation of the page above and below
the one actually displayed. Much like blitting an image offscreen, can we do
some sort of frontloading of the actual pages above and below the displayed
ones to speed up the scrolling itself?
Panning and scrolling images on the screen is much faster than
scrolling a displayed page by one line. Logic of data size and math involved
implies that it shouldn't act that way. Just my opinion.
*inserts foot back in mouth and gets back to work*
