fixed EventedMind/iron-router#606 , UI.body.events #13#21
fixed EventedMind/iron-router#606 , UI.body.events #13#21webcrx wants to merge 1 commit intocmather:masterfrom
Conversation
|
Hi @webcrx, Thanks for this. Someone else discovered this as a solution a little while back also. I need to understand how/why it works. It seems strange that any layout would need to inherit from UI.body vs. just being plugged into UI.body. I also mechanically don't understand why it works. I'm hesitant to duct tape symptoms even if it seemingly fixes the problem. But haven't had time to dive in. Maybe the fastest thing is to ask Core. @dgreensp: What is the correct way to render a component as a child of the UI.body component such that UI.body event handlers respond to events from child components? I thought passing the UI.body component as a parma to UI.render was enough, but it does not seem to work. If it's not a trivial answer and you'd like a reproduction please let me know and happy to share. |
|
@dgreensp: if you get a chance I referenced you in a question above but didn't get your github handle right the first time :). Asking about rendering components as children of UI.body and making sure event handlers still fire on UI.body. |
|
I posted that because only with that fix (for now) i can use global event in all templates without copy code :) |
|
UI.body... is kind of a misnomer. Avi asked me about this recently, so UI.body is a component that renders the concatenation of the I think we should rename UI.body to UI.main, and then make a new UI.body, On Fri, May 16, 2014 at 8:23 AM, Chris Mather notifications@github.comwrote:
|
3 participants
i need this to work with UI.body