Use default action verb kClick instead of kClickable
Switching flutter bridge to use the default action verb kClick rather than the boolean attribute kClickable. The boolean attribute was added specifically for Android and has unwanted side-effects including not allowing nodes marked clickable to have navigable descendants. This CL removes a previous work around that was caused by using clickable attribute. Also changing the touch exploration controller to always issue a simulated tap. Ax gestures do not always get propagated to the tap listener via the flutter bridge. This will make for a better user experience for some ui elements that require simulated taps. Bug: None Test: Local display assistant build, unittests Change-Id: I8bb9204d78ef61bb8afc727b9b6b41e2ca05390c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431557Reviewed-by:Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Randy Rossi <rmrossi@chromium.org> Cr-Commit-Position: refs/heads/master@{#811732}
Showing
Please register or sign in to comment