@jaffathecake Got it. I hope by piggy backing on node.cloneNode(true) for the initial clone it would be less problematic than <svg:use> a <svg:foreignObject>. That was a memorable bug from fuzzying team 😅.
The first option is not ergonomic IMO.
The last option is ... creative, not sure if it is achievable given the level of effort.
Speak of, why not generalize the light-DOM-deep-clone behavior? Maybe we should ship a `<html:clonefrom>` element instead 😝?
Gregory's Server
@jaffathecake Got it. I hope by piggy backing on node.cloneNode(true) for the initial clone it would be less problematic than <svg:use> a <svg:foreignObject>. That was a memorable bug from fuzzying team 😅.
The first option is not ergonomic IMO.
The last option is ... creative, not sure if it is achievable given the level of effort.
Speak of, why not generalize the light-DOM-deep-clone behavior? Maybe we should ship a `<html:clonefrom>` element instead 😝?