" if I have a listener on both the original and a clone, they both fire if I click the clone. That sounds like a feature, come to think of it. Will research eventually."
Eventually: listeners fire on original and clone when clone is clicked, but in both cases the -target of the event is the clone. App code can use that fact to disambiguate. Yay.
ps. ^^^ Gonna leave SVG support as is and go find that lifecycle bug, but if anyone wants to play with SVG from mxWeb I can jump back in as soon as any speed bumps are hit. 🪂
Well, dynamic SVG sub-node remove is OK. All the same code as for HTML tags, might even be able to merge.
The current example out of the box uses the <use> tag to clone an SVG. Very cool, but if I have a listener on both the original and a clone, they both fire if I click the clone. That sounds like a feature, come to think of it. Will research eventually.
Putting SVG aside now to get to that lifecycle bug in which the engine tries to act on some dead references.