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

> I believe your argument is only compelling when your ignore quirks mode. Even in the future when Blink/WebKit are fixed, libraries still need a bit of logic to determine which element is the scrolling element.

The scenario here is a library that intends to work in quirks mode as well as standards mode? Is that a widespread need? If so that would indeed be a good argument.

The rest of your post explains why you think this will work but doesn't really address my concern for why I think it could not work. In other words, I think you are missing long-term futures like

4) All browsers have irrational behavior where body doesn't truly behave like an element, and documentElement controls scrolling via some APIs (CSS overflow) and not others (scrollTop), and browsers also have a scrollingElement alias for body

or

5) Status quo - confusing differences between browsers - including scrollingElement now also being a new difference

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