Keyboard trigger not working in web if assets hidden
BUG:
To allow convenient keyboard triggers over entire prototype it is necessary to add hidden buttons/elements on each artboard. Every button is allowed to have only one trigger (feature request already exists for this problem).
Keyboard keys (windows) working fine if in preview mode.
BUT if sharing on web they don´t work anymore IF the "buttons" are set to invissible.
Workaround: move VISSIBLE buttons with trigger to lowest layer so that they can be hidden behind something in front.
EssZett
shared this idea
Thanks for reporting this! I’ve escalated to the product manager, and we do have a bug filed about it. Since this is a bug, this should be reported in the new Community Forums, not in UserVoice: https://community.adobe.com/t5/Adobe-XD/bd-p/xd
-
Stefan Dickerson
commented
Here's some more related bugginess about this. Even with the workaround I still can't get this working reliably.
Even though we shouldn't have to, I'm creating 4 hidden objects, each mapped to a different key trigger. (Doesn't this workaround open up potential conflicts, like what if I try to map two different paths on two different objects to the key "X"?)
I'm putting this in an overlay. In my prototype there's a text field you click on, the overlay comes in and shows the in-focus text field with a cursor in it. I've mapped the keys 1, 2, 3, 4 to different objects I intended to hide behind the text field, with the intent to go to 4 different places..
It works perfectly a few times, then it just doesn't. Sometimes. Seems to fail (sometimes) if I've switched browser tabs and back again, or if I simply wait too long to interact with it.
Anyway, this key feature would be great, it works perfectly in Preview, but on the web it's not quite there and my researcher can't use it.
-
EssZett
commented
thanks, it was not clear to me where to post bugs.
You said you "filed the bug". But I can´t find it in community.
Will this "feature request" here then be closed? Or why set to "action required"