- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Mar 2025 11:47:18 +0000
- To: public-css-archive@w3.org
> > Like briefly discussed elsewhere, should we be using a CSSOMString? return value for attributes that possibly have no value? (And return null instead of "" when there is no value?) > > Yup, an _empty_ default and _no_ default are definitely distinct values, and need to be represented differently in the OM. I've gone ahead and made the default `CSSOMString?` to accommodate. Right, looks like we already did represent it differently: no default = no entry in the dictionary; empty default = empty CSSOMString. I take it we then prefer an explicit null entry if there is no default? -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11832#issuecomment-2713851576 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 March 2025 11:47:19 UTC