- From: Dirk Schulze <dschulze@adobe.com>
- Date: Sat, 5 May 2018 14:10:11 +0000
- To: Bogdan Brinza <bbrinza@microsoft.com>
- CC: www-svg <www-svg@w3.org>
- Message-ID: <4587A720-AE3C-4AA7-BC18-F19FE3AF209B@adobe.com>
Hi all, If there is time, I’d like to add: [css-masking-1] stroke-bounding-box and non-scaling-stroke https://github.com/w3c/fxtf-drafts/issues/279 This affects more than just CSS Masking but getBBox(), Fill & Stroke and CSS Transforms as well and block implementation. Open questions are: * Use tight stroke bounding box which may be heavily depending on the graphics library. * Use an algorithm that is based on heuristics but give reliable results. * If we use heuristics, how do we handle non-scaling-stroke. Greetings, Dirk On 4. May 2018, at 01:42, Bogdan Brinza <bbrinza@microsoft.com<mailto:bbrinza@microsoft.com>> wrote: Hello, Below is the list of GitHub issues labelled with “Agenda+” we hope to discuss on the call next Monday: • Clarify hit testing behavior of <foreignObject>: https://github.com/w3c/svgwg/issues/427 • Do we really need not to reflect additional enum values in SVG 2: https://github.com/w3c/svgwg/issues/424 • What should happen if you try to set an out of range value on an enum in the DOM: https://github.com/w3c/svgwg/issues/423 • Clarify relation of isPointInFill and pointer-events: https://github.com/w3c/svgwg/issues/416 • dur attribute should permit leading .: https://github.com/w3c/svgwg/issues/394 Hope to see everybody on the call! I’ll use this opportunity to remind about the next call after that and reiterate the plan to discuss and remove features at risk. Please see attached message sent earlier. <Mail Attachment.eml>
Received on Saturday, 5 May 2018 14:10:44 UTC