Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'kendoRendered' event is received only by the last rendered widget's parents #500

Closed
wants to merge 1 commit into from

Conversation

AkosLukacs
Copy link

$emit dispatches the event "upwards", so if the last rendered widget is deep in some tree structure, any listeners that are not parent of that widget, won't get kendoRendered event at all.
Broadcasting from $rootscope solves this.

`$emit` dispatches the event "upwards", so if the last rendered widget is deep in some tree structure, any listeners that are not parent of that widget, won't get `kendoRendered` event at all. Broadcasting from rootscope solves this.
@AkosLukacs
Copy link
Author

A demonstration is here: http://plnkr.co/edit/Q2wq0KILDC7jSfjAhInx?p=preview
(watch the console)
Expected behaviour: you can listen for 'kendoRendered' anywhere, and actually get the event
Actual behaviour: only the parent(s) of the last rendered widget get the event
right now, only 'otherCtrl' receives the event
if I remove 'otherTreeView' from the dom, 'dummyCtrl' does receive the event, but the other does not

@petyosi petyosi self-assigned this Oct 30, 2015
@petyosi
Copy link
Contributor

petyosi commented Jul 15, 2016

the kendoRendered event was a bad idea, in general. It took us a while to figure it out, though. One will benefit much more from a widget init event — #1226. The implementation itself is quite trivial, but we need to update 70+ API reference pages so that the event propagates to the server-side wrappers.

@petyosi petyosi closed this Jul 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants