fix chrome warning

[ben8p]

When documentElement.scrollTop is 0

[cameronjacobson]

Are there specific scenarios, environments, or versions where this is happening? When I isolate the code, and run the following from Chrome's console:

document.documentElement.scrollTop || document.body.scrollTop
//  - or -
document.body.scrollTop || document.documentElement.scrollTop
//  - or -
document.documentElement.scrollLeft || document.body.scrollLeft
//  - or -
document.body.scrollLeft || document.documentElement.scrollLeft

I get expected results. A 'number' type. And when the page is scrolled to the top / left I get 0.

[ben8p]

With the original code, if
document.documentElement.scrollTop returns 0 then document.body.scrollTop
will be evaluated but in strict mode it is deprecared. Thus Chrome send a
warning.
The test prevent the warning.

Le jeu 12 mars 2015 20:41, Cameron Jacobson [email protected] a
écrit :

Are there specific scenarios, environments, or versions where this is

happening? When I isolate the code, and run the following from Chrome's
console:

document.documentElement.scrollTop || document.body.scrollTop
// - or -
document.body.scrollTop || document.documentElement.scrollTop
// - or -
document.documentElement.scrollLeft || document.body.scrollLeft
// - or -
document.body.scrollLeft || document.documentElement.scrollLeft

I get expected results. A 'number' type. And when the page is scrolled to
the top / left I get 0.

—
Reply to this email directly or view it on GitHub
#826 (comment)
.

[cameronjacobson]

I was able to find several threads / discussions about this. While reading through a lot of them, I found the following thread which appears to explain things more thoroughly.

https://code.google.com/p/chromium/issues/detail?id=342307

Part of the way down the thread [comment number 6] someone mentions that they have in fact removed the warning. This was based on a search on GitHub that indicated the issue is less prevalent now than when they originally placed the warning.

There is also mention [comment number 4] that the existing code in raphaeljs works cross-browser. I don't know if this means it will in fact eventually be deprecated, but my hunch is it would not be recommended if this was the case. That individual is using a samsung.com email, but scrolling further [comment number 6] does indicate that they "do not work for Google, ... but are contributor to Blink".

That was as authoritative an answer as I was able to find.

[tomasAlabes]

Any update on this? Seems an old inconvenience in Chrome