Timeline for Winter 16 canvas iframe behavior change
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2015 at 14:31 | vote | accept | Victor | ||
| Oct 7, 2015 at 14:28 | answer | added | Victor | timeline score: 2 | |
| Oct 7, 2015 at 14:24 | comment | added | Victor | Hi Ronnie, they responded that it was intended change and works as designed, though they also said that created internal doc issue to update release notes documentation regarding these changes (no deadline for this - I guess after release that will be right in time :) ). | |
| Oct 7, 2015 at 9:27 | comment | added | Ronnie | Victor, have you heard anything more from SF regarding the change in value of targetOrigin, was this an intended change? We have a case with SF but the response has been slow. | |
| Sep 30, 2015 at 22:08 | comment | added | Victor | Update from SF: introduction of new iframe is "as designed" behavior (related to Lightning Experience and Salesforce 1) that was just missed in release notes document (at least the fact it affects Salesforce classic). Waiting for clarifications about "targetOrigin" behavior change - it's not clear for now if it's also "as designed" behavior that is not described in release notes or an issue that will be fixed (now targetOrigin is referencing outer iframe, not visualforce page that contains canvas - it can't be used for cross domain communication with visualforce page). | |
| Sep 29, 2015 at 13:32 | comment | added | Victor | window.parent.window.parent.postMessage won't work because targetOrigin has not correct value - not the URL of page that holds canvas, but URL of outer iframe | |
| Sep 28, 2015 at 23:26 | comment | added | Heyflynn | the problem seems to be with the winter'16 adding an additional iframe for canvas apps. the parent.postMessage only refers to the parent iframe now. per-winter'16 it references the parent window you want to post messages to. you'll notice window.parent.window.parent.postMessage works | |
| Sep 28, 2015 at 22:21 | comment | added | Heyflynn | having the same issue since na1 was updated this weekend with winter'16 none of our sforce interactions seems to be working. | |
| Sep 28, 2015 at 5:57 | comment | added | Amr Ibrahim | Seems like there are lots of Canvas issues with winter release success.salesforce.com/issues_view?id=a1p30000000TL1NAAW | |
| Sep 24, 2015 at 10:58 | history | edited | Victor | CC BY-SA 3.0 |
deleted 54 characters in body
|
| Sep 24, 2015 at 10:53 | comment | added | Victor | for now we're communicating SF support to clarify the details | |
| Sep 20, 2015 at 23:33 | comment | added | parxier | did you find a solution for this? we're experiencing similar problem. | |
| Sep 18, 2015 at 0:27 | history | tweeted | twitter.com/#!/StackSalesforce/status/644668930850750464 | ||
| Sep 17, 2015 at 17:03 | history | asked | Victor | CC BY-SA 3.0 |