Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[geometry] DOMMatrix parsing does not describe how to handle percentages #536

Open
AtkinsSJ opened this issue Oct 24, 2023 · 0 comments
Open

Comments

@AtkinsSJ
Copy link

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() 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() 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant