I'm making some inquiries. It looks like the old code just ended up setting "position" to 0 when an object was assigned, while the new code (correctly per spec) throws. The real bug is assigning an object to a non-object-valued property...