- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Nov 2018 15:41:48 +0000
- To: public-svg-issues@w3.org
Here 3 tests. Each test has 3 rectangles: 1. rect in `<defs>` section 2. rect with `display: none;` 3. normal rect for reference. **1. `getBBox()`** https://codepen.io/krit/pen/wQzPQj * Chrome, WebKit, Edge: **1.** and **3.** show the correct bounding box. **2.** has an SVGRect with all values set to `0`. * Firefox, `NS_ERROR` for **1.** and **2.**. **3.** shows the correct bounding box. **2. `isPointInFill()`** https://codepen.io/krit/pen/xQEpep * Chrome, WebKit: **1.** and **3.** return `true`. **2.** returns `false`. * Edge and Firefox do not support `isPointInFill()`. **3. `isPointInStroke()`** https://codepen.io/krit/pen/xQEpep * Chrome, WebKit: **1.** and **3.** return `true`. **2.** returns `false`. * Edge and Firefox do not support `isPointInStroke()`. In the WG call, interoperability between new and old functions were a concern as well as backwards compatibility if we require functions to throw. As seen, at least backwards compatibility might not be a concern since Firefox does throw already if `display: none;`. -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/svgwg/issues/456#issuecomment-437680676 using your GitHub account
Received on Sunday, 11 November 2018 15:41:49 UTC