Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Front end developers: stop moving things that I’m about to click on

medium.com

Post reply on HN
Print view View original

121–130 of 365 posts

Re: Front end developers: stop moving things that I’m about to click on

#121

Post by layer8 »

devnullbrain wrote: post #79
romellem wrote: post #7

I 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

I want foo. - Type 'f' - foo appears in the search. - Type 'o', because I type with 10 appendages and getting them to work together requires pipelining. - foo disappears from the search This should never happen.

This happens all the time on iOS with the “predictive text” feature, it’s maddening.

Re: Front end developers: stop moving things that I’m about to click on

#122

Post by bee_rider »

smeej wrote: post #69
joezydeco wrote: post #5

And stop asking me to do a survey on your website when I've only been there for 5 seconds.

Or sign up for your email list. I don't know if I want to hear from you ever again yet!

Would you like to subscribe to this substack before you finish reading literally the first article you’ve ever seen by this author?

Re: Front end developers: stop moving things that I’m about to click on

#124

Post by layer8 »

fbdab103 wrote: post #24
romellem wrote: post #7

I 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.

The sane alternative is to use OpenShell.

Re: Front end developers: stop moving things that I’m about to click on

#125

Post by tartoran »

solardev wrote: post #105
neilv wrote: post #80

This problem first occurred in the mid-'90s, and people saw it was a problem, and that's why we specified the image dimensions in HTML (before the GIF or JPEG header was loaded), so the layout wouldn't shift during load, when people were already reading and navigating. Since almost the beginning, graphic designers were trying to layout Web pages like an advertising brochure, lots of bad ways, rather than as hypertext…

In my experience, it was usually higher-ups and not the UX people who wanted to implement dark patterns. The UX people and devs wanted to make the enduser experience better (believe it or not), but were frequently overridden by some higher business priority (we NEED this popup as soon as the page loads! opt them in to all the newsletters by default! highlight the highest-margin products). Some companies just don't re…

Both front end and backend devs are the eqivalent of workhorses who implement whatever the business wants. Few can afford to keep their record spotless and while I struggle to point out my own blemishes I sure as hell worked on things I didn’t believe in or things I wouldn’t do if I didn’t have to earn a wage.

Re: Front end developers: stop moving things that I’m about to click on

#126

Post by ksherlock »

vidanay wrote: post #68
NikkiA wrote: post #15

A 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.

YouTube also has the problem that there is almost no dead space to "park" your cursor. You have to carefully place it in between autoplaying previews.

There is a youtube setting to disable that. Settings -> Playback and Performance -> inline playback.

Re: Front end developers: stop moving things that I’m about to click on

#128

Post by soulofmischief »

NikkiA wrote: post #15

A 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.

A general golden UX rule is to never cause layout shifts on hover events, preventing this sort of thrashing.

Unfortunately, Google/YouTube and others have lost the plot and no longer employ good UX professionals in their flagship products.

Re: Front end developers: stop moving things that I’m about to click on

#129

Post by layer8 »

pull_my_finger wrote: post #42

Honestly, 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.

Still delay-inserted content like the Wikipedia donation banners are a regular occurrence.

Re: Front end developers: stop moving things that I’m about to click on

#130

Post by InCityDreams »

graycat wrote: post #54

I agree and don't like Web pages that are complicated, require time, clicks, and effort to learn to use, have page content jumping around, cover the page with images requiring the user to stop what they are trying to do, change the window size and magnification, find a way to get rid of the image and do so, return the window size and screen magnification to what they were, and get back to the reason they came to the…

You're doing everything right regarding cookies, but have somehow managed to either not understand how the EU would regard your non-use of them, or your site does not exist.
Post reply on HN