Unable to reproduce the issue on Win 7 using latest stable 51.0.2704.103.
Could you please review the attached screen cast and let us know further if any.

missed the attachment in previous comment.

Deleted: 621928_June_22.mp4 29.1 MB

621928_June_22.mp4 29.1 MB Download

This certainly sounds like a composting issue.

Hello, apologies for the delay. 

Attached to this comment is a video of me producing the bug, it is very easy to replicate as shown in the video. This works on pretty much every page i've visited, using Amazon and Wikipedia as examples in the video.

I'm on the most recent version of chrome, and using Windows 10. Please let me know if you need any additional information, thank you.

James

Deleted: Bug video.mp4 9.0 MB

	Bug video.mp4 9.0 MB View Download

Thank you for providing more feedback. Adding requester "durga.behera@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

Doesn't seem to repro on 52 on windows or mac, but can indeed see it on linux stable (51.0.2704.106). I think we need a bisect.

Unable to reproduce the issue on Win 7,Win 10 and Mac 10.11.5 using stable 51.0.2704.106,beta 52.0.2743.49 and canary 53.0.2784.1.

Though as said in comment #7, able to reproduce it on Ubuntu 14.04 on stable 51.0.2704.106, but not on beta and M53 latest.
Its regressed in M52.

Reverse Bisect info:
====================
Bad :52.0.2724.0
Good:52.0.2725.0

Change Log:
===========
https://chromium.googlesource.com/chromium/src/+log/9c711851334428d698079b73f17d1bb0620960b8..f086d731245c5a5c300a98fbfb3e410fbf3e6220

possible suspect : https://codereview.chromium.org/1950613004
skobes@ : Could you please take a look into this if its related to your change which might have fixed this issue.

Added Release block-Stable against M52, please modify if not appropriate.

I'm unable to reproduce this issue.  It's possible it was fixed by https://codereview.chromium.org/1950613004, though I don't understand exactly how.

Note that this change is in M52 already, so if it is the fix this is not ReleaseBlock-Stable (but we should possibly merge it into 51).

@vollick, if you've repro'ed on Linux stable can you verify that it's fixed by r391652?

M52 Stable is launching very soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged ASAP. All changes MUST be merged into the release branch by 5pm on July 8th (in case if you missed today's 5:00 PM PST deadline) to make into the desktop Stable final build cut. Thank you!

Removing the RB-Stable label as per #7 & #9 since this is not seen on any latest M52 builds.

Please feel free to add it if needed. 

Yes, I've verified locally that it seems to have been fixed by https://codereview.chromium.org/1950613004 / r391652. Should we merge this back into M51?

Hi guys, sorry to be the bearer of bad news, but the issue is still here. I have updated my chrome to the latest version and retried this bug and it still works (Unless you are talking about a version of chrome that is soon to come, in which case, ignore me)

Thanks,

J

Thanks @flackr, requesting merge to M51.

@streety.j.97, we believe this to be fixed in Chrome 52.  If you are on the stable channel the "latest version" is still 51 which would explain why you still see it.  If you like you can try the beta or dev channel (https://www.chromium.org/getting-involved/dev-channel) and verify that it is fixed there.

[Automated comment] Request affecting a post-stable build (M51), manual review required.

Hello all, I have downloaded the dev channel of the latest chrome and can confirm my issue has been fixed 

c#9, do we now understand why this change fixes this issue, and are sure this this is the change that has fixed it (sounds like it from c#12, but want to make sure)? Also, how risky is this change to a post-stable branch?

The change I believe is low risk.

Based on #12 and #16, I have high confidence that the issue is fixed by this change, but I don't understand why or how the issue occurred.

 Issue 615714  has been merged into this issue.

Removing out of date merge-review request.