At first my reaction is that I'm against this, **but** we need to keep it because of the way we implement Behaviors right now. Our Views' triggerMethods are wrapped when they have Behaviors, so we **need** to ensure that we call the view's when possible. This is actually a bugfix.

Eventually this will be abstracted to a `triggerMethodOn` method.