Re: [w3ctag/design-reviews] Review request for ResizeObserver (#187)

Questions!

 - Why aren't the new & old sizes provided by the API directly? Is it always going to be cheap to call `window.getComputedStyle()` within the callback to get the new sizes?
 - The spec includes non-normative text along the lines of `observation will fire when observation starts if Element has display, and Element’s size is not 0,0`, but this seems to ignore "external" visual artifacts like `box-shadow` and `outline` rules that might still cause an element to paint without width/height...or is that incorrect?
 - What's the timing relationship between Resize Observer delivery and Intersection Observer records? I presume the latter happens (sometimes much) later?
 - Is there more example code? ISTM that the explainer should include much more example code to outline the various scenarios where RO will be used.
 - How do RO's work with proxies like the [Offscreen Canvas proposal](https://developer.mozilla.org/en-US/docs/Web/API/OffscreenCanvas)?
 - Were design alternatives considered? If so, why were they discarded?

Regarding Explainer style, we've put together a [draft outline here](https://docs.google.com/document/d/1cJs7GkdQolqOHns9k6v1UjCUb_LqTFVjZM-kc3TbNGI/edit) that might assist you.

Thanks again for filing for TAG review and for providing an Explainer!

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/187#issuecomment-323384320