Tested the issue on windows 10 & 7 , Mac OS 10.12.6 using chrome M60 #60.0.3112.113 and M62 #62.0.3201.0 and observed similar behavior in firefox and chrome.
Attached screencast for reference.

@akiff13-- Could you please check attached screencast for reference and let us know if this is the expected result and please check in fresh chrome profile without any extensions and flags enabled and update us with your observations.

Thanks!

Deleted: 760972.mp4 436 KB

	760972.mp4 436 KB View Download

Your behavior is valid. But me and my collegues have invalid behavior as in my screenshot. Div is moving because we can see bug only after moving. We tested it in clear new chromium too. It has the same problem. You should try it with another hardware. It isn't related to windows version(we have different with same bug).

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Able to reproduce this issue on Windows-10 (HiDPI) using chrome latest stable #60.0.3112.113  by following steps mentioned in the original comment.

Bisect Information:
----------------------
Good build: 60.0.3080.0 (466837) 
Bad build:  60.0.3081.0 (467177)

Note: Unable to perform chromium bisect, all the invoked builds are bad even after increasing the good build range. Hence providing manual CL below.

Change Log: https://chromium.googlesource.com/chromium/src/+log/60.0.3080.0..60.0.3081.0?pretty=fuller&n=10000

From the above CL suspecting the below change
https://chromium.googlesource.com/chromium/src/+/aa2022ef0c852f06466f4e82f8f556242129ff89

drott@ - 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!

Looks more like paint than font. Alloe me to label Paint, but please re-assign if this looks incorrect.

pdr@, could you mind to advice what is the most possible cause?

There are any number oif potential blame patches. Here are just a few. I'll try bisecting again.

https://chromium.googlesource.com/chromium/src/+/1931faea0d5ada216fca3c11add153ceaa82ba6d Set GPU rasterization trigger for OOPIFs. kenrb

https://chromium.googlesource.com/chromium/src/+/23d381fd827c8880b85fe5794627e98af07454cc Move LayerImpl's bounds_delta to property trees, pdr

https://chromium.googlesource.com/chromium/src/+/db968800ed0e05f677ffceaceebe8e94c0edf95f. Skia roll

https://chromium.googlesource.com/chromium/src/+/0e55c1eae61583ba6634a8a58cb30a2b38c922a9 cc: Sync scroll/animation state for impl-side pending tree. 

https://chromium.googlesource.com/chromium/src/+/b1e280d1a61f77855418913417c941c7faff176c cc: Push Animation Finished State and Use Finished State for IsCompleted weiliangc

I could not reproduce with Windows 10 HighDPI (125%) with Version 61.0.3163.59 (Official Build) beta (64-bit).

Given M-61 is rolling out any day now, this seems like we should wait.

akiff13@, do you have the same problem with Chrome Canary?

Can you paste in the results from visiting chrome://gpu for a computer that works and one that does not?

Just got to this bug after my vacation. I agree that this does not trivially reproduce, but it could definitely be due to a difference in our hardware.

As Stephen noted, can you try with Chrome Canary (or re-try with Chrome 61 which should be out now)? If you are still able to reproduce, please go to chrome://gpu, file>save as, and attach the file here.

Testing team: does the repro that you found in comment 5 still work on Canary,
or has it since been fixed?

The NextAction date has arrived: 2017-09-18

Response to C#10, Still we are able to reproduce the issue on latest Canary-63.0.3221.0 on Windows 10 (HiDPI) machine .Removing Test-Confirmation label.
Thanks.

jmukthavaram, can you please post your chrome://gpu information?

I'm not able to reproduce this locally but I think it is likely hardware-specific.

Because this only reproduces on some hardware, I suspect this is cc and not paint. Could also be the Skia roll. I tried to reproduce on both low and high dpi on windows.

Please also try with --disable-d3d11 . Does that fix it?

@robertphillips: this appears to a duplicate of  issue 755871 , can you confirm?

It seems unlikely to be a duplicate of  crbug.com/755871 . That bug is driven by an ancient Intel driver bug. This CL seems reproducible on Windows 10.

akiff13@, is this still happening with Chrome 61? What happens if you disable d3d11 as requested in comment #15?

Testing team: please post the contents of about:gpu and more information about
the specific device.

As per comment #18 attaching GPU details. I have Windows-10 Dell Precision M3800 (HiDPI). 

Deleted: chrome___gpu.pdf 133 KB

chrome___gpu.pdf 133 KB Download

Given the symptoms (i.e., noise on Angle/D3D11) I suspect this is a duplicate of  crbug.com/768134 . 

I have never been able to repro this bug locally however. Could someone who can repro the problem consistently see if it still repros in the 63.0.3234.0 (or above) Canary? Unfortunately, the fix is not yet in any available Beta.

Verified this issue on Windows-10 using chrome latest canary #63.0.3237.7 and latest beta #62.0.3202.52, Observed no noise in the animation using the test case provided in the original comment and confirming this issue got fixed and working as expected.

Thanks!

Given the comments in #22, I'm duplicating this into  crbug.com/768134 

The NextAction date has arrived: 2017-10-16