Re: [csswg-drafts] [css-contain-2] Incomplete event definition for ContentVisibilityAutoStateChanged (#7603)

The CSS Working Group just discussed `[css-contain-2] Incomplete event definition for ContentVisibilityAutoStateChanged`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: [css-contain-2] Incomplete event definition for ContentVisibilityAutoStateChanged<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/7603<br>
&lt;fantasai> oriol: This issue covers different things, but only want to discuss name of the event<br>
&lt;fantasai> oriol: contain introduced ContentVisiblityAutoStateChanged event<br>
&lt;fantasai> oriol: this is inconsistent naming, since other events they use the present tense and this is using past tense<br>
&lt;fantasai> oriol: there's even a proposed design principle in TAG about naming events about avoiding past tense<br>
&lt;fantasai> oriol: just some legacy events are using past tense<br>
&lt;fantasai> oriol: So should we align with this design principle?<br>
&lt;fantasai> oriol: This feature has already shipped in Blink in July or such<br>
&lt;fantasai> oriol: but maybe it could still be compatible to change or maybe Blink could support both for awhile or something like that<br>
&lt;fantasai> oriol: Firefox is implementing now, and WebKit has not implemented this property yet<br>
&lt;fantasai> florian: Do you want to change the name of the event and the object type or just the event?<br>
&lt;vmpstr> q+<br>
&lt;fantasai> oriol: It should be consistent<br>
&lt;flackr> I *think* this is the use counter for registrations: https://chromestatus.com/metrics/feature/timeline/popularity/4328<br>
&lt;emilio> ack emilio<br>
&lt;vmpstr> https://chromestatus.com/metrics/feature/popularity#ContentVisibilityAutoStateChangedHandlerRegistered<br>
&lt;Rossen_> ack vmpstr<br>
&lt;fantasai> vmpstr: On Chrome status there is 0.048% that register a handle for this event<br>
&lt;fantasai> vmpstr: it's a low usage but it's non-zero<br>
&lt;fantasai> Rossen_: is that above the threshold? Wasn't it 0.03%<br>
&lt;fantasai> vmpstr: Justification is that the state change has already happened, different from click event where you can preventDefault<br>
&lt;fantasai> vmpstr: but that's why it was named in the past tense<br>
&lt;flackr> Also animationstart, animationend, transitionstart, transitionend<br>
&lt;fantasai> oriol: form controls also have change event for afterwards, can't prevent change, and this event is in present<br>
&lt;emilio> Yeah, lots of precedents there, `visibilitychange` / `pageshow` / etc<br>
&lt;emilio> +1 for changing<br>
&lt;fantasai> Rossen_: Can we resolve to change, and if we get feedback strongly that this will be a problem, we can revisit?<br>
&lt;fantasai> Rossen_: from spec point of view, right thing to resolve is in favor of change<br>
&lt;fantasai> +1<br>
&lt;vmpstr> +1<br>
&lt;Rossen_> q?<br>
&lt;fantasai> RESOVLED: Change to present tense for ContentVisiblityAutoStateChanged (event and object)<br>
</details>


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


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

Received on Wednesday, 9 November 2022 17:56:19 UTC