I have created Plunkers to demonstrate several issues.
First, selectors don't work correctly. My components use g.some-class as selector and those don't match anymore against a <g class="some-class">. When it's just a class selector .some-class it matches correctly. Fixed in 2.0.0-alpha.53
Second, when the selector doesn't work and there is a data binding defined, the error message is an InvalidCharacterError, because the parser tries to instantiate an @svg:g element with createElement to find the unknown property there. (Fixed in 2.0.0-alpha.49)
Third, even when everything is setup correctly and the component is instantiated, the actual child component's SVG isn't rendered (tested in Firefox, Chrome and Edge). There should be a black circle covering the red circle in the Plunker, it's there in the DOM, but wouldn't render. Fixed with a svg: prefix in the template
I have created Plunkers to demonstrate several issues.
First, selectors don't work correctly. My components useFixed in 2.0.0-alpha.53g.some-classas selector and those don't match anymore against a<g class="some-class">. When it's just a class selector.some-classit matches correctly.Second, when the selector doesn't work and there is a data binding defined, the error message is an InvalidCharacterError, because the parser tries to instantiate an(Fixed in 2.0.0-alpha.49)@svg:gelement withcreateElementto find the unknown property there.Third, even when everything is setup correctly and the component is instantiated, the actual child component's SVG isn't rendered (tested in Firefox, Chrome and Edge). There should be a black circle covering the red circle in the Plunker, it's there in the DOM, but wouldn't render.Fixed with asvg:prefix in the template