Tooltips need a delay, and then they need to skip it

Posted by ibobev 13 hours ago

Tooltips need a delay, and then they need to skip it(blog.master.dev)

137 points | 36 commentspage 2

zx8080 4 hours ago|

Is this post text claude-generated? Very creepy to read around the solution section. It reads like the agent report.

halostatue 12 hours ago||

The pure CSS version seems more interesting to me: https://blog.master.dev/delayed-then-instant-tooltips-with-h...

cush 2 hours ago||

I was disappointed to see the new web popover api doesn't have this basic usability feature built in

self_awareness 9 hours ago||

Hilarious. Web devs discovering UX from Win95. What's next, 3d buttons?

tgv 1 hour ago||

MacOS had it even earlier. I think it's because there's not a mature UI framework out there. They come, have their moment in the spotlight, and are replaced. There's also a ton of them. And they are often written by a very small group of people without deeper understanding of ergonomics, and don't live long enough to get this level of attention. You should be glad if it still gets bug fixes after 2 years.

ProxCoques 8 hours ago||

I know right? It's like interaction design came and went over a period of 30 years and now we're back to the beginning again.

quacked 6 hours ago||

I spend a lot of time seething at how poorly modern software interaction is, and I've come to the belief that they basically solved most of the window-based GUI computing interactivity problems by around XP, and have just been gutting them since then.

My three most-hated modern trends

- Disappearing scroll bar with content that you have to scroll for

- Pills going across the top of the screen that are "most-used" filters instead of a real filtering menu

- Clickable text and non-clickable text appearing the same. I mean come on. Who the fuck is designing these things? That's the one I can't wrap my mind around. How can a self-respecting programmer put out a UI where the display and clickable elements look exactly the same? What are we doing man

nxc18 6 hours ago||

I think the real problem is we don’t have a native-quality UX toolkit on the web - the built in controls are just horrible. So every app has to reinvent the wheel from scratch, or use one of a few hundred (thousand) web component libraries that have all also had to reinvent the wheel from scratch (I guess a div and some text rendering isn’t scratch per se but you get my point)

thaumasiotes 4 hours ago||

Well, Microsoft was interested in making it easy to develop Windows applications, and also in making it easy and pleasant to use Windows applications. They had reason to invest in learning how that could be done and in writing utilities that would let you benefit from their knowledge; doing that made more money for them.

Browsers are different. They don't really benefit from being written for, or from being used. This seems like enough to explain the difference. They provide some functionality, and giving your users a good experience is your problem, not theirs.

I feel like I've seen complaints that Apple has forgotten things it already knew about how to design a usable interface; that wouldn't be explained by this model.

jay_kyburz 10 hours ago||

Perhaps I'm just an old grump, but I prefer the No Delay version in the example.

I like predictable, consistent, and fast.

broken-kebab 6 hours ago||

Same. To me exactly delayed version is annoying. Non-obvious rules which guide behavior make it feel like there's a bug.

denislexic 4 hours ago||

[dead]

jobuildsstuff 4 hours ago|

[flagged]