I don't think we should ever be using `@$el.on`. I'm pretty sure the only reason you'd ever need to do this is when you're listening to a DOM event that belongs to a child view's DOM. I think the DOM of different views should be siloed (they're not designed to bleed up to parent views); listen to the DOM event in its own view (should that be the ExpectedValueView in this case?), and then, if you need to handle that in the parent view, fire an event between child view and parent view, instead of between child DOM and parent view.