News for hackers. Stuff that matters.

A comment on Just how fast is too fast when it comes to web requests?. Parent comment

Re:Just how fast is too fast when it comes to web requests? by rane on Wednesday November 13, 2019 @03:21AM (#21522030)
You don't need a spinner if feedback from clicking the button is sufficiently quick.

According to Google that would be around 100ms.

> Guidelines:

> Process user input events within 50ms to ensure a visible response within 100ms, otherwise the connection between action and reaction is broken. This applies to most inputs, such as clicking buttons, toggling form controls, or starting animations. This does not apply to touch drags or scrolls.

https://developers.google.com/web/fundamentals/performance/r...

[ Parent | on HN ]
Re:Just how fast is too fast when it comes to web requests? by ricardobeat on Wednesday November 13, 2019 @03:49AM (#21522175)
That only applies to actions which have an immediate, perceivable effect, which might not be the case for submitting a form, as described in the OP. For example, opening a dropdown, selecting a checkbox or radio button, etc.
[ Parent | on HN ]
Re:Just how fast is too fast when it comes to web requests? by toastal on Wednesday November 13, 2019 @03:57AM (#21522228)
In the case of network it's also presupposing that the user's has a low-latency, fast connection--which should basically never be assumed.
[ Parent | on HN ]