Timeline for Locker Service DOM accessibility when action invoked via method
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 3, 2017 at 20:57 | vote | accept | dsharrison | ||
| Jan 3, 2017 at 20:57 | answer | added | dsharrison | timeline score: 0 | |
| Nov 30, 2016 at 10:16 | answer | added | Doug Chasman | timeline score: 2 | |
| Nov 30, 2016 at 6:15 | history | tweeted | twitter.com/StackSalesforce/status/803844841226596352 | ||
| Nov 30, 2016 at 3:35 | comment | added | dsharrison | @MohithShrivastava just added a gist. I stripped a lot of stuff out from our actual use case to just highlight the issue we are seeing but let me know if you have any questions about why things are set up the way they are or if you need more info. | |
| Nov 30, 2016 at 3:34 | history | edited | dsharrison | CC BY-SA 3.0 |
Add gist with reduced test case.
|
| Nov 30, 2016 at 3:19 | comment | added | dsharrison | I'll put the gist together and yes, disabling locker service restores the intended functionality. | |
| Nov 30, 2016 at 3:14 | comment | added | Mohith Shrivastava | would love to see reduced gist to further investigate ? Also does it work with locker disabled to call it as a locker issue ? | |
| Nov 30, 2016 at 3:14 | history | edited | Mohith Shrivastava | CC BY-SA 3.0 |
deleted 18 characters in body
|
| Nov 30, 2016 at 3:12 | history | asked | dsharrison | CC BY-SA 3.0 |