Timeline for Locker Service: How to get the event target?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2017 at 0:10 | comment | added | Ravi Jayaramappa | @joshuadelange This seems to be fixed now. I have verified it in the Spring 17 release. Here's the component markup I used gist.github.com/anonymous/fcf2e7aee13d3d9f8cc2e125c5c9174b Please let us know if its still a problem. A git gist of your code showing sample data in v.results would be useful. | |
| Nov 16, 2016 at 14:55 | comment | added | joshuadelange | @DougChasman Thank you Doug! Were you able to hear anything back from them in the last week? | |
| Nov 8, 2016 at 15:14 | history | edited | Doug Chasman | CC BY-SA 3.0 |
added 40 characters in body
|
| Nov 8, 2016 at 15:14 | comment | added | Doug Chasman | Exactly - opened W-3458193 to track this and the Locker team is investigating now | |
| Nov 8, 2016 at 15:10 | comment | added | Lucas Ennouchi | So, you mean that his component is losing the ownership of the DOM element because of the aura:iteration which kind of "steals" it ? | |
| Nov 8, 2016 at 14:58 | history | answered | Doug Chasman | CC BY-SA 3.0 |