Today saw the article ( the Response Times: at The 3 Important Limits ) feel very good, there is simply finishing the next point.
Response Times: The 3 Important Limits
The basic guidelines on the operation response time of more than three decades has not changed, and these guidelines are not limited to a door or technical language.
- 0.1 seconds is instantaneous user experience boundaries, which means that no prompts (feedback) to display the results directly.
- 1 second: even if you feel the delay, but still feels smooth and maintain continuous operation, in general, the delay between 0.1 seconds to 1 second, is no special tips, but the user will still feel the loss of direct response.
- 10 seconds is the user focus on a single task limit for longer delays, users will perform other operations without waiting for the computer is finished. Therefore, during the execution of a computer user should be given prompt. As the time for the user in terms of ten valuable tips now so important, otherwise users do not know what to say.
other
- The response time of the computer in general, the sooner the better, but the bottom line is to ensure the availability, should not be too fast so that the user can not operate. For example, the scroll speed is too fast to make a list of users can not be stopped in time targeted content.
- When an operator needs to wait more than 10 seconds, the user should be given a percentage of the progress bar, this effect will be far better than the remaining time only prompt the user, and may interrupt or cancel a given operation.
- For the progress of the operation can not be calculated, the user should be given appropriate feedback. For example: When scanning the database of unknown size, the table can be printed scanned. Another alternative is to provide a simple animation of waiting, prompts the user to program in operation.
- For 2 to 10 seconds of operation, if the percentage progress bar appears to be overkill, and would enable users to display excessive flicker kind of effect is not good. Then you can use only a "busy" animation, and accompanied by a changing digital prompt progress in the right position, the better.
The actual
1, there are many tabs or album turned round on the page, these mostly use the mouseover event is triggered. This will inevitably lead to a problem, mouse inadvertently triggered across the region, will be switched, it gives a flicker of feeling.
Specific solution: Since the delay in 100 milliseconds, users will not be aware of, it would increase the trigger delay, the code is as follows (using jQuery coding to do presentations).
var timer; // Handle Time
$('div.tab-holder li').hover(function(){
clearTimeout (timer); // First clear handle on the first registration of
timer = setTimeout(function() {
// perform handover
}, 100);
});
2, in which the application Suggest, if every keyboard event triggers a request, then this one will be many invalid requests and cause some pressure on the server. Suggest, so most are used as one example of the delay time is generally controlled within 200 to 250 ms.
Reproduced in: https: //www.cnblogs.com/rainman/archive/2011/01/04/1925814.html