mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-30 11:37:16 +02:00
34ec33d71c
We were failing to discriminate between DOM removals happening to SVG elements cloned as part of an SVG use element instantiation. When a "use source" element is removed, all clones of that source must be updated to reflect the change. But when a "use clone" element is removed, that's fine. This was causing the surprising disappearance of use element subtrees, seen for example on https://cal.com/
5 lines
110 B
Plaintext
5 lines
110 B
Plaintext
use1 > [object SVGSVGElement] foo
|
|
use2 > [object SVGSVGElement] foo
|
|
no use1
|
|
use2 > [object SVGSVGElement] foo
|