3 ms·
Yeah, USE tag is pretty buggy across browsers. Also, sometime you just need to inline SVG, for example if you want some icon path fill color to change on mouse
by tehno 9y ago
Yeah, USE tag is pretty buggy across browsers.
Also, sometime you just need to inline SVG, for example if you want some icon path fill color to change on mouse-over. Easy with inline SVG and CSS rule. Can't really do that (well) with external .svg.
- abritinthebay 9y agoWe actually had a nice system for that... but again: browser bugs :( Until browsers collectively get off their asses with SVG (most of these bugs are years old in their big trackers) using React for SVGs is a good workaround.
- Already__Taken 9y agoThey won't because it seems like they might as well forge ahead with CSS additions and drop an entirely separate renderer. That's what happened to the SVG Animations. Of course it's not like svg will get removed so Why fight it...
- abritinthebay 9y agoIt seems they stop work as soon as a feature hits SVG - CSS Animation, Canvas, WebGL... all have open SVG bugs. Some years old.
- josteink 9y ago> Easy with inline SVG and CSS rule. Can't really do that (well) with external .svg. I can see that easily solved much better, cleanly and not to mention lightweight with some CSS rather simple pre-processors in the build process. Or is your argument that you already have a (React-based) build-process and you'd want to align this with what you have, rather than creating something new and different along-side everything else (despite the result being suboptimal)?