You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, I missed that <percentage> should actually have been replaced with <percentage-token> in the <progress> production rule, as explained in the detailed definition appearing below the production rule:
<percentage-token> [...]
Note: This only allows literal percentages, like 15%; calculations like calc(100% / 7) will not work [...].
But this restriction seems to be motivated solely by internal constraints that authors would not understand it, imo.
Would it not be possible to say that <percentage> always resolves to [percentage → 1] as a term of a math function replacing <progress>?
- the type of <'animation-timeline'> for <progress> must be []
- the type of <percentage> for <progress> must be [percentage → 1]
- the type of <percentage> in math functions for <progress> must be [percentage → 1]
- the type of <percentage> in progress() must always be based on the closest context
- the type of <calc-mix()> calculations do not need to be made consistent with
its <progress>
w3c/csswg-drafts#10770
Uh oh!
There was an error while loading. Please reload this page.
The type of
calc-mix()
must be made consistent with the type of its<progress>
, which is defined with:What is the type of
<progress>
in these examples?calc-mix(0%, 1px, 2px)
in a<length-percentage>
contextcalc-mix(calc(0%), 1px, 2px)
in a<length-percentage>
contextcalc-mix(--timeline, 1px, 2px)
My respective guesses:
[percentage → 1]
[percentage → 1]
[]
In my opinion, the type of
calc(0%)
matching<progress>
should always be[percentage → 1]
, whatever the "higher" context is.The text was updated successfully, but these errors were encountered: