Paul Falgout

I'm pretty sure I follow this, but a fiddle would help. This would require regions be setup after `initialize` as well. Personally I think that the ideal fix would be...

A pretty poor work around for the moment would be to: ```js regions() { this.setElement(this.el); return { region: '.selector' } } ```

ah the problem in the workaround is that `this.el` isn't set until the backbone.view constructor call.. well actually not until the `setElement` call :-) in this case.. but if you...

I don't think that #2 is correct. Perhaps a failing test could prove this, but just looking through the parse behavior, the view that gets attached to the view's behavior...

Yeah branch off of next and PR into it :-) You'll be happy to know that `next` is all node v4+ so all of the jsdom issues for testing should...

So looking at regions.. I think the main issue here is that regions ensure their element on the `show`, but now that there's a `getRegion` interface on the `View` it...

This will be resolved here https://github.com/marionettejs/backbone.marionette/issues/3294

Not resolved

As mentioned above https://github.com/marionettejs/backbone.marionette/pull/3244/commits/5603b0eb551cd43e9daaff69e0dc8a7682e4369b

I think the best way to approach this work might be to start testing the things with the least amount of dependencies. So I'd think we could make a utils...