Do you have any extensions, in particular, adblockers, privacy extensions, or other content blocking extensions? If so, does it work properly with all extensions disabled?

No extensions at all. Also, I just tried it on a different machine, a Windows 8.1, again no extensions and the issue is still present.

I've experienced it on a few websites and I assumed there was something wrong with my mouse but there isn't, it's Chrome

Does Chrome's developer tools console report any errors? If so, can you copy and paste the error messages here?

Where would I see any errors? I opened Developer tools but I don't see an Errors section (sorry, I'm quite new to all of this)

To check for errors:

1. Press Ctrl+Shift+I to open Chrome developer tools.
2. Click the "Console" tab at the top.
3. Check for any red or yellow error warnings/alerts.

There is a yellow warning, it says:
A Parser-blocking, cross-origin script, http://cdn.listrakbi.com/scripts/script.js?m=UT8Un6tp8Rte&v=1, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.

Also, I just tried it on a Windows 7 machine and it works fine. Maybe this is an issue with Chrome on Windows 8.1/10?

>A Parser-blocking, cross-origin script, http://cdn.listrakbi.com/scripts/script.js?m=UT8Un6tp8Rte&v=1, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.


Does your device have poor network connectivity? Given that it's issuing this kind of warning it's probably expected behavior. Do you happen to be the administrator or webmaster of this site?

The device doesn't have poor connectivity. The Windows 7 machine is right beside it, both on the same wifi network, and don't forget, Edge and Firefox do not have this problem. 

Did a quick check:
 1. The document.write warning is not relevant: the script is not blocked unless the warning is followed by a ERR Cache miss (I can also confirm that the website still works with the intervention enabled / having said script blocked).
 2. I was able to reproduce on Chrome 52 and 55 (Windows) but not on Chrome 54/55 (Mac, Windows).

Removing Shivani since this is very unlikely related to the doc.write intervention.
+needs-bisect (assuming a regression).

rnimmagadda@, could you help us?

Test case: http://www.lush.ca/
steps: 
 0. start a bisect on a Windows machine (could not repro on Mac)
 1. open the URL above
 2. click on one of the headings (e.g. Bath, Hair...)
 3. a navigation should occur


Thanks in advance!

====================================

Good Build:

47.0.2502.0    Base Position: 347539


Bad Build:

48.0.2527.0    Base Position: 352270

=====================================

Able to repro this issue only on Windows 10 for the Google Chrome Stable Version - 53.0.2785.89

This is a regression issue broken in M48, below mentioned is the bisect info:

CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/8f96adc65258bf999417cefb8c5aead6a8ed0876..bfe839f75f182861d8322a861b4e7ed584be4f3a

Suspecting Commit: eb2728fc03dead670668dbeb071e8584e2a0504b

Review URL: https://codereview.chromium.org/1360233007

@yukishiino: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner.

Thank you.

The issue doesn't reproduce on my env.  I've tested on the following environments.

Windows 10
Chrome 55.0.2852.0 canary (64-bit)
Chrome 53.0.2785.89 m (64-bit)

Windows 7
Chrome 52.0.2743.116 m
Chrome 55.0.2852.0 canary (64-bit)

Can someone still reproduce the issue?

Also are there similar web pages that repdocues the same issue?  Since our implementation of onclick, etc. hardly depends on a platform, it could be a site issue.

I can reproduce the issue (Windows 10, Google Chrome	53.0.2785.89 (Official Build) m (64-bit), incognito) and spent some time trying to understand what's going on.

There are several click events handler that do a ton of processing when clicking on these categories (well anything for that matter).

Given that the issue goes away when one removes the click event listener from http://cdn.heapanalytics.com/js/heap-347315313.js, I'm guessing that this is an issue (i.e. rely on a behavior that is no longer true) in that code rather than a regression in Chrome.

I managed to find another website that had this issue (assuming it is the same issue). It was grocerygareway.com , but the problem is, they have since completely revamped their website. The issue was pretty serious on that site because when you would click the "Buy" button next to grocery items, it would not add them to the cart. It's definitely a regression because i used to use grocerygateway in Chrome last year and did not experience this problem. Is it possible there is a cache of the previous version of grocerygateway.com? Either from goog

Google or waybackmachine? (Sorry for the double post)

Gosh, sorry for the triple post, new keyboard. The website was grocerygateway, I apologize for the typo