[Webkit-unassigned] [Bug 143609] Consider implementing Document.scrollingElement

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 13 12:50:44 PDT 2015


--- Comment #6 from Benjamin Poulain <benjamin at webkit.org> ---
(In reply to comment #5)
> 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:
> https://github.com/google/closure-library/blob/
> 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?

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.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150413/46d95e79/attachment.html>

More information about the webkit-unassigned mailing list