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
After #888 a11y listeners can be added just like any other input listener. We have been doing this already in PressListener.
PressListener is part of a "new" set of Scenery input listeners. FireListener is part of the "new" set and is very similar to ButtonListener in its feature set. It may end up replacing ButtonListener in the future. So I was wondering if we should skip ButtonListener and proceed with FireListener instead. But we are currently in a transition phase as the "new" set of listeners are finalized. Over Slack, it was reported that ButtonListener should not yet be marked deprecated because FireListener may not be complete. So we expect the transition will take some time. For this reason, we should instrument ButtonListener now.
It looks like there is some very old (pre-PDOM) a11y code in ButtonListener already, we should start there.
The text was updated successfully, but these errors were encountered:
This was done, ButtonListener now responds to the click event, and activates the button in response.
It looks like there is some very old (pre-PDOM) a11y code in ButtonListener already, we should start there.
This has been removed. Old code that used to check the Pointer for an isKey flag was replaced by clickfocus and blur listeners to update the buttonListener overCount.
I added a TODO to mention that we will likely come back to this once #939 is sorted. At that point, we probably won't respond to click events, and instead respond to keyup and keydown events instead. This is true for all of our current listeners. Closing.
Motivated by phetsims/sun#487.
After #888 a11y listeners can be added just like any other input listener. We have been doing this already in PressListener.
PressListener is part of a "new" set of Scenery input listeners. FireListener is part of the "new" set and is very similar to ButtonListener in its feature set. It may end up replacing ButtonListener in the future. So I was wondering if we should skip ButtonListener and proceed with FireListener instead. But we are currently in a transition phase as the "new" set of listeners are finalized. Over Slack, it was reported that ButtonListener should not yet be marked deprecated because FireListener may not be complete. So we expect the transition will take some time. For this reason, we should instrument ButtonListener now.
It looks like there is some very old (pre-PDOM) a11y code in ButtonListener already, we should start there.
The text was updated successfully, but these errors were encountered: