More default component states (on-click, on-tap, on-mousedown, visited, on-focus)
FINALLY there's a hover state on components! GREAT!
However I quickly ran into a limitation. When the user touches a button or clicks it with the mouse/trackpad, the button needs an "on tap" or "on click" state that very briefly changes a button's appearance to give the visual feedback "your click or touch was detected".
So now that you have HOVER please add ON CLICK/TAP ort whatever you want to cal it.
Basically the component state changes for a definable amount of time before the destination or next state is triggered.
While you're at it, how's about looking at some of the long-time available link states we know from the web, like visited, or on-focus (when users like to use the tab button to move from button to button)
-
Amelio Rate commented
Simple request: pls add ability to add an "active" state to a button. "Active" means when the button is pressed — the state appears only while the mouse/touchpad button is engaged, and turns off automatically as soon as the mouse/touchpad button is disengaged.
The "tap" trigger accomplishes the 1st portion of the active state's function, but the state remains even when the tap is over.
-
Anonymous commented
This is a must have. Otherwise one cannot prototype a desktop application
-
TeaTime commented
Agree with Caryn and everyone here! We need to have 2 'tap' interactions!
-
Anonymous commented
Hm, I really don't understand why we don't have an click/tap event yet ..
Anyway, please make it possible ASAP guys, hover and click events are really a minimum to present interractive wireframe... -
Marine commented
+1 we absolutely need this option to increase our design!
-
Caryn commented
Basically, you can still see the effect as an isolated element, but since it's not possible to have the same 'tap trigger to do 2 things — 1. to show both the tap state of the component and also 2. jump to another page, it's not useful for prototyping except for to be used in a UI library.
The missing pieces to achieve this is to allow the destination of a state to be another page, not just another state within the component, ideally with a time delay