@l446240525 -- Could you please provide the exact behavior observed.
Observations --
Navigated to the URL provided in the issue and observed different sizes of blocks being displayed.
Did not observe any scroll bar issues, assumed according to the title.
If possible could you please provide a screen cast which would help us in triaging the issue further.

Note: Seeing the same behavior in Firefox also.
Thanks in Advance.

Thank you for providing more feedback. Adding requester "msrchandra@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 the issue on windows 7, Mac 10.12.4 and Linux ubuntu-14.04 using Chrome stable-57.0.2987.133 & Canary-59.0.3063.0
Worked on reverse bisect and below is the info:

Manual Bisect:
------------
First Good build:55.0.2877.0—Revision-422258
Last Bad build:55.0.2876.0 -Revision-421986

Per revision bisect tool info:
------------------------------
You are probably looking for a change made after 422201 (known good), but no later than 422202 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/6403abd0235a72f80ddfd588b3e9bfe4918e497c..20166be8458e48f27382ef6d4fd0679cfccf9361

Possible suspect:
----------------
https://chromium.googlesource.com/chromium/src/+/20166be8458e48f27382ef6d4fd0679cfccf9361

As per the above CL, CC'g 'skobes' & marking it as untriaged for further invetigation from dev.
Thank you!!

This is the intended behavior of the scroll anchoring feature.

For more information about scroll anchoring, see the explainer at:
https://github.com/WICG/ScrollAnchoring/blob/master/explainer.md

Setting "overflow-anchor: none" is the correct solution if this behavior is not desired.