Shindig Team,
Earlier today I updated my local sandbox version of shindig to SVN
revision 960614. When I build and start the server and access the sample
container in Firefox 3 with Firebug open, I get the following console
output:
No relay set (used as window.postMessage targetOrigin), cann
Hi Randy:
What's the top-level page, and how is each gadget initialized to
gadgets.rpc? I'm unaware of any updates to the underlying lib that generates
these errors so I suspect something may have changed in sample container's
gadget init sequence.
For each gadget, you need to do: gadgets.rpc.set
Actually just setting the iframe's parent to point to the container will allow
the 2 calls below to work.
That is the iframe's src should contain a parent parameter that is the same as
the parent.
kam
On Jul 7, 2010, at 8:31 AM, John Hjelmstad wrote:
> Hi Randy:
>
> What's the top-level page,
Kam/John,
I did a little more digging and determined the following:
1. It appears that the first error is occurring while the container is
being loaded, so at that point gadgets are not initializing. As I
mentioned before, the error seems to be the result of an unexpected
configuration since
I'd look more deeply at #1 -- the container will likely have a goodly amount
of trouble if it's trying to send a call to itself, since there's no
initialization for a self-call :) Figure out why that's occurring and I'd
imagine we can get rid of the problem. Sounds like it's not container <->
gadge
John/Kam,
I have created a JIRA issue for these errors that includes two patches
that are ready for review.
https://issues.apache.org/jira/browse/SHINDIG-1380
The description in the JIRA issue outlines what I think is going amiss.
Of course, the patches may not be perfect, but they do indica
