3 ms·
Could you elaborate on the bugs in SVG? Are there any usability issues beyond the bugs? I tried some cursory googling 'why not to use svg', 'svg bugs', etc and
by stinky613 9y ago
Could you elaborate on the bugs in SVG? Are there any usability issues beyond the bugs? I tried some cursory googling 'why not to use svg', 'svg bugs', etc and didn't really find any common/recurring.
- tyingq 9y agoI mentioned the issue with gradients in another comment. There's also a good presentation here on other issues: http://slides.com/sarasoueidan/tips-for-avoiding-common-svg-pitfalls http://slides.com/sarasoueidan/tips-for-avoiding-common-svg-... Perhaps not all "bugs", but unexpected anyway.
- spiralganglion 9y agoHistorically, the SVG-related systems in most browsers haven't seen a lot of love, so it's lagged behind other web technologies. This seems to be getting better — I know Safari just landed a nice 3x performance improvement to one of the SVG filters. Here's a handful of issues that I still encounter, due to cross-browser differences. * You can't use the full range of CSS3 colors. * You can't set certain style properties via CSS (requiring the use of attributes). * You can't use self-closing tags for certain elements. * Differing behaviour when you set an attribute to "null" (which is fine, it's just a gotcha) SVG performance also varies wildly, more so than JS perf, HTML DOM perf, or CSS perf. This seems to correlate with the visual quality of the rendered result — Chrome is the fastest but has excessive smoothing, poor sampling of scaled images, etc; Safari is the slowest but produces the cleanest result.
- abritinthebay 9y agoOne of the most annoying bugs is Chrome’s utterly broken implementation of the Use element for SVG. That’s one of many, but it’s one they’ve know about for years.