On Thu, 26 Feb 2015 15:09:15 -0300 Jorge Arellano Cid <jcid at dillo.org> wrote:
Most probably remembering the scroll position for Back and Forward.
Well, surprisingly not. I didn't tested extensively, but simply browsing several URLs and navigating forward/backward works fine and the page is positioned exactly where the page was left.
Let's say you set the fail timeout to 30 seconds... Can you imagine it?
Now if the page has let's say 7 stylesheets. Which compete with the main page, and dozens of images for bandwith, add the "temporary unavailable" answers, or simple fails that need a retry which some servers use to avoid bots wasting BW, or peak usage hours, etc. Then, how many do we expect before drawing?
The point is: there're plenty of factors.
Well, yes there are plenty of factors. But IMHO, there are some arguments for the opposite: If the page is already received (at least partially) there is very big probability that the CSS files (if they are on the same web site) will be delivered successfully and approximately in the same time range. If this time is small enough, why not to wait a little in order to get better user experience (not flickering pages). There is some network performance limit, where rendering the page twice will be slower than waiting for the CSS files and rendering once. As long as with the time the network performance increases and with the Dillo supporting more and more HTML features, the rendering speed is expected to decrease, then this wait for the CSS files probably will be implemented one day. This way IMHO, some more complex logic (and probably some heuristics) could improve the overall performance. At least, this feature deserves dillorc option. :)
I'd like to look at it but currently work on a resize/redraw bugs fills my time.
Take your time! You are doing great work in all cases. Best Regards. -- http://fresh.flatassembler.net http://asm32.info John Found <johnfound at asm32.info>