Tess: CSS will be disucssing this tonight

David: I think this is pointing out a gap in the design principles doc... we ought to be able to document how people make this sort of decision so people do it with some sort of consistency. I'll open an issue on that doc.

Peter: We've been down this road before on the design principles

Sanghwan: and we never actually fix the document

Peter: I know CSS WG have done this before...

David: You're right, it's issue 55 that is closest to this. I'll link to it.

Torgo: Is there a link to the CSS Agenda?

David: https://lists.w3.org/Archives/Public/www-style/2019Apr/0012.html

Torgo: MIlestone for next wee

Tess: last time we talked about this was before a CSS call.

Peter: this wasn't discussed on the [CSS] call.

David: [nobody] really cared about this detail.

Alice: in the linked CSS wd draft issue they said they resolved null and asked us. Null seems fine to me. David saw your proposal about undefined but don't know about that.

Alice: i think our opinion is "not an exception"

Dan: can we close this?

Tess: sounds like we can to me - unless anyone has strong feelings.

Peter: i'm ok with it returning Null. Meta question: do we have advice in our API design guidelines for this sort of thing.

Tess: can we close this issue and open up a design guidelines issue?

Alice: already have an issue - that david referenced in that review.

Tess: I'll comment on it and close it.

[woot!