Previously because drop called Keyboard.manager.manage(instance) it meant that the Keyboard.manager could never drop a keyboard. In theory this is fine, but in effect it meant that despite the fact that keyboards would have other managers assigned, they'd still be in the "instances" array of the Keyboard.manager forever. Now an instance can be dropped, effectively disabling it.
…ectors is not loaded yet, so it did not add the click events to the buttons
This is a faster way, because getPosition and setPosition already handle margins and stuff. That browser sniff for IE was not necessary either.
…ctions in the Assets object so do not need the operator (thanks Oskar)
IE6 doesn't like inserting `div`s in `table`s.
…, but the range from a negative number to a positive number.
IE and Opera return computed styles in the actual unit it that was used, while other browsers return pixels.
…preserve compatibility with 1.2 and will fix a bug with element positioned or floated without a fixed height.
In IE a non-injected Element would still have the `document` as parentNode. Using `getParent` solves that.