Fix hover logic on touchables #104
Loading…
Reference in New Issue
No description provided.
Delete Branch "esavkin/web2019:84-touch-ux-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #84
What do each of these "fixes" consist in exactly?
As I said before dragging the card out of the crate to remove it is fine behavior IMO. What did you replace it with?
No replace, just buttons and warnings are now showing when clicked (on touch devices only), in similar way when hovered
Click is far easier and more accessible than drag. Also deleting by drag is hard to discover, and not really common way of doing this, meaning users will get stuck for a while, is not a good UX. In most cases (iOS, OneUI, AOSP launchers, Telegram Stories) I see there is at least an alternative way, in some cases it is not even an option (Microsoft ToDo, TaoBao). The only one I could find that forces to drag-only is Instagram stories.
No reason not to show a same button as on hover but on click so far.
What about the other questions?
34572c4ec6
toa5b217c183
OverlayTrigger
, which can be triggered by both hover and tap, and can be closed by tapping outside and inside or leaving a mouse.OverlayTrigger
is used in cards options anyway, and working better than in-house solution - it knows where the screen ends and repositions itself when needed, so the content is fully visible. The overlay itself is basically the same except position.