[css-cssom-view-1] Introduce scrollend and overscroll events #4537
Conversation
|
The tests are added under wpt/dom/events/scrolling. |
|
@smaug---- @SamFort-MSFT @smfr FYI |
|
This should define integration with the event loop better. In particular any reactions to some abstract notion of "kernel input" need to queue a task. |
There was a problem hiding this comment.
I think it would be valuable to clarify somewhere whether the overscroll event gets fired even if there is no visual effect (e.g. rubberbanding) applied to the document. Otherwise people may assume that overscroll is only fired when there is a user-visible overscroll effect.
| 1. If <var>doc</var> is already in <var>doc</var>'s <a>pending scroll event targets</a>, abort these steps. | ||
| 1. Append <var>doc</var> to <var>doc</var>'s <a>pending scroll event targets</a>. | ||
| 1. If a <a>viewport</a> is getting scrolled, let <var>doc</var> be the <a>viewport’s</a> associated {{Document}} and <var>target</var> be the <a>viewport</a>. | ||
| Otherwise, an element is gettings scolled and let <var>doc</var> be the element's <a>node document</a> and <var>target</var> be the element. |
There was a problem hiding this comment.
typo: /gettings scolled/getting scrolled/
|
Closing as not being worked on. Also, @argyleink already landed a commit to add |
|
Have we specified the web-exposed behavior for overscroll anywhere (e.g. whether scrollTop etc go negative)? |
[css-spec-shortname-1] Introduce scrollend and overscroll events
This proposal fixes the #3801 issue. It merges the proposed new events from WICG repo into the main spec.