Created a minified test case here: https://jsfiddle.net/aerkp0ga/. 

Definitely breaking with spec here: https://drafts.csswg.org/cssom-view/#dom-element-scrolltop

Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.4 with chrome #59.0.3061.3
Issue broken in M59

Bisect Info:
===========
Good build : 59.0.3056.0 ,  Revision Range - 460603
Bad build  : 59.0.3057.0 ,  Revision Range - 460966

After executing the per-revision bisect script , i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/174eb44312202a5132de900553f7c302da0feef6..85bab14c835935e79a0b63f24b47f671840373de

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/85bab14c835935e79a0b63f24b47f671840373de

Review-Url: https://codereview.chromium.org/2743053003

erikchen@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Gentle Ping!
erikchen@ could you please look into this issue.

Thanks..

Erik since this was bisected to your change can you have the first look at it?

I'm running Version 60.0.3112.101 (Official Build) (64-bit) on a Mac and this problem exists in all situations; not just full screen.

Whenever I scroll a page and run document.body.scrollTop from dev tools it returns `0`.

I'm running beta Channel Version 61.0.3163.59 (Official Build) beta (64-bit) on Mac OS. I'm also noticing `document.body.scrollTop` always returns `0` no matter the scrolled position on the page. Current Stable version (Version 60.0.3112.101 (Official Build) (64-bit)) seems to be working fine. What I want to know is if this behavior (relaying on document.documentElement.scrollTop instead of document.body.scrollTop) is related only to the beta/dev/canary channels or is it going to be part of the stable release once 61 gets released.

This is likely related to, and fixed by: https://bugs.chromium.org/p/chromium/issues/detail?id=758130#c5.

TEs, can you confirm that this problem is fixed on ToT?

Tested on latest Canary #62.0.3201.0 on Windows 7, Mac 10.12.6 and Ubuntu 14.04 and still able to reproduce the issue.

Attached the screenshot for reference.

Removing the label 'Needs-TestConfirmation'.

Thanks.

Deleted: 706971.png 532 KB

	706971.png 532 KB View Download

I'm running stable channel Version 61.0.3163.91 (Official Build) (64-bit) on Mac OS Sierra 10.12.5 and I still get that issue; `document.body.scrollTop` returns always 0 even if the full screen mode is not enabled.

to reproduce the issue:
- execute window.scrollTo(0,100);
- document.body.scrollTop return 0 instead of 100

I've checkout out an old Chromium Version 59.0.3071.0 (Developer Build) (64-bit) Mac OS from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/464642/ and tried the same scenario: document.body.scrollTop returns the right scrollTop value 100.

Thanks,

#15 - a non-full-screen version of this issue is unrelated here, please, only mention full-screen body.scrollTop issues here.

The issue you mentioned is an intentional change (albeit accidentally without a lot of forewarning). Firefox behaved this way for years.
See https://www.chromestatus.com/feature/6386758136627200 for some details.

erikchen@ can you take another look. It seems that TE does still see the issue.