SVG.js

FAQ

Two SVG's are generated when I initialize SVG.js. Is that a bug?

No, this is most definitely not a bug. SVG.js creates one invisible <svg> to calculate path data, bounding boxes for invisible elements and so on.

We don't want to modify the documents created by users because that could result in unwanted effects. That's why we create this one extra document for us to work on. Note that we only create one extra document, no matter how many SVG's you initialize.

We could implement this functionality ourselves to avoid the creation of this little "parser" as we call it. But that would result in a lot of extra code, and it would affect performance.

Can SVG.js run on Node.js?

Yes, you can! Have a look at github.com/svgdotjs/svgdom.

How can I modify an element that already exists in the dom?

There are many ways of referencing existing elements. Take a look at the referencing section to get elements by id, using CSS selectors, using Zepto or jQuery, ...

I need help getting something to work...

The best place to ask questions of this kind is Stack Overflow. We even have a dedicated tag.
We also have a chat at gitter which you can find under https://gitter.im/svgdotjs/svg.js where you can find quick help.

I found a bug. Where do I report it?

Thanks for taking the time to report it! You can create an issue on Github and we will attend to it as soon as possible.

Where can I find tutorials?

CSS-Tricks has some good ones and more will be coming soon!

How do I contribute or fix something in the docs?

In the contributing section, you'll find all information that is needed.

Fork me on GitHub