W3C home > Mailing lists > Public > www-style@w3.org > April 2015

[cssom-view] Easing the transition to spec-compatible body scrollTop behavior

From: Rick Byers <rbyers@chromium.org>
Date: Wed, 8 Apr 2015 15:34:05 -0400
Message-ID: <CAFUtAY8eEfBv4UReuZ_mzJe0arvrDKG-c0T0w7mzuZ2rYMr+pQ@mail.gmail.com>
To: "www-style@w3.org" <www-style@w3.org>, Simon Pieters <simonp@opera.com>
I'm continuing to try to get blink fixed
<https://code.google.com/p/chromium/issues/detail?id=157855> to follow the
spec for body/documentElement scrollTop/Left behavior.  We've uncovered another
framework <https://code.google.com/p/chromium/issues/detail?id=426181>
which relies on a WebKit UA check, making it hard for us to change.  It's
not at all clear to me when (or even if) we'll be able to ship
spec-compatible behavior without an unacceptable level of breakage.

At the same time, while working with Facebook engineers we realized there
isn't really any great work-around for existing code trying to support both
types of browsers.  Naive approaches like this one
<https://gist.github.com/dperini/ac3d921d6a08f10fd10e> don't work
reliably.  The best I've seen now is to have explicit functions for getting
and setting the document scroll position (which set both
body/documentElement, and get returning whichever is non-zero).  But this
is hard to integrate to existing code
that expects to be able to determine the Element which can scroll the

How about we make this transition easier by explicitly defining an API
which returns either documentElement or body depending on which one scrolls
the viewport?  Frameworks can rely on a heuristic polyfill for existing
browser engines, while newer engines can tell the page explicitly which
element they're supposed to use.  This should also make dealing with
framework code (which may or may not be used in quirks mode) a little
simpler too.

Received on Wednesday, 8 April 2015 19:34:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC