You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.
This would fire on mouse click, tap, or Enter / Space keys.
Investigation needs to be performed as to whether this actually needs to exist, or whether browsers already support it well enough inherently through the click event (though there may at least be the mobile tap delay to consider).
It may also be worth looking at Mayhem's activate event (in ui/dom/actions) for inspiration, though Mayhem uses its own event system so it might not be entirely applicable.
It appears that it was used on elements without activation behaviors, corroborating the above point.
I would think we should be able to get by without needing this simulated event at all, if all cases where it would be necessary can be rendered as elements with activation triggers/behaviors (e.g. a, button... unfortunately I haven't found an exhaustive list anywhere).
Rather than leave this hanging on hold for potentially a long time, I'm going to go ahead and close this, but we can easily search for a11yclick in issues again to resurrect it if need be.
This would fire on mouse click, tap, or Enter / Space keys.
Investigation needs to be performed as to whether this actually needs to exist, or whether browsers already support it well enough inherently through the click event (though there may at least be the mobile tap delay to consider).
It may also be worth looking at Mayhem's activate event (in
ui/dom/actions
) for inspiration, though Mayhem uses its own event system so it might not be entirely applicable.dom Proposal Reference
The text was updated successfully, but these errors were encountered: