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

Hey all,

Thanks for the thoughtful discussion here.

Per most transitional periods for features, we might see pain for a long time as a result of any change. That means we aren't going to take a side about what Blink should do to manage a transition (if any).  

The TAG's job is to make sure that _when_ we arrive at a different world, it's the one that's actually better. A functional DOM that doesn't require wrapping ad infinitum is a goal we must aim for.

Lastly, multiple viewports aren't A Thing (TM) in the platform today. Many APIs we expose simply won't do the right thing in a multi-viewport world. They're the vestigial tail of a once hoped-for future. They do not weigh on the discussion at hand.

The current situation is bad/broken and that fixes which exacerbate the `+` issue won't fly. We also view the `<iframe>` solution as a non-starter. As a result, I'm going to write up a review that captures as much of the discussion here as seems reasonable with the punch-line being that the Blink proposal looks good.

The larger concern I've got is that none of this reads on the root issue: how did `scrollingElement` get decided? How can a programmer set it themselves? I.e., why is this magical? That'll be the meat of the discussion in the writeup.

Regards

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