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

Hey @atotic; we had a chance to discuss at today's F2F in Nice. Overall:

 * We're generally happy with this. Thanks for the detailed feedback on the questions.
 * Thanks for updating the explainer! Sample code truly is the lifeblood of good API design.
 * Is this going to be launched as an Origin Trial? If so, this seems to be in good shape.
 * Great to see [Web Platform Tests!](https://github.com/w3c/web-platform-tests/pull/6878)
 * The question about "previous value" keeps coming up in our discussion. (Mutation Observer, e.g., enables developers to request this data for some value types](https://dom.spec.whatwg.org/#dictdef-mutationobserverinit). Given that it's cheap to track this in the engine on an opt-in basis, it might be a helpful addition.
 * Regarding which value to deliver, what's the argument against reporting any/all of border/client/content sizes?
 * thanks for the update on IO vs. RO timings. They make sense.

-- 
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-332449968

Received on Wednesday, 27 September 2017 08:34:14 UTC