Lightning for Gmail not working due the Sandboxed parent frame not allowing the alohaPage frame to load
Last updated 2018-03-23 ·Reference W-3992846 ·Reported By 4 users
Summary
If alohaPage has a parent from that is sandboxed, then it will not render properly. This is because the final step during initialization is to set the location of the frame to the VF page URL. We do this by calling contentWindow.location.replace() instead of setting frame.src directly. This is because calling replace() does not add a history entry and navigation back is smoother. However, when the parent frame is sandboxed (like in LAB and others, like msMail.app) then so is the alohaPage frame, and you are not allowed to call replace
Repro
Generic Steps that can be followed in personal Org:
1. Add the Salesforce Lightning for Gmail extension in Chrome.
2. Enable 'Lightning for Gmail' in the Org. Add a dummy inline VF page to a Contact page layout.
3. Open Gmail account. On the right hand side of the page a panel comes up asking to login to Org. Login to the Org.
4. Search for a contact in the search bar, and open the same.
Expected results : The inline VF page should show up like in Classic.
Actual results : Error message pops up, and the inline VF page doesn't show up:
This page has an error. You might just need to refresh it. Error in $A.getCallback(){Failed to execute 'replace' on 'Location':The current window does not have permission to navigate the target frame to...} Callback failed
Workaround
None as now
Reported By (4)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.