- From: Dirk Schulze <dschulze@adobe.com>
- Date: Fri, 23 Nov 2018 06:11:23 +0000
- To: Domenico Strazzullo <strazzullo.domenico@gmail.com>
- CC: www-svg <www-svg@w3.org>, "w3c-svg-wg@w3.org" <w3c-svg-wg@w3.org>
Hi Domenico Strazzullo, I am sorry for not correcting the minutes. Resolution 7 applies and replaces resolution 6. Resolution 8 clarifies the behavior for getScreenCTM() and getCTM(). Greetings, Dirk ________________________________________ From: Domenico Strazzullo <strazzullo.domenico@gmail.com> Sent: Thursday, November 22, 2018 11:42:17 AM To: Dirk Schulze Cc: www-svg; w3c-svg-wg@w3.org Subject: Re: Minutes, SVG WG teleconference, 12 November 2018 Points 6 and 7 are the same (?), but their sentences in parenthesis are opposite. Domenico Strazzullo On Mon, Nov 12, 2018 at 11:07 PM Dirk Schulze <dschulze@adobe.com<mailto:dschulze@adobe.com>> wrote: Hi all, Here are the meeting minuted of the call on 2018-11-12: https://www.w3.org/2018/11/12-svg-minutes.html Summary of Resolutions 1. SVG WG ok with updated CR of Geometry Interfaces. 2. <foreignObject> in referenced subtrees of the <use> element would not be considered for the shadow tree 3. Image pixel data isn't used for hit testing 4. Replace DOMPoint with DOMPoint2DInit with SetMatrix() and createSVGTransformFromMatrix() 5. The host coordinate system is the furthest SVG viewport as defined in SVG 1.2 Tiny 6. Elements that "do not get rendered" may not correct the correct, expected value for methods that require calculating the geometry of an element. (Does not include getCTM() or getScreenCTM()) 7. Elements that "do not get rendered" may not correct the correct, expected value for methods that require calculating the geometry of an element. (Also includes getCTM() or getScreenCTM()) 8. getCTM(), getScreenCTM() return null in this situation, everything else throws a to-be-determined exception in this situation. Greetings, Dirk
Received on Friday, 23 November 2018 06:11:54 UTC