Re: [csswg-drafts] [css-mixins-1] Problems with public representations of CSSOM values (#11908)

@cdoublev Thanks for the review, as always.

I'll address each point as needed, but first:

I thought there was a distinction between CSSOM APIs that _serialize_ a value (produce valid CSS, e.g. cssText) and those that provide a "JS view" into the underlying data structure.

 - We don't _need_ to CSS-escape a CSSFunctionRule.name, because a JS string already knows where it begins, where it ends, and what its contents are.
 - Similarly, we don't need to wrap a syntax in "type()" if a (JS) string is known to _only_ hold a syntax.

@cdoublev Perhaps you know about some guidelines (or even normative text) that proves my "world view" wrong here?

-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11908#issuecomment-2915741368 using your GitHub account


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

Received on Wednesday, 28 May 2025 10:05:51 UTC