- From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Apr 2019 05:24:48 +0000
- To: public-svg-issues@w3.org
@BigBadaboom that is a good point. What holds you up to still add SVG features to that document? Or the renderer to be a full-SVG-renderer able to process this SVG file? On the other hand, the MIME type maybe a way to enforce an SVG parser/renderer to go to a more strict mode **if** it would have one. It requires the whole industry to agree to fall back to the strict mode and not simply use the full-SVG parser to be effective though. That said, SVG used in an `<img>` element in HTML, `<image>` in SVG or as CSS image already has a lot of requirements and restrictions that make it suitable to use the SVG as avatar on social platforms. The industry already agreed and implemented those restrictions specifically aiming the privacy and tracking concerns of social media platforms _and_ the users and we _still_ are not allowed to use SVG images. SVG Native is not adding more security IMO. -- GitHub Notification of comment by dirkschulze Please view or discuss this issue at https://github.com/w3c/svgwg/issues/664#issuecomment-484771319 using your GitHub account
Received on Friday, 19 April 2019 05:24:49 UTC