- From: Sam Atkins via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Oct 2023 10:36:30 +0000
- To: public-fxtf-archive@w3.org
AtkinsSJ has just created a new issue for https://github.com/w3c/fxtf-drafts: == [geometry] DOMMatrix parsing does not describe how to handle percentages == https://drafts.fxtf.org/geometry/#ref-for-typedef-transform-list > If parsedValue is failure, or any <transform\-function> has <length> values without absolute length units, or any keyword other than none is used, then return failure\. `<percentage>` values appear in some transform-function definitions: 1. In Transforms-1, the [`translate()`](https://www.w3.org/TR/css-transforms-1/#funcdef-transform-translate) functions have `<length-percentage>` parameters. A percentage here needs to be rejected like a non-absolute length, since it cannot be resolved without an element. 2. In Transforms-2, the [`scale()`](https://www.w3.org/TR/css-transforms-2/#funcdef-scale) functions are modified to accept `<percentage>` parameters that are equivalent to numbers, so these can be resolved. Case 2 could be handled during parsing so may not be an issue. But I believe case 1 does need to be covered here. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/536 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 October 2023 10:36:36 UTC