Re: [csswg-drafts] [cssom-view] VisualViewport should probably also include onscrollend (#8103)

+1, it'd be nice for this to be in normative text. I'm also not a spec expert but I think adding text in the "scrolling is completed" [steps](https://drafts.csswg.org/cssom-view/#scrolling-events:~:text=Whenever%20scrolling%20is%20completed%2C%20the%20user%20agent%20must%20run%20these%20steps) is probably correct.

I added similar text in  [run the scroll steps](https://drafts.csswg.org/cssom-view/#document-run-the-scroll-steps) for the visual viewport:

```
If target is a Document, fire an event named scroll that bubbles at target and fire an event named scroll at the VisualViewport that is associated with target.
```

Rereading this now, I think this says that whenever the document is scrolled we should also fire `scroll` at the VisualViewport, even if the VisualViewport offset doesn't change. I think that's wrong, we should only fire `scroll` at VisualViewport if its offset changes.

I think we want to add VisualViewport to the `pending scroll event targets`:

```
Whenever a VisualViewport gets scrolled (whether in response to user interaction or by an API), the user agent must run these steps:...
``` 

And then the run scroll steps should be:

```
 * If target is a Document, fire an event named scroll that bubbles at target
 * If target is a VisualViewport, fire an event named scroll at it.
```

And then add similar language for the scrollend steps.

@argyleink - if you're already doing work here would you mind making these changes? If not, I could probably squeeze in a PR later this week.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 29 November 2022 20:41:34 UTC