Event Listeners in Backbone View are not being added to objects in the DOM?

In initialize you write el = $('. ContainerOuter') But Backbone. Js processes events before initialize —meaning that it's already bound those events to a different el (which you should see in the DOM as a lonely div ) You can hack this by overriding make the function that's used to create el : make: -> $('.

ContainerOuter')0.

In initialize, you write @el = $('. ContainerOuter') But Backbone. Js processes events before initialize—meaning that it's already bound those events to a different @el (which you should see in the DOM as a lonely div).

You can hack this by overriding make, the function that's used to create @el: make: -> $('. ContainerOuter')0.

2 Relax; everything is behaving as it should. Backbone uses jQuery's delegate, for two reasons: First, a bind has to be done every time the target element is created. Second, delegate is more efficient.

A single click delegate on containerOuter can listen for click events on thousands of child elements, without cluttering the DOM with extra listeners. – Trevor Burnham Sep 17 at 21:59 1 (That comment was written in response to one that was subsequently deleted, asking why the events seemed—from Chrome's Dev Tools—to be bound to the . ContainerOuter element.) – Trevor Burnham Sep 18 at 1:47.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.