Manuel Dell'Elce

For the time being manual Backbone detection can be used: https://github.com/Maluen/Backbone-Debugger#backbone-detection

I'm gonna do some debugging with an app using Layoutmanager and will report.

Views are removed, but aren't displayed as such in Backbone-Debugger. Backbone-Debugger considers a view removed when its "remove" method has been called, as per Backbone.View interface. Backbone Layoutmanager however, removes...

Note: when removing a non-layout view directly via its "removeView" method, then the subviews are removed _correctly_ by using the remove method: ``` javascript // Use this to remove Views,...

So what if a subview has a custom "remove" method? Won't it be called when doing "mylayout.remove()"? Probably I'm missing something, otherwise an issue could be opened on the LayoutManager...

@arfa Nice suggestions, any chance you could open an issue on the LayoutManager repository for adding the explicit remove call to subviews when removing a Layout?

We have just to make sure to spot subviews addition and removal on the fly. This could be done by monitoring the DOM for element additions and removals, checking what...

> and wouldn't be compatible with detached views and Minionette's Regions, which swap views in and out of the DOM without removing them. Even when detached, I still consider these...

We can't ask any user to change their Backbone applications, so that's just not feasible, we'll have to monitor the DOM to find additions like we'll have to do to...

I see, the main project philosophy however is to strive to make it work everywhere with no modifications at all (yes that's not written anywhere), so what you are proposing...