In Firefox 35, the transformations are applied to the canvas, and so are changed when the canvas size changes (this is the approach we resolved to take, to make it similar to a transform on the root element). In IE 11, the transformations are applied within the viewBox coordinates, and so are independent of canvas size (this is how it worked under the old draft test). In Chrome 40, things are wonky altogether (caching issues? images flicker in and out); the effect is independent of canvas size if the viewBox is also declared in the fragment, but not when using the default viewBox from the file--in this case I'm not sure what's happening, since it doesn't match FF or IE. Opera doesn't have the wonky repaint issues, but is otherwise the same as Chrome (the figure labelled "transformation" ends up with only whitespace on screen).