Nested transitions compete for ownership.

[mbostock]

Consider the following:

var foo = d3.transition("foo");
foo.selectAll("bar").attr("attr1", "value1");
foo.select("bar.baz").attr("attr2", "value2");

The second select creates a new transition which clobbers the previous selectAll's transition.

[mbostock]

A really easy way to fix this is to use the existing d3_transitionInheritId mechanism.

[mbostock]

Another idea is to set a transition ID per event lifecycle. That could potentially lead to conflicts, though.

[mbostock]

Fixed in 2.0.0.