Skip to content
This repository has been archived by the owner on May 15, 2023. It is now read-only.

Initialize dom element event received after setChildren #13

Open
MinaXenou opened this issue Aug 27, 2016 · 2 comments
Open

Initialize dom element event received after setChildren #13

MinaXenou opened this issue Aug 27, 2016 · 2 comments

Comments

@MinaXenou
Copy link
Contributor

This is a race condition issue. The problem is that,many times, the "childrenChanged" Event is received even before the node placeholding event. This has as a result that the node related to the childrenChanged Event is not yet stored in the nodemap and an "Error : could not find node" is thrown. As I can see the most of the errors are related to that kind of race conditions. Maybe one possible fix could be to use here also a queue with events related to a node which are not executed before the node initializations. Once the node is initialized (Registered in the nodemap) the execution of all the related events is fired.

@MinaXenou
Copy link
Contributor Author

MinaXenou commented Aug 27, 2016

2016-08-27 18_58_24-myvm running - oracle vm virtualbox

This is an example of two nodes ( 3 and 4) that receive a childrenchanged event but are not placeholded nor initilized yet (you can see the placeholding and initialization events happening later for both nodes, I have also printed timestamps of the events)

@soney
Copy link
Owner

soney commented Aug 27, 2016

@MinaXenou hmm, does this happen in the code that emits the events as well?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants