- From: Jonathan Chan via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Jun 2016 20:23:50 +0000
- To: public-houdini-archive@w3.org
jonathanyc has just created a new issue for https://github.com/w3c/css-houdini-drafts: == [css-typed-om] CSSLengthValue normalization typo? == The [section](https://drafts.css-houdini.org/css-typed-om/#lengthvalue-normalization) on CSSLengthValue normalization says: `Otherwise, if the provided value can be parsed as a calc expression with a resolved type of <length> or <percentage>, then a CSSCalcLength is constructed with each unit that is mentioned in the calc expression reflected as the matching attribute set to the appropriate value.` But in the linked spec on 'resolved type,' it says that: `A math expression has a resolved type, which is one of <length>, <frequency>, <angle>, <time>, <number>, or <integer>. ... If percentages are accepted in the context in which the expression is placed, a <percentage-token> has the type of the value that percentages are relative to; otherwise, a math expression containing percentages is invalid.` Is there some spec that says `<percentage>` is also a resolved type, or is this a typo? Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/249 using your GitHub account
Received on Friday, 24 June 2016 20:23:53 UTC