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

In #7734 we resolved to use empty array when there is no box, so automatically it should follow that these trigger notifications, since there will be a change between `[]` and `[(0,0)]`:

 - When a disconnected element becomes connected and generates a 0x0 box, or viceversa.
 - When a connected element that generated no box starts generating a 0x0 box, or viceversa.

Here we keep having `[]`, and doing something special to get a notification doesn't seem worth it:
 - When a disconnected element becomes connected but generates no box, or an element that generates no box is disconnected from the DOM.

Here a notification can still be achieved by initializing the array to something invalid like `[(-1,-1)]`:

 - When an element whose size is considered to be 0x0 is first observed: #3664 said yes, and I guess this is regardless of whether it's an actual 0x0 box, or it's an inline box, or there is no box, or the element is disconnected from the DOM.

And I guess these will depend on what we do for inline boxes (#6358):
 - When a disconnected element becomes connected and generates an inline box, or viceversa.
 - When a connected element that generated no box starts generating an inline box, or viceversa.
 - When an element that generated a 0x0 box becomes an inline box, or viceversa.

I think inline boxes should just populate the array with the actual sizes, then the first 2 cases would change between empty and non-empty array, triggering a notification. The 3rd case would typically trigger a notification too, but wouldn't for a 0x0 inline (e.g. `font-size: 0`).

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


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

Received on Friday, 16 December 2022 23:08:08 UTC