3 ms·
> If the application you're using (the one(s) you're referring to when you say "cloud applications") is sending the key input to the backend and waits to render
by doix 4y ago
> If the application you're using (the one(s) you're referring to when you say "cloud applications") is sending the key input to the backend and waits to render it client-side until it received a response
I'm 99% sure nobody does that, that would be insane :D.
It's most likely caused by React and the use of controlled input components without thinking about performance. If your input sets it's value from React state, then you're updating the state on every keypress and re-rendering the component. In the most simple case, it's probably fine. But depending on your component hierarchy, it's pretty easy to end up in situation with over 50ms of typing latency.
- capableweb 4y ago> I'm 99% sure nobody does that, that would be insane :D. I agree, hence the surprise! Although parent explicitly calls out "cloud applications" so I'm guessing online has something to do with it. And in the context of online/offline, it wouldn't matter if it's internet connected or not, using controlled input components with state changes going through a deep hierarchy would introduce that sort of delay no matter if you're online or offline.
- TeMPOraL 4y ago> I'm 99% sure nobody does that, that would be insane :D. I imagine you haven't seen how people implement autocomplete on web forms ;).