Should we preload the preview pages?
in
1 post,
1 voice
joeytwiddle
Script's Author
|
It can be a little slow to actually load a page in the preview pane. One solution to this would be to have a few (say 3) hidden IFRAMEs, into which the first three result pages are automatically preloaded. Now when the user hovers, the corresponding IFRAME can be displayed and the page may already be fully loaded for him. :) If the user moves down the results list, we can preload the 2 results following the one he is currently viewing. Disadvantages: It's going to be a bit heavier on your browser, and on the websites we preload, some of which we might not even view. Some might call this unsociable or irresponsible. If any one of the pre-loaded pages happens to have a frame-escaping javascript, then it will break out of its IFRAME and we won't see any of the other results. (Anyone know a way to stop frame-breakouts?!) This is an existing problem anyway, but by pre-caching we multiply it. We will have to track the main result links, ignoring "Cached", "Similar Pages" links etc. If Google changes their page format, our script will now run a higher risk of breaking. This would of course be an option for the user. (Well a boolean at the top of the script. ;) Do you want this? Or would you rather keep the script simple? |
