<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Consider implementing Document.scrollingElement"
href="https://bugs.webkit.org/show_bug.cgi?id=143609#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Consider implementing Document.scrollingElement"
href="https://bugs.webkit.org/show_bug.cgi?id=143609">bug 143609</a>
from <span class="vcard"><a class="email" href="mailto:benjamin@webkit.org" title="Benjamin Poulain <benjamin@webkit.org>"> <span class="fn">Benjamin Poulain</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=143609#c5">comment #5</a>)
<span class="quote">> I'd rather just fix the damn bug too. The problem is that we're finding
> lots of sites that have been forced to guess at the scrollingElement using a
> UA check (here's an example:
> <a href="https://github.com/google/closure-library/blob/">https://github.com/google/closure-library/blob/</a>
> 32365aba43acb36c5d693256ef5d4dbe3bddddfe/closure/goog/dom/dom.js#L632, and
> Facebook had something similar). I need some good/simple/reliable guidance
> for those sites to migrate to the spec-compatible behavior. After a number
> of failed attempts, I don't see any path for switching blink to the correct
> behavior without first adding such an API. Thoughts?</span >
The problem here is the UA check for detecting behavior.
If it is just a matter of feature detection, one could change scrollTop/Left on body, observe which viewport has been modified, then restore the scroll position.
What I do not like about "scrollingElement" is that it looks like a temporary hack. It goes against keeping the platform simple.</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>