Default browser issue

[apel69]

I am having a hard solving an issue with the default browser. I have one website (NBC News) where none of the links function when pressed. They highlight yellow but no new page opens. If worked before and for some time after I rooted my phone. I have cleared the cache and data, restored it from a known good Titanium backup, and restored it again after removing it with Titanium backup. The only time it has started working was when I had the cell store flash 4.1.2 on it. Here again it worked before and after I rooted. I incrementally installed apps and used it for a while to see if another app was causing it. Out of the blue it stopped working again. I don't want to switch to another browser besides the same issue occurs with Chrome and Dolphin although it works with Firefox and Opera.

Galaxy S3 running 4.1.2 rooted stock ROM.

 

[GSDer]

Not exactly sure what to tell you - assuming that this is the site that you're referring to then my experience is the same as yours: if I tap one of the story blurbs, it briefly highlights and then unhighlights. Note however that if I long-press on one of the story blurbs, I get this and if I choose Open then it opens the story like you would have expected. Annoying, but it's a work around. Of course, you could change the browser to Desktop view but that rather defeats the purpose.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk 2

 

[meyerweb#CB]

The same thing happens in Chrome, but the links work as expected with Firefox (on my device). I have Adobe Flash installed, which Firefox makes use of, and the stock browser doesn't. I don't know if that explains it, nor do I know why NBC would use Flash for simple links, but it appears to be an issue with the site, and not with the browser.

 

[apel69]

The longpress then open works. It's a bit of a nuisance but better than nothing and it's just the one url. It's just odd that it used to work and then took a factory ROM reset to fix it for awhile.

I reinstalled Chrome and it behaves the same as the default browser. It's even more odd that this occurs across multiple browsers. Makes me think it is something deeper in the system or maybe it could be something as simple as a checkbox somewhere. Wouldn't be the first time.

I tested it out on my old Galaxy S with the default browser and everything functions fine.