Paul Falgout

While doing some region work, I definitely think it's time to readdress this

It's possible this should just wait for v5 since the behavior will be moderately different for nondestructive views.. But we could introduce it, documenting the upcoming breaking change, so that...

Merge conflicts are going to be a reality I think. Otherwise we get into the situation where we have an urgent bug that needs fixing but we can't release because...

I think it makes sense to merge relevant docs directly into master because it's the only way we're going to be able to push them outside of rolling a release...

Could we just add esfix to a precommit hook or something?

I'm not sure where this goes, but we need to add something about the stuff that gets merged into master should get merged back into `next` as well

I'm not entirely sure what a great fix for this is going to be. An easy one is to make your selectors more specific.. such as this for the fiddle:...

I am working on a blog post about this issue as it relates to events/triggers.. (by that I mean I wrote a title) so this is interesting context.. but @scott-w...

So this has an open PR scheduled for v4.0, but I'm leaning towards wanting to hold off on this. I think this is going to bite people (@JSteunou) who currently...

FWIW I don't think `triggerMethod` needs to check if it's a function either. Right now ```js View.extend({ onRender: 1 }); ``` will work just fine. Might as well let `onRender.apply`...