[csswg-drafts] [css-typed-om] Should a type have a null percent hint to match `<number>`? (#10763)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-typed-om] Should a type have a null percent hint to match `<number>`? ==
Before https://github.com/w3c/css-houdini-drafts/commit/808c87a30bea55b869b30d85e6235e1254839bce, a type always had to have a null percent hint to [match](https://drafts.css-houdini.org/css-typed-om-1/#cssnumericvalue-match) `<number>`. 

Now:

  > If the context in which the value is used does not allow `<percentage>` values, then the type must additionally have a null percent hint to be considered matching.

`opacity: calc((1% + 1px) / 1px)` is now valid if I am not mistaken, which seems unexpected because what is the resolved value of `1%`?

  - the context allows `<number>` and `<percentage>` (resolved to `<number>`)
  - `1%` has type `[percent → 1]`
  - `1% + 1px` has type `[length → 1]` with a `length` percent hint
  - `(1% + 1px) / 1px` has type `[length → 0]` with a `length` percent hint
  - `[length → 0]` with a `length` percent hint matches `<number>`

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10763 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 21 August 2024 03:19:27 UTC