[FIX] (Canvas Render Concurrent Animation) Concurrent renders, from different protovis root panels, specially if each was using animations, would step on each others toes, by constantly stealing the canvas to the other vizualization.
Now, a visualization can only steal an already bound canvas if it is the first time that it is rendering on it. This breaks the continuous-stealing to each others' cycle.
When stealing, a visualization now orders the other to stop any existing animation.
[FIX] (Animation Control) The animation count field would, in some strange situations, reach to a negative value...
Alied to the fact that, currently, only one animation is supported at a time anyway,  the field was replaced by a test to the value of the current $transition field.
[FIX] (VML Animation FillStyle) Bug rendering animated fill styles (note that it's generally very slow to animate in VML, so this is kind of a cosmetic fix).
[FIX] (Animation shapeRadius shapeSize) These two important dot properties were not being animated.
[REM] (SVG Web) Removed SVG Web support. It's just feeling up space and making the code less maintainable.
[REM] (pv.renderer Batik) Removed branching code with tests for the "batik" renderer. These cases were resolved by creating overridable methods at appropriate places, so that the existing protovis-cgg.js can override (in CGG project).
[FIX] (examples tests) There were quite a few broken samples out there... There are still 2 breaking:
* examples/antibiotics/antibiotics-scatter.html - dots are not a correct positions
* tests/layout/treemap-margin.html - treemap should have a root padding/border.
[FIX] (radial gradient) Certain color operations were failing due to a bug in _cloneWithStops in that stops were lost in the way...
[FIX] (treemap paddings) padding{Left, Right, Top, Bottom) methods had broken compatibility with previously existing same named mark properties, in that the mark instance was no longer returned when setting a value. Also, the changes assumed that values would be functions, while previously they were numbers.
[FIX] (pv.Mark get property value) Regressioin on the ability to, from within the code of some property, obtain the value of the same named property of another mark/instance. The current code resulted in infinite recursion.
[FIX] (pv.Mark#instances) An old bug, from Mike Bostock's time (one of the few not introduced by me!), where trying to obtain a corresponding target scene would fail (source.index instead of source.parentIndex was being used). See tests/mark/panel-anchor2.html for an example.
[FIX] (pv.Mark#bind) Regression on setting properties with no value to null. There was no error being thrown, but it would generally not be done correctly.
[FIX] (pv.Mark#mouse) Another old one. Calling mouse from a place other than a mouse event handler would generally result in NaN mouse positions (see examples/eyes/eys.html).
[FIX] (pv.Panel canvas default size) Regression in initializing a root panel instance's height from its canvas' height. Would result in NaN height.