We have a number of applications that leverage tools such as the CKeditor
to enable embedding user authored content. Allowing this content to refer
to a gadget is a valuable use case, but introduces a problem when the user
goes into edit mode as the editor component injects its own iframe into the
page. This patch allows such a gadget placement to work even while in the
rich text editing mode.

Rich Thompson



From:   "Henry Saputra (Commented) (JIRA)" <[email protected]>
To:     [email protected],
Date:   02/27/2012 01:30 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=13217353#comment-13217353
 ]

Henry Saputra commented on SHINDIG-1704:
----------------------------------------

I just want to make sure I understand the purpose of the patch:
1. Trying to render gadget with common container which has gadget site
inside the window of another iframe already in the same window.
2. Now, the rpc code in the container should check for the embeddedlevel
hash value of the current container window to get the right window where
the DOM element for the site live?

I dont think this is the scenario intended for the rpc and common
container.

> 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



Reply via email to