Re: [csswg-drafts] [cssom-view] Scroll steps don't match implementations (#11164)

The CSS Working Group just discussed `[cssom-view] Scroll steps don't match implementations`, and agreed to the following:

* `RESOLVED: Fix up the spec to put all scroll-related events in a single queue`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> emilio: the cssom-view spec has a bunch of issues, it doesn't match impls in several parts and are just wrong in several<br>
&lt;TabAtkins> emilio: scroll events aren't fired at a specific time, scroll-snap are fired before other scroll events, there's no distinction between visual viewport and others<br>
&lt;TabAtkins> emilio: i posted my research on how browser behave in this regard<br>
&lt;TabAtkins> emilio: webkit and gecko order visual viewport and regular scroll events consistently<br>
&lt;TabAtkins> emilio: with addition of scrollEnd and scorllSnap, the chromium appraoch of just having them on the same separate queue and fire them in order makes sense, i think<br>
&lt;TabAtkins> emilio: in aprticular, i don't see a reason why scroll triggered by some events should fire on the same frame vs another<br>
&lt;TabAtkins> emilio: so having all scroll events in one queue, fired in order<br>
&lt;TabAtkins> emilio: and side effects firing in next frame. seems fine<br>
&lt;TabAtkins> emilio: i have a patch to fix all this, but wondered if people have strong opinions<br>
&lt;TabAtkins> astearns: did you do any looking back thru commit history to see why scrollsnap is sbefore all other events?<br>
&lt;TabAtkins> emilio: no, they were the last added and i think they were just put in the wrong place<br>
&lt;TabAtkins> TabAtkins: i defer to flackr, so as long as he's looked at it i'm happy to accept emilio's opinion<br>
&lt;TabAtkins> astearns: everyone was pinged, no comments in a few months<br>
&lt;TabAtkins> dbaron: flackr or skobes, i'll ping them both<br>
&lt;TabAtkins> astearns: do people want to wait on a positive response? i'm happy to just change the spec<br>
&lt;TabAtkins> TabAtkins: i think the spec is messy enough that we can just merge what we have and quibble over the details<br>
&lt;TabAtkins> ntim: should i ping Simon?<br>
&lt;TabAtkins> emilio: yes plz<br>
&lt;TabAtkins> astearns: do you think we should wait on resolution?<br>
&lt;TabAtkins> ntim: dunno<br>
&lt;TabAtkins> dbaron: i guess i dont' feel like we have to wait. would be nice to get thru to them at some point, but it can be post resolution<br>
&lt;TabAtkins> astearns: so proposed: Fix up the spec to put all scroll-related events in a single queue<br>
&lt;TabAtkins> ntim: one argument for waiting for simon is he's co-editor<br>
&lt;TabAtkins> emilio: that means he can revert my change<br>
&lt;TabAtkins> astearns: yeah, it's been months and i'd like to move things along<br>
&lt;TabAtkins> astearns: objections to the proposed resolution?<br>
&lt;TabAtkins> RESOLVED: Fix up the spec to put all scroll-related events in a single queue<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11164#issuecomment-2776275645 using your GitHub account


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

Received on Thursday, 3 April 2025 16:01:20 UTC