Re: [csswg-drafts] [css-overscroll-scrollend-events] Content has no way of understanding whether it is being overscrolled or whether scroll has ended (#3801)

> I envisioned overscroll events being about rubber banding within a given scrollable area (sending scroll event with negative offsets is not very web-compatible)

This is the intention. The sign only tries to capture the direction of it. i.e. if you are overscrolling/rubbber banding from the right or from the left.  Note that these are not `scroll` events. So they do not interfere with the current web. So I don't think they would cause any web compat issues. The proposal is to have a new event for rubber banding called `overscroll` that has this delta that could be negative.

> Using them to propagate information about scrolls between iframe needs more thought, particularly across origin boundaries
The scrolling itself is already exposed somewhat. As you may start the finger within a cross origin iframe and the outerframe might get scrolled (due to scroll chaining). This is just to expose the information in the same space (i.e. scrolling) to the content that is being scrolled. So it is not so much as leaking information (like touch move path or anything) to a cross origin. What do you think?

-- 
GitHub Notification of comment by NavidZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3801#issuecomment-571330482 using your GitHub account

Received on Monday, 6 January 2020 21:50:43 UTC