Update Chrome beta to 51.0.2704.77, problem still there.
Deleted cache, problem still there.
Deleted data, problem solved.

Thanks for the report. Can you please provide more details for further triaging?
1. Device Model and OS version
2. Video and bug report( if possible)

1. Samsung S6 Edge+ with MM 6.0. 1
2. Link to video was already provided in OT

Thank you for providing more feedback. Adding requester "rsgavara@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Issue is not reproducible on latest Chrome 51.0.2704.81 / S6 Edge+ (6.0.1).Also changed Device language to italiano and checked as per screen record shown but not reproducible.
Hence closing as wont-fix.
Can you please try with latest Chrome 51.0.2704.81.

I have further information.

Both latest chrome stable 51.0.2704.81 and beta 52.0.2743.62 are installed on Samsung Galaxy edge+ and Samsung Galaxy tab s2, both with latest android MM 6.0.1

On Edge+ the links from touch to search are opened correctly for both stable and beta.

On Tab S2 the links from touch to search are NOT opened for both stable and beta.

I have restarted Tab S2 in safe mode and tested with chrome stable, to no avail: this proves that it's not due to any third party app installed.

I have tried clearing chrome cache and data, to no avail.
I have tried clearing cache partition from recovery, to no avail.

May I have a feedback please?
This is driving me crazy...
I cannot see any pattern in any test I have made, but for sure there must be "something" preventing the opening of the links from the touch to search results.

Ok this is getting ridiculous. 

On Tab s2, where hyperlinks are not working for stable and beta, I have installed development and the latter was working. Then I removed beta and development,  tried with stable and it was not working. I reinstalled development and... IT WAS NOT WORKING ANYMORE!!!

On Edge+ all three stable, beta and dev keep on working, although in the past beta was not working and it started working again after clearing data (solution that is not working on tab S2).

Is there someone with a damn solution or at least with the decency to give me a fucking answer?

I'll take this -- clicking on a link in the Overlay should always take that link.  Evidently there's still a problem on some devices.

giovanni.stoto@, sorry for the lack of response -- I've been on vacation for a week and will be on vacation again during the week of 7/18.  I'm sorry this has been frustrating for you, but please keep all interaction professional, profanity is not allowed and likely to just make the problems worse or lead to being banned.  Feel free to send mail directly to me at donnd@chromium.org if you'd like any clarification on this meta-issue of being able to get timely updates on bugs.  We appreciate the bug report and help isolating this issue.

