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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=143609

--- Comment #5 from Rick Byers <rbyers at chromium.org> ---
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?

-- 
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/9b05b748/attachment.html>