![]() In other words, if the server hosting the page fails to respond for more than 1 or 2 minutes or whatever, then Safari interrupts the page loading process and displays an error message instead. Safari has a built-in mechanism that instructs it to give up on the process altogether after a while, presumably through some kind of “time-out” countdown. For whatever reason, the connection to the server gets lost, and Safari is unable to continue loading the page. In my low-bandwidth working conditions, this happens fairly often. This was not just an indication that the loading process was still in progress, but that it was actually stalled. Because sometimes the blue bar would stay there, but would stop moving. by changing its state gradually, in real time, as the page was being loaded.Īnd that’s a crucial distinction. It gave an idea of how much of the page had been loaded because the length of the field for the site’s URL doubled as an indicator of the estimated length of the entire loading process and the length of the blue bar within that field was an indicator of how much of this length had been covered.Īnd it indicated to the user that something was taking place not just by being there, but by moving along, i.e. The blue progress bar in the previous versions of Safari fulfilled both purposes:
0 Comments
Leave a Reply. |