- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Sep 2022 02:51:28 +0000
- To: public-css-archive@w3.org
> Yes, but these listed properties were already broken with an initial observation of [(0, 0)], e.g. Agreed. I didn't mean to say that the change to -1,-1 is wrong, I meant to say that it doesn't handle all cases, such as insertion/removal of a 0x0 element. Based on Blink code and the current spec, it sounds like the idea was that when the element is out of the DOM, it would have a 0x0 size and when it's in the DOM and rendered, then it would have non-0x0 size. So I don't think the case of having a rendered size of 0x0 was considered in detail. I like your idea of having a [] size, which is the same as what I wrote about a nullable last size. That should fix all the issues without the need for -1,-1 initialization, right? -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7808#issuecomment-1261674834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 September 2022 02:51:30 UTC