- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 25 Sep 2013 19:52:26 +0200
- To: "Robert O'Callahan" <robert@ocallahan.org>, "Henrik Andersson" <henke@henke37.cjb.net>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "Simon Fraser" <smfr@me.com>, "Dirk Schulze" <dschulze@adobe.com>, "www-style list" <www-style@w3.org>
On Wed, 25 Sep 2013 15:38:33 +0200, Henrik Andersson <henke@henke37.cjb.net> wrote: > Simon Pieters skriver: >> I don't follow. What's the use case for a movable rectangle? >> >> >>> Since we are on the topic of DOMRect, I'd like to request some utility >>> methods. >>> >>> First, a way to check if two DOMRects intersect and if so, a way to >>> find >>> the resulting intersection area. >>> >>> Second, a way to check if one DOMRect is fully contained inside another >>> DOMRect. >>> >>> Third and finally, a way to check if a DOMPoint/DOMPointLiteral is >>> contained in the DOMRect. >> >> Use cases for these? >> >>> These are very handy methods to have in a rectangle abstraction and are >>> easy to implement. Lets not force content authors to implement this. >>> Better have it right in the interface. >> > > I do not have any use cases. At least nothing better than "people will > want a generic Rectangle class". OK. Do we have any data about how people use utility methods in other languages/libraries? The canvas 2d API seems like something we can study... -- Simon Pieters Opera Software
Received on Wednesday, 25 September 2013 17:52:58 UTC