Another big thing we're missing is support for the <use/> element in
SVG-edit. Looking further at your source it has a lot of <use>s so
none of those show up in SVG-edit at the moment.
The issue with supporting elements and attributes in SVG-edit means
that we have to be very careful about security considerations. For
instance, <use> elements can refer to other files - we don't want to
allow that in SVG-edit because it might bring in elements from other
files (though I think there are cross-domain restrictions on <use>'s
xlink:href, I'm not entirely sure.
Furthermore, <use> elements could be resized, etc - not sure how this
might be impacted on the UI (can <use> be selected, moved, resized,
deleted, etc? I think the answer is 'yes' to all of those, but each
time we add support for something in SVG-edit we need to carefully
think about it.
(As an anecdotal story, I just recently found out that when I added
support in SVG-edit for the <title> element that a user could cause
invalid XML or inject <script> inside. I hope I fixed this last