Re: [csswg-drafts] [resize-observer-1] Firing observations on insert/remove when rendered size is (0, 0) (#7808)

The CSS Working Group just discussed `[resize-observer-1] Firing observations on insert/remove when rendered size is (0, 0)`.

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> vmpstr: we recently resolved to set … to -1 so ro would fire when size is 0,0<br>
&lt;bramus> vmpstr: I think that may break some of the spec because once it fires and you then remove and readd the element, the last reported size will now be 0,0 and the reinsertion wont fire again which is not what we expect<br>
&lt;bramus> vmpstr: we expect the process to be consistent. have a proprosal to have a nullable last reported size as opposed to -1,-1<br>
&lt;bramus> vmpstr: when removed it would be null<br>
&lt;bramus> vmpstr: i think oriol listed all cases to consider<br>
&lt;bramus> oriol: best to go over issues in list<br>
&lt;bramus> oriol: 1st question listed in issue at https://github.com/w3c/csswg-drafts/issues/7808#issuecomment-1263694781 – should we add a notification here?<br>
&lt;bramus> astearns: maybe take the list back to the issue? unless vpmstr has a summary?<br>
&lt;bramus> vpmstr: no strong opinion. most things listed should have a notification. ok with taking back to issue<br>
&lt;bramus> astearns: lets do that<br>
&lt;bramus> astearns: once we have answer to all issues we can bring a proposed resolution to the agenda<br>
&lt;bramus> oriol: call for people to reply in issue, its been open for a while<br>
&lt;bramus> astearns: yes, please record opinions in our issues<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7808#issuecomment-1351796808 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 14 December 2022 17:15:48 UTC