4 ms·
This is how it should be - mouse actions trigger on releasing the button, not when pushing it. It allows the user to correct a mistake if they accidentally pres
by TonyTrapp 6y ago
This is how it should be - mouse actions trigger on releasing the button, not when pushing it. It allows the user to correct a mistake if they accidentally pressed the button, because they can move the mouse away from the clicked object and the action will not trigger. Many modern self-cooked UI systems seem to forget about this, it's just sad.
- albertgoeswoof 6y agoRight click is different though, it shouldn't trigger an action in most cases, instead it should bring up a menu. The faster that comes up the better.
- literallycancer 6y agoSeeing as we are in a thread on Vivaldi, a spiritual successor to Opera where mouse gestures were quite important for the overall experience, I'll go with "actions on mouse down are just fine".
- TonyTrapp 6y agoBut didn't Opera gestures always end on mouse-up? That makes it even more important that a context menu only opens on mouse-up, because otherwise you would potentially both open the menu and execute an action at the same time.
- spijdar 6y agoThis is exactly why some people (including me) prefer this idiom -- right click down to make a context menu appear, nudge the mouse over a few pixels to select e.g. the back button, mouse-up and there you go.
- diroussel 6y agoOn the mac context menus show up on mouse down. This is so you can click, then drag the the menu entry you want, then release the button to select the menu entry. Overall there is only one click, not two. Some people find it faster.