Re: [csswg-drafts] [css-values-5] Should progress functions have a calculation tree as their internal representation? (#10979)

  > Any single value wrapped in a `calc()` will discard the `calc()` at computed-value time.

`progress()` is now a math function therefore it discards `calc()` in a component of a declared value, but other progress functions can not.

  > functions returning `<number>` that aren't math functions don't get any special treatment regarding integers; they're just invalid

So `z-index: progress()` is rounded to the closest integer, but `z-index: container-progress()` is not and is either valid or invalid depending on the function output. But you want to change that, right? (I did not understand your reasoning in the rest of your comment.)

  > there's no functions defined as returning `<integer>` at all

There is `sibling-index()` and `sibling-count()`.

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10979#issuecomment-2415647487 using your GitHub account


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

Received on Wednesday, 16 October 2024 03:24:27 UTC