- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Oct 2017 17:31:53 +0000
- To: public-houdini-archive@w3.org
Any input that can potentially accept a CSS `<number>` (or, in TypedOM language, any place where a CSSUnitValue with a type of "number" would be valid) should be a `CSSNumberish`. Many numeric attributes don't qualify; the difference in the transform style constructors is deliberate, as translate() only takes lengths. Output should always be `CSSNumericValue`, as we'll always output TypedOM objects. (So yeah, readonly attributes are `CSSNumericValue`, read/write attributes are `CSSNumberish` *if* they can accept a `<number>` value.) (`CSSKeywordish` is more absolute - *all* keyword-accepting input should be `CSSKeywordish`. There's no conglomeration of value spaces to worry about here.) ------- Note: I wrote my earlier comment based on the first comment in the thread, coming straight off of the email. I hadn't seen the second comment. I was specifically referring to `CSSMathNegate` needing to be switched to `CSSNumberish`, not referring to the transform stuff. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/498#issuecomment-340035338 using your GitHub account
Received on Friday, 27 October 2017 17:31:56 UTC