A great one lately is Wikipedia's new search with suggestions. If I'm typing in the search bar, I may type a complete query and then press "Enter". Well, if my mouse happened to be hovering over a suggestion, then "Enter" will choose that suggestion instead of completing my chosen query instead.
Front end developers: stop moving things that I’m about to click on
41–50 of 365 posts
Re: Front end developers: stop moving things that I’m about to click on
#42Honestly, everyone knows this. If you're creating sites that do this in 202X you're just being willfully ignorant/lazy. There are plenty of component libraries for rendering placeholder components in the popular frameworks, react has the suspense API etc etc for exactly problems like this.
Re: Front end developers: stop moving things that I’m about to click on
#43The gold standard for the web should be: Craigslist Fast, functional, responsive.
Or McMaster Carr. RS, with it's laggy backend (I assume, as their recent UI shinification didn't change it: it was bad before) could learn a lot from them. Then again, McMaster Carr want you to use an app on mobile and the new RS site works on mobile quite well, with the lag more hidden by the inefficiencies of mobile browsing in general.
McMaster Carr is one of the greatest websites there is. It's incredibly easy to find just about any kind of hardware.
Re: Front end developers: stop moving things that I’m about to click on
#44All the examples are a case of unfortunate timing: asynchronous things doing late UI replacement that happen to conflict with the time window in which you click. That's amateur stuff. Our car does this intentionally. As your finger is in mid-air, on its way to hit something on the touch screen, it's detecting this motion and then shows a context bar in the top and bottom by the time you land your finger. Which often…
Some phones are great at this - if you're on a call and want to look up your account number to give to a service rep, getting close enough to tap an app button turns off your screen, even in speakerphone mode. Pull back your hand to tap the power button to turn on the screen? Well the screen detected your finger left and turned on just as you were hitting it. Now you're in a third state, intentionally off screen, and just moving your finger around the sensors won't change that. You have to tap the same power button again, and then start the process all over.
Don't forget you've been talking to a service rep this whole time, or more likely sitting going "uhhhhhhmmm..." like a dipshit.
Re: Front end developers: stop moving things that I’m about to click on
#45I have googled the letter "n" countless times just trying to visit news.ycombinator on firefox android...
Re: Front end developers: stop moving things that I’m about to click on
#46Latest one to catch me out on is when receiving calls on my Pixel phone it will pop up "screen call" as an option where the "accept call" button had been half a second earlier, and not let you override it to actually accept the call.
Re: Front end developers: stop moving things that I’m about to click on
#47I swear some of these are intentional results of bad A/B testing (or active maliciousness) - especially as it often seems that what you want to click moves out of the way for an ad.
Re: Front end developers: stop moving things that I’m about to click on
#48Honestly, everyone knows this. If you're creating sites that do this in 202X you're just being willfully ignorant/lazy. There are plenty of component libraries for rendering placeholder components in the popular frameworks, react has the suspense API etc etc for exactly problems like this.
When it comes to ad links I've always wondered if it's ignorance or done deliberately to make you click on the ad.
Re: Front end developers: stop moving things that I’m about to click on
#49A particular bane of mine is the self-oscillating UIs, youtube is particularly bad at it these days - if the mouse pointer is in 'just the right place' (which is bigger than it sounds) then you get the seek-bar preview frames popup, which moves things just enough that the mouse pointer is no longer over the area that triggers it, so it vanishes, and the whole thing starts again.
Where is that spot? That has never happened to me, but I'm curious to see what it looks like.
Re: Front end developers: stop moving things that I’m about to click on
#50I agree with [this][1] idea: > an autocomplete has one chance to reorder per keystroke. if you got it wrong and you have a better ordering a bit later you must “swallow the sadness” (as per the original author of this wisdom) but never change already displayed items [1]: https://twitter.com/dan_abramov/status/1470751551568363530
Can someone please tell the Windows Start Menu designers? Have completely ruined the experience as it constantly juggles items as its heuristics are seemingly updated. I especially enjoy how Bing results get prioritized over local applications and files.
I cannot figure out how "upd" shows Windows Update but "update" does not.