This drives me up a wall. Short of UX and front end devs taking this seriously, ive always wondered if theres a way for an OS level / browser level UX library to keep track of the "clickable state" 20ms ago (configurable to the user's reaction time liking) so the thing I click on is what my brain thought it was clicking on.
The better solution is developers and designers taking a sense of pride and craftmanship in this sort of thing. So many of my least favorite interfaces are presumably designed and implemented in an environment with a gigabit connection to their apps backend so they never catch it.
This one has somehow found its way into the iOS photos app of all places. Something is deeply amiss in the industry if the corporate avatar of design misses that one.
I sometimes use a trackball — without a "scroll wheel".
So in Google Maps on the web, I'd have to click the + and - buttons on the screen repeatedly to zoom in and out.
But those buttons don't always stay put. There is a status bar underneath it, that sometimes contains text so long that it wraps: and then that pushes the buttons up.
This. I'm not a fan of expanding links, like when a user hovers over a small button with an icon, and it expands to reveal the full button name, but the content around it (like other buttons) shift because of the size change.
It's a bit ironic the laws of UX is presented this way with gaudy graphics that are cumbersome to scroll through. They take up a lot of screen real estate and would disrupt what the typical user is used to.