- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 20:02:09 +0000
- To: public-css-archive@w3.org
We had some Chromium discussion of this in https://chromium-review.googlesource.com/c/chromium/src/+/4878164?tab=comments , but really the conclusion there was to fix the test to accept multiple possible behaviors (as discussed above in https://github.com/w3c/csswg-drafts/issues/9121#issuecomment-1683001516) until this issue is resolved. As far as sensible behavior goes: * I think it's strange to return a `matrix()` for elements that are `display: none` because doing so, for some cases (resolving percentages) requires making up a size of box to resolve those percentages against. * I also think it's strange to return `none` (as the resolved value) when the computed value isn't `none`, with the exception of cases where `transform` doesn't apply (like `display: inline`) where I think returning `none` does make sense. * It's probably bad to return something closer to the computed value (a list of functions) because it's bad for calling code to get something other than a `matrix()` for edge cases when the calling code expects either `matrix()` or `none`. So, basically, I think all three possible behaviors that I've thought of are bad. It sounds like we also need to worry a good bit about compatibility here, which may mean that we should just pick the bad thing that's web-compatible instead of the bad things that aren't web-compatible. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9121#issuecomment-1756139759 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 20:02:11 UTC