Re: [heycam/webidl] Investigate banning nullable enums (#213)

> https://drafts.csswg.org/web-animations/#dictdef-basecomputedkeyframe
> https://drafts.csswg.org/web-animations/#dictdef-basepropertyindexedkeyframe
>  https://drafts.csswg.org/web-animations/#dictdef-basekeyframe

Yeah, this one is a bit weird.  It might have been nicer to have an explicit "default" value or something...  @birtles do you recall why null was picked here?  I should have asked this in <https://bugzilla.mozilla.org/show_bug.cgi?id=1429671>...

>  https://w3c.github.io/web-nfc/#dom-nfcwatchoptions

This one hasn't had wide review yet, so hard to say what the story there is.  The prose talks about a default value of "", the IDL has no default value at all.  I would assume that this IDL has nothing to do with whatever reality exists here, if any.

>https://w3c.github.io/webrtc-pc/#dom-rtcicecandidate
>https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver

I _think_ here null is used to mean "we don't know".  Not sure why that couldn't be an enum value, but its possible that these specs don't fully control the value set of these enums or something... @jan-ivar do you know?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/213#issuecomment-411445554