How does remove unused SVG namespaces decide what to drop?

It scans element prefixes and attribute prefixes. A xmlns:foo with no foo:* usage is removed. The SVG xmlns stays.

Will xlink:href survive unused-namespace cleanup?

If any xlink: attribute exists, xmlns:xlink is kept. Otherwise it is dropped.

This pass is prefix-usage based. The Inkscape/sodipodi/Sketch pages target those exporters even if you still want a surgical list.

Browsers ignore unused xmlns. Removing them only shrinks markup.

FAQ

Quick answers

How does remove unused SVG namespaces decide what to drop?: It scans element prefixes and attribute prefixes. A xmlns:foo with no foo:* usage is removed. The SVG xmlns stays.
Will xlink:href survive unused-namespace cleanup?: If any xlink: attribute exists, xmlns:xlink is kept. Otherwise it is dropped.
Is this safer than removing Inkscape namespaces by name?: This pass is prefix-usage based. The Inkscape/sodipodi/Sketch pages target those exporters even if you still want a surgical list.
Do unused namespaces change rendering?: Browsers ignore unused xmlns. Removing them only shrinks markup.

Source

Ready

React component

React Native (react-native-svg)

PNG export · 2× for retina

0 B