Timeline for Event fired by a dynamically created component does not get caught
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2017 at 14:08 | comment | added | Eric | Ran into this as well. After several hours of trials finally found this thread. Thanks @ChrisWoolcott - for finding this bug and posting the answer. | |
| Sep 8, 2017 at 15:07 | comment | added | Willem Mulder | September, and still not fixed... Spent way too much time on this. | |
| Mar 9, 2017 at 9:57 | comment | added | Keith C | Rather depressing that I just hit this - including having to remove the name - in March 2017. | |
| Oct 26, 2016 at 14:56 | comment | added | Chris Woolcott | Depending on the application structure, stopPropagation() could be used to prevent other components handling the same event if required. | |
| Sep 21, 2016 at 2:05 | comment | added | Scott Morrison | This is fine, if you only have one instance but what if you have multiple instances and only want one of the instances to handle the event that was fired without the other instances picking it up? | |
| Mar 23, 2016 at 23:47 | review | Late answers | |||
| Mar 23, 2016 at 23:50 | |||||
| Mar 23, 2016 at 23:31 | history | edited | martin | CC BY-SA 3.0 |
code formatting
|
| Mar 23, 2016 at 23:30 | review | First posts | |||
| Mar 23, 2016 at 23:31 | |||||
| Mar 23, 2016 at 23:30 | history | answered | Chris Woolcott | CC BY-SA 3.0 |