Consider this simple SVG file:
The easiest, standards-compliant way to differentiate between these is to use the SVG test suite provided by W3.org. This suite provides tests for use
structs that you can play with to determine compliance, among many others.
The problem is how your y
value is being parsed, which is causing your figure to translate out of the second frame, but only in some browsers. This is the correct, cross-browser way to specify the desired translation:
<use x:href="#img" clip-path="url(#walk0)"
transform="translate(0,80)"
/>
I would assume the dubious parsing with respect to the current clipping pane is a regression.