Basically the test is passing fine on my IE9 VMs and the individual tests are passing on the bots, but it appears that when everything is run together on the bots, that the tests fail.
What I believe is happening is that we're delaying the MutationEvents using window.setImmediate which is being polyfilled on IE9 to window.setTimeout(0) and running into a timing issue on slow machines with the test.
We should have a much better resolution once we get a proper setImmediate from dart2js.
BUG=
Review URL: https://codereview.chromium.org//12899003
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@20119 260f80e4-7a28-3924-810f-c04153c831b5
This only works for trees which are in the document, but when a tree is added to the document everything should just 'start working'.
This should work on all browsers (tested on Chrome, FF and IE9).
Not sure about performance impact on large trees and lots of bindings (balance between optimizing for lots of bindings or lots of elements, few bindings), but it should not impact anything if models are not used.
BUG=
Review URL: https://codereview.chromium.org//12754013
git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@20104 260f80e4-7a28-3924-810f-c04153c831b5
blois@google.com