You are right, I do feel sorry, but anger has prevailed  (it shouldn't have) also because in the Google Chrome book all I'm getting are the usual answers (clear cache, try development. Ecc.).

So I apologize,  but I was just trying get to get at least a little attention.

Anyhow, I am a computer science engineer so I do know what it takes to debug an issue that does not have a pattern. That's why I'm trying to give some many feedback as possible after my tests. Of course both edge+ and S2 are not rooted (not that I don't know how to do it...) so I breve it'll be difficult to send you logs.

If necessary, I can run further tests, maybe in a more organized way, so please let me know why I can do.

All I can tell, at the moment, is that on edge+ links are working with stable/beta/devo,  while on S2 none is working including get stable in safe mode.

And gain, sorry for having lost my temper

Sailaja, do you have a Tab S2 we can borrow to try to repro?

Consider that, out of irony, when I had only the edge+ links where not working, then I tried clearing data (not only cache) and it started working again. 2 weeks ago I bought an S2 (the latest model, with Qualcomm and 6.0.1) and links are not working, whatever I do. I managed to have dev working, so to try a test I removed both beta and dev to try stable to no avail, so I reinstalled development and this stopped working again. 

giovanni.stoto@ Here's a quick test that might give us some useful info: after tapping on a link that does not navigate, tap on the bar to promote to a separate tab.  Does the separate tab show the same search results as the overlay?  I think there's a small chance it will actually show the contents from the link chosen instead.  If it does, you have a workaround that might be helpful, and let us know!

Nope, it opens the same search results in a new tab.
But some links are working: YouTube and Google play.
Links to Google maps also open up but not in a new tab but in the same overlay.

Matt, any idea why a tap on a result link wouldn't get handled?  I'm guessing it's getting filtered by the OverlayPanelEventFilter somewhere near the "wasEventCanceled = true;" in this code: https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/compositor/layouts/eventfilter/OverlayPanelEventFilter.java?q=onTouchSearchContentViewAck&sq=package:chromium&dr=C&l=394
But it looks like the event will be passed on regardless, as long as there's a containerView.  Any ideas off the top of your head?

Giovanni, are you sure the navigation never takes place?  Maybe when you tap on a result, if you wait a few seconds it will eventually load in the overlay panel?  BTW, it would be nice to know the use-case that you have where it's important for you to be able to click through result items from the search.

I'm sure: I click on a search result in the overlay, the heading blinks in blue and nothing happens.

You wanna know something funny? I have installed a screen recording app on the edge+ and when I started recording with chrome beta I realized that links stopped working!!! Tried with stable and it works. I'm sure it cannot be the app as I have also uninstalled it and beta still doesn't work while stable works.

Will try to post to my public Dropbox a video.

https://www.dropbox.com/s/yzuhdhv4gz89pkh/2016_07_12_08_25_13.mp4?dl=0

Here's the link to the video.
I first open beta, click on 3 links and nothing happens and then I cick on the top bar and a new tab is opened with search results. Then I open stable where all is working.

BTW, I'm not alone 😉

https://m.reddit.com/r/chrome/comments/3evuz8/hyperlinks_dont_work_in_touch_to_search_results/

Unfortunately no. There is a similar problem in Reader Mode where links are not navigated to. From what I could tell the InterceptNavigationDelegate was being ignored or replaced (see  https://crbug.com/601811 ).

sgurun@, do you happen to know of bugs in InterceptNavigationDelegate that might account for this (see #21)?

Dear all,  all of a sudden the problem is now showing also on edge+ with both beta and stable

unfortunately I do not know, sorry.

Edge+
Installed ne beta 52.0.2743.83
At first still not working 
Cleared cache and still not working
Cleared data and now working

Will report soon on Tab S2

Tab S2
Installed beta 52.0.2743.83
Cleared data and NOT WORKING

Ok this is getting ridiculous: haven't installed anything new on my edge+ and haven't done anything different than usual, yet today links have stopped working again (after that yesterday I managed to have them working by clearing chrome data (.

Giovani, I cannot repro.  Can you summarize when this is happening for you and when the problem goes away to try to help guide us to how to repro?  Has anyone else seen this?  

The pro lemon is that there's no pattern and the issue is inconsistent between the s6 edge+ and the tab s2

For example yesterday I decided to go back using Chrome stable, Web view stable and Google Apps stable. In particular I decided to go back to Google Apps stable as the last two betas were giving me problems to how reminders are displayed in calendar and widget (BTW,  how canice I report this to the development team?).

So I unsibscribed from all beta version,  reset the phone and the tablet and started using stable versions.

Now the TTS hyperlinks are wo4king on the phone but not on the tablet, which is strange as the tablet is just as brand new.

I wish there was a way to logcat what happen when I click the link and nothing is opened.

And besides the rom (both latest marshmallow 6.0.1 rooms though) the two devices are set exactly in the same way: same apps, same settings 

OK guys, bad news...
I have replaced my Samsung Galaxy S6 Edge+ with a Nexus6p fully stock, not rooted, not modified, clean as Google made it. Using latest stable version of Chrome 51.0.2704.81

At the beginning the hyperlinks were working but one day all of a sudden they stopped working. And of course I have no idea why. That's to say it's not only a Samsung issue.

Any news?

No news -- as far as I know nobody here can repro.

Please remind me why this is an important usage pattern for you?  We think most users are looking for an answer in the search results in the form of a one-box or other information that does not require a click-through.  I'm inferring from your interest in this problem that there's an important use-case for you, and I'm curious to know what it is! Of course this is clearly something that needs to be fixed regardless, but if we're blocking some important use case for people like you that will help raise the priority of this issue.

Well it's a Google Chrome feature and it's very useful: you are browsing and find say a word you wanna search, you don't need to open a new tab, you select the word, get the overlay with the search results and click on the one you wanna read.

As long as this was happening on Samsung devices only I was less worried, but now it happens also on my brand new nexus 6p, fully stock no root.

Thanks for the details!

I wonder why none of the testers or developers are seeing this, and if there's some pattern to your usage that we happen to avoid, e.g. signing in to your account, clearing data, etc.  Thanks for ruling out Samsung-only since it happened on your 6p.  I suspect the difference is that we tend to not click-through often.  Clearly there's something very flaky with that click-through logic, but it will be hard to find without a way to repro.

Well, I've had my 6p for one week only and I tested this only after a couple of days of normal use. I'll try to run a test tomorrow in safe mode, but without root I cannot even read the log cats, so cannot help further.

I had to totally reset my Nexus and now it's working. Nexus is also rooted not, so if problem appears again I'll be able to send you a logcat

> Has tts been removed from latest chrome version?
Note that we're doing some experiments with tap suppression so you may need to tap more than once to get TTS to respond when you have not opened the panel recently.

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]