- From: mattwoodrow via GitHub <sysbot+gh@w3.org>
- Date: Sun, 08 Oct 2023 08:38:08 +0000
- To: public-css-archive@w3.org
I feel like that case is somewhat different (in my mind, at least), in that UAs were using the presence of a 3d transform function as an internal heuristic for which rendering path to use (which also had very subtle rendering differences due to antialiasing), and there was resistance to leaking that into the spec since it should just be an implementation detail. In this case, the 3d-ness is super relevant to what we're trying to define, so I think it's more reasonable to put into the spec. I agree that using the 3D functions rather than the computed matrix has more predictable behaviour. Regardless, this might be worth putting on the Agenda to discuss more widely. -- GitHub Notification of comment by mattwoodrow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/918#issuecomment-1751963498 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 8 October 2023 08:38:10 UTC