Standalone SVG: Uncaught TypeError: node.getAttribute is not a function

[simonwidjaja]

I have a very basic standalone SVG that look like this:

<?xml version="1.0" encoding="utf-8" ?>
<svg version="1.1"
  id="stage"
  xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
  x="0px" y="0px" width="800px" height="500px" viewBox="0 0 800 500" xml:space="preserve">
<script xlink:href="svg.js"></script>
<script>
  var draw = SVG('stage')
  draw.image('car1.jpg', 800, 500);
</script>
</svg>

This approach works. And I can draw all kinds of native SVG elements (rect, circle etc.)
EXCEPT images are throwing the following error (they will be rendered properly though...)

Any ideas what is going wrong here?

[simonwidjaja]

Is the assumption that draw.image(...) should be fully supported in a pure/standalone SVG right? or are there any known issues? This is critical for my current project, so any hint is highly appreciated

[Fuzzyma]

I tried this and in my case the image is loading. It throws an error anyway. However - this only happens when using a standalone svg and when the image is not used in a pattern.

How it comes, that the image does not load in your case? The error does not impact the image loading itself

[simonwidjaja]

thanks for the feedback.
The image WILL BE loaded and displayed.
quote: "(they will be rendered properly though...)"
I just wanted to know if this is the wrong path I am taking and if there is a known issue. I don't like uncaught errors in my project ;) So I need to know if SVG.js is the right library for pure/standalone SVGs.

[Fuzzyma]

Its a bug which will be fixed in the next release. However it wont anything bad in your case

[simonwidjaja]

ok. so you are saying a try...catch and good to go? I will do that. Any update when we can roughly expect the next release?
I have heavily worked with SVG.js for the last two weeks and it's really fun. Keep up the great work!

[simonwidjaja]

I cannot even catch that error:

    var s = SVG('stage')
    s.circle(200,200)
    try {
      s.image('car1.jpg', 200, 200)
    }
    catch(err) {
      console.warn(err.toString())
    }

BTW: Is branch 3.0.0 already useful? I'm not implementing production code yet, so "beta" version would be fine...

[Fuzzyma]

The error is asyncronous and cant be catched by a syncronous try catch. The fix is released with 2.6.3.

In 3.0 i didnt see that error popping up. Its under development and will change rapidly in the next weaks (I already have some commits prepared which change a lot. However I need to test everything properly)

[simonwidjaja]

Oh just saw your fix/commit. Just replaced 2.6.2 with your 2.6.3. Works like a charm so far.
Thanks a lot! Looking forward to v3.