Helping people with computers... one answer at a time.
Sometimes you can begin using a web page before it's fully downloaded, sometimes you can't. We'll look at one common reason why that might be.
I have a dial-up internet connection and the slow speed is probably the problem, but lately I have noticed that on some web pages I have to let the page completely load before I can hit login or whatever is the next logical thing to do. If I hit login before the current page loads I'll get the browser error screen. Aren't there supposed to be some interrupts in good programming that allow the keyboard to take control of the situation before the web page is completely loaded? One of the pages I am having trouble with is Discover Card while Master Card works like a champ. I suppose I could minimize the problem by using the other card as the main one.
I can only speculate, but I've got a pretty good hunch as to what's going on. It is likely a design issue, meaning that it's a side effect of how that particular web page is constructed.
Absolutely you can interrupt the page download, but the problem is that if you do the browser may not yet have everything it needs to do what you've asked.
So why does it work "early" for some and not for others?
It's all about web page design.
And I think that's best described if we look at a hypothetical sequence of events when you download a web page (for the pendants out there, I'm not saying this is exactly what happens: this is an over-simplification for purposes of example):
You request the login page from your bank's site.
Your browser begins downloading the HTML file that is that web page.
The browser may begin displaying the HTML before the file is completely downloaded. Typically this happens from the top of the page down, but this can be severely impacted by specific page design.
As it displays the page the browser encounters images, which are actually separate requests it then makes of your bank's web server. It may make those requests when the image is encountered, or it may wait until the entire HTML file has been downloaded, or it may happen somewhere in between.
At some point that HTML file we started with finishes downloading.
The page is "done".
That should be enough to at least theorize why logging in before a page has completed download works for some sites and not for others.
As you've experienced you can quickly get a sense for which sites allow you to login early. Unfortunately there's no real remedy for the others. In some cases all this is also impacted by how your browser chooses to perform its task, so if you're really motivated you can try the page in a different browser. It might work, but it might not.
Comments on this entry are closed.
If you have a question, start by using the search box up at the top of the page - there's a very good chance that your question has already been answered on Ask Leo!.
If you don't find your answer, head out to http://askleo.com/ask to ask your question.