You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Henry Saputra (JIRA)" <ji...@apache.org> on 2012/07/09 20:59:34 UTC
[jira] [Created] (SHINDIG-1816) Change the check for child RPC to
also verify if parent url parameter exists
Henry Saputra created SHINDIG-1816:
--------------------------------------
Summary: Change the check for child RPC to also verify if parent url parameter exists
Key: SHINDIG-1816
URL: https://issues.apache.org/jira/browse/SHINDIG-1816
Project: Shindig
Issue Type: Bug
Components: Javascript
Affects Versions: 2.5.0-beta2, 2.5.0-beta1, 2.0.0
Reporter: Henry Saputra
Priority: Minor
The Shindig container could be rendered inside parent iframe and in this scenario, the rpc check for isChild (almost the same as check fro isGadget) does not work well because its actually act as the real container even though its put inside another iframe.
The proposed fix to add check for url param "parent" as well as the check for window instance.
--
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
[jira] [Assigned] (SHINDIG-1816) Change the check for child RPC to
also verify if parent url parameter exists
Posted by "Henry Saputra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Saputra reassigned SHINDIG-1816:
--------------------------------------
Assignee: Henry Saputra
> Change the check for child RPC to also verify if parent url parameter exists
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-1816
> URL: https://issues.apache.org/jira/browse/SHINDIG-1816
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Affects Versions: 2.0.0, 2.5.0-beta1, 2.5.0-beta2
> Reporter: Henry Saputra
> Assignee: Henry Saputra
> Priority: Minor
>
> The Shindig container could be rendered inside parent iframe and in this scenario, the rpc check for isChild (almost the same as check fro isGadget) does not work well because its actually act as the real container even though its put inside another iframe.
> The proposed fix to add check for url param "parent" as well as the check for window instance.
--
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
[jira] [Resolved] (SHINDIG-1816) Change the check for child RPC to
also verify if parent url parameter exists
Posted by "Henry Saputra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henry Saputra resolved SHINDIG-1816.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.0-beta3
Committed revision 1359422.
> Change the check for child RPC to also verify if parent url parameter exists
> ----------------------------------------------------------------------------
>
> Key: SHINDIG-1816
> URL: https://issues.apache.org/jira/browse/SHINDIG-1816
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Affects Versions: 2.0.0, 2.5.0-beta1, 2.5.0-beta2
> Reporter: Henry Saputra
> Assignee: Henry Saputra
> Priority: Minor
> Fix For: 2.5.0-beta3
>
>
> The Shindig container could be rendered inside parent iframe and in this scenario, the rpc check for isChild (almost the same as check fro isGadget) does not work well because its actually act as the real container even though its put inside another iframe.
> The proposed fix to add check for url param "parent" as well as the check for window instance.
--
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