[css-scroll-snap-2] Use present tense for snap event names

[DavMila]

It was pointed out here that "snapchanged" (introduced in the scroll-snap-2 spec) doesn't follow the convention of using present tense to name JavaScript events.

Additionally, zcorpan suggests using names that put the snap events closer, alphabetically, to the scroll and scrollend events.

To riff off on that suggestion, I propose:

• scrollsnapchanging instead of snapchanging, and
• scrollsnapchange instead of snapchanged

which reflect not just that snapping is happening but that there is a change in snap targets as is the intention of the events.

[css-meeting-bot]

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 scrollsnapchange

The full IRC log of that discussion

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