craftyjs/Crafty — pull request #635 by dkapadia (2013-12-03 22:31:08+00:00)
Title: Removing a component should actually remove the class from DOM

When using the DOM component, I found that removing a previously added component did not correctly remove the component from the DOM element's className.

The reason updateClass doesn't work as expected is that the RemoveComponent event is triggered before the component is actually removed from the entity. A different solution to the same problem would be to move that trigger further down in core.js, but that seemed like the sort of thing that could break other folks.