fixed EventedMind/iron-router#606 , UI.body.events #13
Conversation
| @@ -363,7 +363,9 @@ BlazeUIManager = function (router) { | |||
|
|
|||
| BlazeUIManager.prototype = { | |||
| render: function (props, parentComponent) { | |||
| this._component = UI.render(Layout.extend(props || {}), parentComponent || UI.body); | |||
| // Layout extending UI.body to get into the lookup chain for events | |||
| var bodyLayout = UI.body.extend(Layout); | |||
There was a problem hiding this comment.
Why does inheriting from UI.body cause UI.body events to be handled from the layout?
|
Excellent question - i started following the path on a click event. Honestly i cant really understand how the DomRange works by reading the source code. But as soon as you extend a Component its changing the behaviour of the DomRange structure. This Event delegating thing is really quite complex. I found a lot of hints that forced me to try this approach. Would be to much to share my whole chaotic path through DomRange. Would be great to hear something from someone quite experienced with the DomRange :/ if my testing enviroment could help you i can share it. |
|
|
This seems like the missing part, i dont think this has any bad side effects? What do you think @cmather?