Re: [csswg-drafts] [css-scroll-snap-2] Use present tense for snap event names (#9697)

The CSS Working Group just discussed `[css-scroll-snap-2] Use present tense for snap event names`, and agreed to the following:

* `RESOLVED: scrollsnapchanging and snapchange`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> flackr: was pointed out that "snapchanged" event felt inconsistent with other names which use present tense<br>
&lt;fantasai> flackr: removing past tense, and adding 'scroll' in front of 'snap'<br>
&lt;fantasai> flackr: the idea was to make them sort next to the scroll events<br>
&lt;fantasai> flackr: proposal is snapchanged -> scrollsnapchange and snapchanging -> scrollsnapchanging<br>
&lt;TabAtkins> No particular opinion, except I agree the tense change is good.<br>
&lt;fantasai> flackr: I think the tense change is good, ambivalent about adding 'scroll'<br>
&lt;fantasai> flackr: they do only apply to scroll containers<br>
&lt;fantasai> flackr: so not unreasonable to say 'scroll'<br>
&lt;TabAtkins> I don't think "scroll" is quite necessary, unlikely that "snap" will ever apply meaningfully to anything else<br>
&lt;fantasai> Agree, but the one benefit is it aligns closer to the CSS properties<br>
&lt;fantasai> which makes it easier for people to associate them<br>
&lt;fantasai> RESOLVED: scrollsnapchanging and snapchange<br>
&lt;TabAtkins> Yeah, that's fair.<br>
</details>


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


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

Received on Wednesday, 1 May 2024 23:19:42 UTC