Jeremy Darling

That does make it even more odd. So basically deliverChangeRecords is supposed to deliver only associated (already being observed) changes to the specific handler... Yep I not only think this...

Found more info and got a response on the list :) http://wiki.ecmascript.org/doku.php?id=harmony:observe Reading through the New Internal Objects, Properties, and Algorithms and Modifications to Existsing Algorithms sections makes the change...

Completely agree, I can't come up with a valid usecase for only delivering messages to one handler and not the others, but who am I to argue :). Guess maybe...

Since Object.observe has its own hackish way to override setImmediate the two are probably colliding. I'm not sure there is a way to actually check to see if setImmediate is...

Can you post a simple example that this breaks with so I can create a test case from it. Also the PR you submitted utilizes bind, as that isn't supported...

Excellent, I'll take a look and see what I can put together, will take me a few days at minimum as I'm buried in real work and home activities.

Tests for Array, Object, and Observable are now in place. Tests are segmented on functionality (do Array's work, do Object's work, etc) and named as tests..js so they group well...