Problem is that it is an outside tool that is consumed as a component. From what I understand, we do not have a way of impacting the loading of the iframe and making it a completely separate container would result in significant bloat in the client and not provide normal operation for things such as eventing.
Is there some significant problem with having the core provide support for placing a gadget within an (uncontrolled,) embedded iframe? Rich Thompson IBM T.J. Watson Research Center / Hawthorne, NY Phone: (914) 784-6203 / (203) 445-0384 email: [email protected] From: "Henry Saputra (Commented) (JIRA)" <[email protected]> To: [email protected], Date: 03/03/2012 09:46 PM Subject: [jira] [Commented] (SHINDIG-1704) rpc does not support communicating with gadget created in an existing iframe [ https://issues.apache.org/jira/browse/SHINDIG-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221768#comment-13221768 ] Henry Saputra commented on SHINDIG-1704: ---------------------------------------- Can the CKeditor iframe include Shindg common container script to become small OS container? this will allow the CKEditor to host the gadget? > rpc does not support communicating with gadget created in an existing iframe > ---------------------------------------------------------------------------- > > Key: SHINDIG-1704 > URL: https://issues.apache.org/jira/browse/SHINDIG-1704 > Project: Shindig > Issue Type: Bug > Components: Javascript > Affects Versions: 2.0.2 > Reporter: Yao Zhang > > When you try to render a gadget to a dom node inside an existing iframe, rpc does not work as the code is using document.getElementById to get the domnode. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
