- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Feb 2018 21:16:03 +0000
- To: public-houdini-archive@w3.org
> * string representations of values (input to parsing and output from serializing) > * typed OM representations of values > * the underlying representation of the values I think what needs to be defined is: * specified underlying -> Typed OM * computed underlying -> Typed OM * specified Typed OM -> string (this is just "what the author typed") * computed Typed OM -> string "string -> underlying value" is just a CSS parse, not the responsibility of this spec. "string -> Typed OM" is always indirected thru the underlying value; we don't want to define an additional type of parsing. And as you say, "specified underlying -> computed underlying" is a badly-specified part of existing CSS, that @fantasai and I plan to fix at some point soonish. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/718#issuecomment-368653186 using your GitHub account
Received on Monday, 26 February 2018 21:16:13 UTC