Re: [spec-reviews] CSSOM View document.scrollingElement (#51)

@phistuck,
no I don’t have such an example, but I don’t think that’s the way to measure the correctness of what is being implemented (wrongly in my humble opinion).

Other than that, my proposal was to have a `getScrollingElement` polyfill or a new method on the global space and not a new `scrollingElement` property on the `document`. There may already be enough aliases of the `documentElement/body` on the `document` node if we look at "DOM 1 Core" and the "DOM 2 Traversal".

This proposal does fit with your reasoning on the above code snippet and is future proof for when Webkit would fix the bug about Quirks/Standards modes behavior related to which element scrolls the `viewport`. That behavior have been in the specs for the last decade, the bug was spotted a long time ago but it was never fixed in Webkit. Now that bug was "forcedly" inherited also by Internet Explorer and Opera. It is the right time to fix it in the right way, instead of forcing everybody to make the wrong choice and the specs rewritten.

Have you noticed that everything "scrolling" related (properties and methods) are already bound to the `viewport` ? (see: scrollX, srcollY, scroll(), scrollBy(), scrollTo() and more).

Have you noticed that there is nothing "scrolling" related on the `document` node ?


---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/51#issuecomment-96670276