- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Jan 2018 05:27:10 +0000
- To: public-houdini-archive@w3.org
dbaron has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-typed-om] "Create a CSSUnitValue from a string" invents its own CSS parsing == The definition of [create a CSSUnitValue from a string](https://drafts.css-houdini.org/css-typed-om-1/#create-a-cssunitvalue-from-a-string) says: > To create a CSSUnitValue from a string str, return a new CSSUnitValue object with its value internal slot set to the numeric portion of str parsed into a number, and its unit internal slot set to the unit portion of str, or "number" or "percent" if str is a plain number or percent. This seems to be inventing its own CSS parsing, and does it in a rather vague way (for example, what's a "numeric portion" -- does it support scientific notation?). It seems like it would be better to depend on the way CSS already parses dimensions. Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/600 using your GitHub account
Received on Monday, 29 January 2018 05:29:30 UTC