Paolo Fulgoni

Here is another use case which would benefit from this requested feature: We run end-to-end tests on an ECS Task with Fargate. If, for a bug, a test gets stuck,...

The namespace setter you proposed would be great, but I'm afraid it wouldn't work. I'm not a namespace expert at all, but I found that merely setting the `xmlns` attribute...

That could be a good idea! As far as I understood, both elements and attributes can "belong" to a namespace. So a new API for attribute could be useful too....

Sorry for not being clear... Please consider this SVG image as example: http://dev.w3.org/SVG/tools/svgweb/samples/svg-files/car.svg (cool, isn't it?) The main `` tag "declares" several namespaces with the associated prefix. Let's consider `inkscape`...

Yes, `NameList` seems to be something not really used in DOM implementations. For example, it is obsolete in Gecko: https://developer.mozilla.org/en/docs/Web/API/NameList. Anyway, it seems that `createElementNS` and `createAttributeNS` methods are the...

No problem, of course. I can create the namespace-aware elements anyway with the jQuery style: ``` $("") ``` Thanks for considering the proposal.

class diagram

As I wrote on Gitter yesterday, I was thinking about extracting the SVG manipulation part in a separate library too, and make it fully netstandard compliant. My original idea was...

@wieslawsoltes do you think you could achieve the full rendering functionality of vvvv/Svg with your Svg.Skia implementation?

So creating the new svg parsing/manipulation library seems a good idea for many reasons. If vvvv/Svg will use such libary, should it maintain backward compatibility? I mean, splitting the library...