- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Aug 2024 19:43:13 +0000
- To: public-css-archive@w3.org
I don't have a strong opinion on this. Like I said in my previous comment, I'm *generally* inclined to canonicalize things early when possible just as a personal taste, but if we get substantially easier impl from delaying the canonicalization until interpolation time and never actually producing an IACVT value, I'm fine with doing that instead. > (or the new percentage keyword). What did you do for that case instead? Just set the basis of the canonicalized form to `100%` or something? > The edits here made the endpoints IACVT, which means that I think the situation [...] can't actually occur. It still can, if it was the *interpolation* making the value too large, due to combining the two endpoints. But, granted, if canonicalization of the endpoints made it too big in and of itself, then indeed the situation wouldn't occur. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10220#issuecomment-2292066787 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 August 2024 19:43:14 UTC