<html>
    <head>
      <base href="https://bugs.webkit.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Consider implementing Document.scrollingElement"
   href="https://bugs.webkit.org/show_bug.cgi?id=143609">143609</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Consider implementing Document.scrollingElement
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>528+ (Nightly build)
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Unspecified
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>HTML DOM
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>rbyers&#64;chromium.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Document.scrollingElement would always return 'body' in WebKit's (non-spec-compliant) implementation, until <a class="bz_bug_link 
          bz_status_REOPENED "
   title="REOPENED - document.body.scrollTop &amp; document.documentElement.scrollTop differ cross-browser"
   href="show_bug.cgi?id=106133">bug 106133</a> is fixed.  Today some frameworks are forced to rely on a UA check to try to predict this behavior.  Document.scrollingElement is designed to be a trivial API for the engine to tell JS exactly which element (body or documentElement) it considers to be the one that scrolls the viewport.

See <a href="http://dev.w3.org/csswg/cssom-view/#dom-document-scrollingelement">http://dev.w3.org/csswg/cssom-view/#dom-document-scrollingelement</a>
And <a href="https://lists.w3.org/Archives/Public/www-style/2015Apr/0108.html">https://lists.w3.org/Archives/Public/www-style/2015Apr/0108.html</a>

We're planning on shipping this API in blink ASAP to help ease the transition to spec-compliant scrollTop/scrollLeft behavior (<a href="https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/mJ5SlCj3CHc">https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/mJ5SlCj3CHc</a>).  However we'd like some feedback from other vendors before we do so.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>