Able to reproduce the issue on Win-10 using latest canary #61.0.3135.4.
Issue is not seen in OS-Mac.

Thanks...!!

Bisect Information:
--------------------
Using per revision bisect providing information below.

You are probably looking for a change made after 451177 (known good), but no lat
er than 451179 (first known bad).

Change Log URL:
https://chromium.googlesource.com/chromium/src/+log/4d81d1e61673e8e3f988fe8efaebf630308f8e85..a33c8f5acb10c229da14134b9987e3b16eaa74f4

Review-Url: https://codereview.chromium.org/2660593002
 
yiyix@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. 

Thanks!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/daf838dca867613a3f7dc9fa915b14b6245da83e

commit daf838dca867613a3f7dc9fa915b14b6245da83e
Author: yiyix <yiyix@chromium.org>
Date: Thu Jul 06 00:36:40 2017

Fix bug: Cursor overlaps with text in omnibox when window is dragged

The cursor location used to get updated after the dragging event is over, 
so the cursor shows in the previous location for some time before jumping 
to the new location as shown in the bug. In this fix, Textfield::OnBoundsChanged 
will trigger location updating for text cursor as well. 

TEXT=TextfieldTest.TextfieldBoundsChangeTest

Bug:  734988 
Change-Id: Idbc05e59b8b97f76ec9d70b5c99b887e69798fda
Reviewed-on: https://chromium-review.googlesource.com/559591
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#484422}
[modify] https://crrev.com/daf838dca867613a3f7dc9fa915b14b6245da83e/ui/views/controls/textfield/textfield.cc
[modify] https://crrev.com/daf838dca867613a3f7dc9fa915b14b6245da83e/ui/views/controls/textfield/textfield_unittest.cc

This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

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

this bug caused another P1. It should land in M61 instead.