- From: Jarek Foksa via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Apr 2017 13:07:37 +0000
- To: public-svg-issues@w3.org
@AmeliaBR >From my testing `pathElement.getBBox()` returns a proper [geometric minimum bounding box](https://en.wikipedia.org/wiki/Minimum_bounding_box) in the user space. I.e. the smallest possible rectangle inside which the path fits in, computed using raw path data (without applying any transforms). That gist is demonstrating the problem I was talking about earlier - you can't just take a bounding box in the user space and transform it's coordinates to some other space - this will produce a bounding box of another bounding box which is not useful and wrong if you stick to the mathematical definition. Making `getScreenBBox()` behave this way would in my opinion be inconsistent with how `getBBox()` works and redundant because there is already `element.getScreenBBox()` which does it. -- GitHub Notification of comment by jarek-foksa Please view or discuss this issue at https://github.com/w3c/svgwg/issues/76#issuecomment-291137262 using your GitHub account
Received on Monday, 3 April 2017 13:07:43 UTC