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
When cancelSyntheticClickEvents is true in lib/utils/settings.js (default), click events initiated by mobile screen readers (VoiceOver or Talkback) are immediately killed by function _handleNative in lib/utils/gestures.js. This obviously affects any element using that module, but also seems to affect every other element on the page (i.e. even non-polymer elements), because the event listeners are injected globally ob the base html element and handle events before any other function.
Description
When
cancelSyntheticClickEvents
is true inlib/utils/settings.js
(default), click events initiated by mobile screen readers (VoiceOver or Talkback) are immediately killed by function_handleNative
inlib/utils/gestures.js
. This obviously affects any element using that module, but also seems to affect every other element on the page (i.e. even non-polymer elements), because the event listeners are injected globally ob the basehtml
element and handle events before any other function.The latter point means this bug can render nearly an entire application inaccessible even when most components do not use Polymer. See home-assistant/frontend#8178 and home-assistant/frontend#10617.
Please excuse that I cannot verify the breakage with Talkback as I do not currently have a device readily available.
Live Demo
iron-overlay-behavior demo on webcomponents.org
Steps to Reproduce
Expected Results
Buttons should work equivalent to when VoiceOver is off
Actual Results
Nothing happens for either button
Browsers Affected
Versions
The text was updated successfully, but these errors were encountered: