Re: [csswg-drafts] [css-view-transitions] Making the callback param non-nullable (#9460)

The CSS Working Group just discussed `[css-view-transitions] Making the callback param non-nullable`, and agreed to the following:

* `RESOLVED: Make the parameter non-nullable, but keep it optional`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> noamr: we have a startViewTransition call that takes one param that is marked as optional nullable with default of null<br>
&lt;emilio> ... we resolved to extend this to allow a dictionary<br>
&lt;emilio> ... so naively it'd be an optional nullable union<br>
&lt;emilio> ... but that's not possible in WebIDL<br>
&lt;noamr> it's vmpstr, not noamr<br>
&lt;emilio> vmpstr: so proposal is making it non-nullable<br>
&lt;emilio> ... this only precludes null of being a valid parameter<br>
&lt;emilio> ... it'd still be optional<br>
&lt;emilio> astearns: if we decide on null as a naive way of dealing with the optionality?<br>
&lt;emilio> ... was there a purpose?<br>
&lt;emilio> vmpstr: there wasn't, it was just in the editor's draft since the beginning<br>
&lt;khush> +1<br>
&lt;emilio> q+<br>
&lt;khush> q+<br>
&lt;astearns> emilio: so if null is passed we will start throwing?<br>
&lt;astearns> ack emilio<br>
&lt;emilio> vmpstr: that's right<br>
&lt;emilio> emilio: hopefully nobody is doing that, if you're fine with the compat risk seems fine<br>
&lt;emilio> vmpstr: usage is low enough<br>
&lt;emilio> emilio: sounds good then<br>
&lt;emilio> khush: to add to vmpstr there's no production usecase where you'd do that<br>
&lt;emilio> ... because the callback is where you are supposed to mutate the DOM<br>
&lt;emilio> vmpstr: to clarify it's still optional, it'd be just explicit null that could be problematic<br>
&lt;emilio> RESOLVED: Make the parameter non-nullable, but keep it optional<br>
</details>


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


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

Received on Wednesday, 18 October 2023 16:10:57 UTC