81–90 of 92 posts
It will never cease to amaze to me that Apple (under Jef Raskin who also wrote about this in The Humane Interface) observed and fixed problems with interactions like this in SYSTEM 6 in like 1993 or something - only for the same problem to have to be re-descovered and re-fixed decades later.
How do you think tooltip hover works on mobile?
Why do we need to explain what a thing is or does on every site? Are JavaScript devs seeing video games and the key takeaway is everybody loves the tutorial where they’re told W moves forward? Or are they doing wacky JavaScript devs stuff like making pageup forward because it contains word “up” so fixed another bug. Then patting themselves on the back.
Just display the text information. Let me print it. Use consistent designs. Don’t intercept my clicks.
I could do an hour long standup rant just about how you guys need to STOP intercepting my clicks. In fact I’ll narrow it down to just Microsoft. They continuously find new ways to block and obstruct clicks. Once windows toast notifications got mostly fixed they reinvented toast notifications in yet another parallel duplicate feature with Teams toasts that spawn back to back to block critical button clicks.
I can’t believe even Apple has let this slip and iPhone is also subject to click blocking.
What are the rest of you devs doing all day?
I wrote an chrome extension to block them: https://chromewebstore.google.com/detail/google-workspace-ho...
It will never cease to amaze to me that Apple (under Jef Raskin who also wrote about this in The Humane Interface) observed and fixed problems with interactions like this in SYSTEM 6 in like 1993 or something - only for the same problem to have to be re-descovered and re-fixed decades later.
Chesterton's Fence. Why on earth do we need this thing here? Oh, that's why.
“Do not remove a fence until you know why it was put up in the first place.”
It will never cease to amaze to me that Apple (under Jef Raskin who also wrote about this in The Humane Interface) observed and fixed problems with interactions like this in SYSTEM 6 in like 1993 or something - only for the same problem to have to be re-descovered and re-fixed decades later.
Earlier quoted context omitted.
Chesterton's Fence. Why on earth do we need this thing here? Oh, that's why.
Rewrite will be better /s
It's a great gig if you can get it. Horrible for the users and investors, of course, but great for the engineers.
I ran into the same problem about 20 years ago when implementing hover-based dropdown menus on a website. It was only about 10 lines of JS and a couple global variables but I was the only person who understood it. :-P (These days I would have included more comments.) Naturally, there was a fallback to pure CSS menus, because we weren't barbarians.
> only about 10 lines of JS Ah, the good old days when we wrote JS function to do something, or copied from dHTMLZone. These days the first 10 lines of JS is loading hundreds of lines of JS libraries. (Yep, I'm an old man yelling at clouds!)