Fun read: https://sorenblank.com/craft/the-invisible-shape
#TIL one of them is even patented by Amazon 😲
Fun read: https://sorenblank.com/craft/the-invisible-shape
#TIL one of them is even patented by Amazon 😲
@cheeaun I didn't know so much thoughts were put into this.
@cheeaun huh, interesting
i started wondering how my #linux desktop handles that problem, and it seems like:
#GTK apps with traditional menus seem to do a variation of the "safe triangle" scheme, where they will delay closing or switching to a different sub-menu if your mouse position close enough to the sub-menu
so does #libreoffice
#firefox, despite using GTK-style looks, uses a timeout-based scheme, which, IIRC, is also used by ms windows
apps that use #libadwaita and are designed specifically for GNOME do not have pop-up submenus at all, instead you have to click on an item to go into a sub-menu (and most have shallow enough menus that it is not a problem in the first place)
#Qt apps also use a timeout, but a more lenient one than firefox
@cheeaun "...and one suggestion there is to let browsers handle the hover delay and the safe triangle themselves. If that happens, none of us will have to write this ever again." Yes, please!
> Just with math instead of an SVG, seven years earlier.
This sentence feels so wrong. Like, wdyt vector graphics code does? It's not math vs. SVG but "a precise formula invented exactly for this purpose" vs. "abusing a math engine invented for graphics and doing bounds checks" ^^'
But this also explains why I had such big problems using context menus on macOS. I've had to use macOS on $previous_job for 3 years and context menus always gave me trouble. The interactive demo demonstrates this really well. Curved, Safe Triangle and Amazon's approach all work fine for me, but I move my cursor too slow or whatever for Apple. Soooo annoying, I really hope that if browsers adopt some of this, they won't choose their approach.
@cheeaun now I know what I'm missing when I use an app/site that has a half-ass custom menu implementation. Thanks.