Why is it not common UX practice to start ignoring user input prior to rearranging the UI, and only responding to user input once the layout has settled and perhaps after a short delay?
It’s very frustrating to reach for an option in a list, only to have the list repopulate just as I tap, inevitably on an undesired option
I’m not even talking solely about web design: even the Google Cast destination picker does this and it’s native Android code
Has Apple solved this over in iOS land?
I agree, just a day ago I accidentally clicked Send this way, and sent a silly empty message on one site.
I wonder if this is mainly an issue/feature of web engines? Maybe the idea is to make the initial load faster?
Yeah, I think there are some cases where it’s a performance thing, sure: e.g. a list that displays a few hard-coded common options, and is repopulated with personalised options once they’ve been fetched from a back-end
Lazy loading, you mean?
I imagine, is this something we can disable?
There was UnLazy for Firefox, but I think it’s not developed anymore and on some pages won’t even work because they all use different techniques for lazy loading.