- From: Isiah Meadows via GitHub <sysbot+gh@w3.org>
- Date: Sun, 16 Dec 2018 22:19:51 +0000
- To: public-houdini-archive@w3.org
isiahmeadows has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-typed-om] Why is StylePropertyMap.get defined to return `undefined` instead of `null`? == In [this section](https://drafts.css-houdini.org/css-typed-om/#dom-stylepropertymapreadonly-get) and the [associated IDL](https://drafts.css-houdini.org/css-typed-om/#the-stylepropertymap), `StylePropertyMap.get` is defined to return either `undefined` or the resulting `CSSStyleProperty`. This is inconsistent with the DOM and HTML specs, which use the optional type `T?` which means `T or null`. It's very explicit in the spec it means to use `undefined`, even though it doesn't explain its departure from `null` and `T?`, so I was just wondering what the reasoning behind it was. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/848 using your GitHub account
Received on Sunday, 16 December 2018 22:19:53 UTC