W3C publishes a corrected SVG 2 Candidate Recommendation Snapshot aimed at browser interoperability

The dev.to post that covered the release for icon teams puts it plainly. The specification defines how something should work, and browser implementations determine how reliably it works in practice ^[14]. A Candidate Recommendation Snapshot is text that engine teams implement against. Publishing it did not make every SVG 2 feature available in every browser ^[3]. Corrections aimed at interoperability ^[1] cut down the places where two engines can read the same sentence two different ways. Users see the difference only after engines ship code that follows the corrected text ^[14].

According to the post, SVG 2 is meant to modernize the specification and clarify existing behavior. It does not set out to reinvent vector graphics ^[4]. That matters for how teams should treat the geometry change. Defining dimensions and positions as CSS properties moves more of an icon's shape under stylesheet control, but the post adds "where supported" ^[6]. It also says support for each property has to be checked before production use ^[7].

The reference syntax is the cheapest change to act on. Older markup reads `<use xlink:href="#search-icon" />`. SVG 2 markup can drop the namespace prefix and write `<use href="#search-icon" />` ^[8]. It is one of the few spec changes that find-and-replace can mostly handle. I think a library can make the switch in its next routine release, once it has confirmed that the browsers it targets accept the plain attribute ^[7].

Reuse carries the most risk for icon systems. SVG 2 refines the rules for `<symbol>` and `<use>`, covering how reused elements are sized, styled and rendered ^[9]. In an icon system the same asset may appear in many different contexts ^[13]. A sizing disagreement between engines therefore shows up at every reference to that symbol. The post says the refinements aim at consistency, and that actual behavior still depends on browser implementations ^[15].

For conformance data, the post points to the Web Platform Tests results for SVG. It calls them a starting point and says application-specific testing remains important ^[11]. Treat a pass rate like any benchmark table: it describes the test suite's workload. It transfers to an icon library only if the suite covers the same symbol sizing and stylesheet rules the library depends on, in the browsers its users actually run ^[11].

None of this forces a rewrite. The post's advice for icon libraries is that predictability is often worth more than the newest available syntax ^[12].