For some types of data detector links we choose not to perform the default action. Therefore we don't generate a synthetic click on tap. There are to code paths that lead to calling handleSyntheticClick that need to be guarded with this logic. Only one was covered in r195769. rdar://problem/25146483
Created attachment 274152 [details] Patch
Comment on attachment 274152 [details] Patch Is this testable?
(In reply to comment #2) > Comment on attachment 274152 [details] > Patch > > Is this testable? I wouldn't know how. The two code paths are triggered depending on the duration of the tap vs touch.
Committed revision 198245.