Expose the check on the wrapper object so that we can handle simulating the touch on iOS.
<rdar://problem/27629346>
Created attachment 284963 [details] patch
Comment on attachment 284963 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=284963&action=review > Source/WebCore/accessibility/ios/AccessibilityObjectIOS.mm:89 > + return false; Will this also take care of the case where the listener is on a parent node?
Created attachment 284966 [details] patch update from review
Created attachment 284967 [details] patch better styling
Comment on attachment 284967 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=284967&action=review > Source/WebCore/accessibility/ios/AccessibilityObjectIOS.mm:88 > + if (node->hasEventListeners(eventNames().touchstartEvent) || node->hasEventListeners(eventNames().touchendEvent)) We may have code for this already. Can you do a search for ontouchstart and see if there's something in ax alread
Comment on attachment 284967 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=284967&action=review >> Source/WebCore/accessibility/ios/AccessibilityObjectIOS.mm:88 >> + if (node->hasEventListeners(eventNames().touchstartEvent) || node->hasEventListeners(eventNames().touchendEvent)) > > We may have code for this already. Can you do a search for ontouchstart and see if there's something in ax alread I searched ontouchstart, ontouchend, touchstart and touchend. And there's no related accessibility code.
Comment on attachment 284967 [details] patch Clearing flags on attachment: 284967 Committed r203955: <http://trac.webkit.org/changeset/203955>
All reviewed patches have been landed. Closing bug.