We want to gauge the "searchyness" of the text tapped in order to better decide whether to trigger or not.
The first step in doing this is to gather the text surrounding the point where a Tap gesture occurs so it can be examined before doing any UX (such as selecting the word). Pedro's refactoring CL does this, so I'm thinking of importing that part of the refactoring into the mainstream code.
Once we have access to the tap-text we can use it to build a rudimentary searchyness value, probably based on the length of the word tapped and whether it's capitalized.
See go/cs-suppression for background on Tap Suppression.
CC'ing marq@ so we can try to coordinate an iOS implementation.
Comment 1 by donnd@chromium.org
, Aug 17 2016