Browser Preloads Next Page | |||||||||||||||||
We need a standard HTML code for the "next page" link, and browsers that automatically PRELOAD the "next page" into a "next page" cache.... so that if I click "forward" (eg. alt left arrow, or however you do it on your browser of choice) I immediately see the next page.. I often read multipage articles. There is only ONE place I'm going after I finish page 3 and that is to page 4. I know it, you know it, and the broswer should know it. The browser should be able to detect the next page link and preload it, so that when I hit "next page" the next page is instantly available instead of having to wait the interminable 1, 2, 3 or even 10 seconds it takes for the page to download. Think of the person hours that could be saved..... the billions of articles with multiple pages .... the 3 times or 7 times billions of multisecond waits for the next page to download that could be eliminated. Spouses would have more time for each other... parents would at last be able to spend time with their children.... Think of the humanity. Two things are needed. An HTML standard and compliant browsers. I have no idea how to make these things happen. Probably Mozilla and Mozilla Firefox would be the place to suggest this feature.... but unless people code their pages with the standard HTML it won't happen... so you'd probably need to get MS and Explorer on board with it. However even without an HTML standard, I'd bet that a browser that automatically preloaded any link with the text word "next" in it (even without an HTML standard) would correctly cache the likely next page in most instances. Cheers.
mikemike, Jul 18 2004
What do you think of this idea or comment? | |||||||||||||||||
Users who liked this idea also liked: | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
Add your comment
Although this is probably a good idea (and I am not voting against it), the concept that 10 seconds is an interminable amount of time strikes me as rather strange.
Already done. Check out rel="prefetch" links and Mozilla Firefox.http://simon.incutio.com/archive/2002/10/17/mozillaPrefetching
dumky, your link seems to show that it can be done... not that it has been done. (Do I misread it?)
Glad to see someone has thought about it.... why isn't it routinely available (as a selectable option) on Mozilla, Mozilla Firefox and (cringe) Explorer?
But thank you for providing that.
sand.... 10 seconds is completely unacceptable when you are in the middle of a sentence or idea, and / or trying to get through an article quickly. Everybody lives life at a different pace though. :-)
Sand,Welcome to the real world. Either you're retired and don't know what to do with your spare time or too old to use the internet much; or perhaps both.
To translate the 10 second delay into terminology you might relate to, try to imagine if every time you went to turn the page in a book (assume it is an interesting story) it got stuck and you had to wait 10 seconds to turn the page. Or if every time you went to take a sip of prune juice, you had to hold your glass at your lips for 10 seconds before your mouth would open to take a sip.
I disagreed with this idea for a number of reasons.
1. It is a waste of bandwidth. Let's say you look at the first page of an article and decide not to continue, bandwidth used to preload the subsequent page(s) is wasted.
2. It could produce incomplete pages. Example: You're reading a message board thread. When you begin reading the first page there is only one post on the second page, so the second page gets preloaded with one post. It is quite possible that more posts will be added to the second page before you actually finish reading the first and click the next page link, but you would only see the first post unless you refreshed the second page.
3. It can be done already at the discretion of the web developer using the prefetch command (Google currently uses this to preload the first result of searches).