Apple does this, a lot. The number of times I have incorrectly called somebody on FaceTime because I clicked on a contact at the same time FaceTime decided to update the list should be embarrassing for them. I have zero idea how this doesn't get fixed. It should be a trivial change to make sure the list is updated however they'd like before showing it to the user. As it is right now, given that it's slower or about as fast as me clicking something on the screen, it seems updating the list is the very last thing they do.
Front end developers: stop moving things that I’m about to click on
251–260 of 365 posts
Re: Front end developers: stop moving things that I’m about to click on
#252Earlier quoted context omitted.
I would suggest that the enormous size of today's pages have taken us back to the behavior seen in the dial-up days. Then: Page was slow because the delivery was via a 56k analog modem. Today: Page is slow because the average page size is 2.2mb. Plus JavaScript parsing + execution time. Plus asynchronous calls to go load more stuff. Plus time to re-layout around the new stuff.
> Page is slow because the average page size is 2.2mb. Plus JavaScript parsing + execution time. Plus asynchronous calls to go load more stuff. Plus time to re-layout around the new stuff. I think it's mostly blocking chains of multiple networks requests that execute in sequence (taking a network round-trip each time). I inherited a slow ~2mb frontend app at work, which seemed horrendously bloated to me. It turned ou…
Unless your website is some kind of game or application why the hell does it have 2 megs of JS? Remove your shitty tracking and ad code.
Re: Front end developers: stop moving things that I’m about to click on
#253Re: Front end developers: stop moving things that I’m about to click on
#254Anyone else try peeping the chat in Zoom?
Also: someone sends you a direct message, you reply, but you send the message to everyone :).
Re: Front end developers: stop moving things that I’m about to click on
#255Earlier quoted context omitted.
This - "Cumulative Layout Shift" - is part of Google's Core Web Vitals - https://support.google.com/webmasters/answer/9205520?hl=en - so if people are doing that, they're going to be penalised by Google. (Although probably only a bit, given the number of other factors that go into search rankings).
Meuh - google does this with youtube. Load video: video centered. Oh there's a side bar, let's shift the video. Oh the contents needs a smaller dimension, let's shift again. Rather annoying if you're used to watching videos at more than default speed - the control for that shifts 2-3 times.
Google is so huge that, as we say in the UK, it doesn't know its arse from its elbow - the teams are so disparate that it would be difficult to coordinate. Besides which, the "other factors" that I mention heavily favour a site like YouTube, such as the enormous number of inbound links, to a point where they can ignore the inconvenient bits of Core Web Vitals.
Re: Front end developers: stop moving things that I’m about to click on
#256Earlier quoted context omitted.
Relatedly, many websites have nowhere to tap that doesn't do anything. If you try to select some text then want to tap away (to clear the copy/select all/etc popup) you can't do so without navigating away from the page or causing something else unwanted to happen. This gets doubly frustrating when navigational elements don't contain actual anchor links. If you long-tap on mobile to open in a new tab, the browser deci…
The Reddit redesign is a classic example of this. Click or tap somewhere accidentally and you'll probably cause something annoying to happen. The most obvious is around the modal thread view.
Atlassian Jira is a good example of that too. It is safer to click on a minefield than a Jira page.
Re: Front end developers: stop moving things that I’m about to click on
#257This isn't even just affecting the web. In the macOS Ventura in Safari they added a new option in the context menu when "right" clicking on an image, something like "Copy subject" or whatever that means. The problem is that that option isn't there from the beginning, but it pops up 1-2 seconds after, as if they are doing some processing on the image. Now if you are in a shop for example with a list of products, or an article or whatever, anywhere where an image is linked to something else and try to open the context menu for opening in a new tab (yeah I do that more often than using the CMD click), if the image is towards the bottom and the context menu doesn't have enough room at the bottom and is rendered a bit higher than your click so that it fits in your viewport, you wait 1-2 seconds and Apple adds right at the end of the context menu another option that just moves all other options one slot higher, making you always click for example Open in new window instead of a new tab or whatever option was right under your intended click, as everything in the context gets shifted. I don't know how Apple didn't see this and I don't know who thought that adding another entry in the context menu after it's rendered initially is a good idea.
Re: Front end developers: stop moving things that I’m about to click on
#258just in case someone from Amazon owned Twitch.tv reads this in the future
First issue is that it shows the controls for the video, and allows you to click on them and shows you them as clicked or changed, but when the video loads it resets them.
So if you want to reduce VOLUME or mute things before video loaded. Give it a try, looks like it works, nope, too bad, it's reset. Same with the PAUSE button. Nope, it will fool you into thinking you have paused it but it will actually autoplay the video. Basic essential functionality in a video player rendered useless.
Secondly is the Setting menu to reduce / change quality or speed up the video. Here menu items load in after the menu is first open, even after the video has loaded. So you go to change something useful but nope you accidentally click the report button or something. You literally have to open the menu, wait a couple of seconds and then you can click on the option you want.
Now there was a similar issue with stuff not loaded, underneath the video player, where the user would click something near the follow/unfollow but they would accidentally unfollow the user. Now they added a confirm dialog, so at least that's an improvement.
Re: Front end developers: stop moving things that I’m about to click on
#259This is a problem for people who are very proficient when using the internet, "computer experts", and not for many others. However, this has been a problem in Google search results for a while now (and you know what I mean, I don't even have to say it), I figured they have would fixed it by now... I have even made a custom Chrome Extension that kills these annoying ads and shifty DIV's. It would be nice to see a big…
> This is a problem for people who are very proficient when using the internet, "computer experts", and not for many others.
I'd disagree. My mum is 83 and has complained about this in apps on her phone and when using websites.
Re: Front end developers: stop moving things that I’m about to click on
#260Earlier quoted context omitted.
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.
+1000. I forget which search -- it's probably macOS Spotlight -- drives me batty with this daily. Firefox has a related misdesign. If you type a word which matches both a search keyword and a history item, the search keyword takes precedence -- which is nonsensical, since I've typed nothing (not even a space) following the search keyword. So e.g. I have a `cpp` keyword to search `en.cppreference.com`; typing `cp`+Ent…
Spotlight 100%