[csswg-drafts] [resize-observer] Add offset position to rects (#3550)

gregwhitworth has just created a new issue for https://github.com/w3c/csswg-drafts:

== [resize-observer] Add offset position to rects ==
The CSS Working Group just discussed `Which box information should we pass to the callback`.

&lt;dael> smfr: Also odd API only returns sizes. I'd like rect for all of these and they should be relative to top left of border box<br>
&lt;dael> smfr: To resolve what changed is you return all rectangles and an enum to say which changed<br>
&lt;dael> astearns: Would be which changed, it's which of them changed<br>
&lt;dael> smfr: Yes<br>
&lt;dael> gregwhitworth: Not opposed to having results return in other static areas. THis was just an issue for the resize observer. Not sure if you want to expose in CSSOM or whatever.<br>
&lt;dael> gregwhitworth: smfr are you saying youw ant shape is what would be return from getClietnRects?  I had talked with Alec (sp?) that we'd have getBoundingClientRects be what's returned for these boxes. But we said it's about size change not position<br>
&lt;dael> smfr: These rect are in local coordinates. Which I think is fine. This API shouldn't be able abspos or client pos. If you're giving size of contents I'd also like offset from top left. That seems natural and cheap to compute<br>
&lt;dael> gregwhitworth: Makes sense. Ic an open that issue. Are we providing for sake or is that a thing authors want commonly? That they want to check the offset<br>
&lt;dael> smfr: I would imagine the users care about fitting thigns inside. I think it's about size and not position

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3550 using your GitHub account

Received on Wednesday, 23 January 2019 18:02:45 UTC