To avoid this kind of ambiguities like `pow(2%, 4)`, I support > TabAtkins: Maybe go back to pow() and sqrt() only accept numbers Then authors can choose `pow(2, 4) * 1%` to get `16%` or `pow(2/100, 4) * 100%` to get `0.000016%`. Note this is not just about percentages, e.g. if `1in` is `96px`, then it doesn't make much sense if `pow(1in, 2)` is still `1in` or `96px`, but `pow(96px, 2)` becomes `9216px`. If values with non-empty types are accepted, the types should be multiplied. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2331#issuecomment-468660481 using your GitHub accountReceived on Friday, 1 March 2019 13:13:22 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:44 UTC