Description

One of the effects of this bug is that RPCs sent from a container to gadget iframes do not reach their destination because the RPC library fetches the frame reference from window.frames[id]. This is the code fragment from Shindig:

Vadim Gerasimov
added a comment - 18/Feb/10 23:36 I agree that adding gadgets.rpc.useIdOverFrameName(); would be a good solution. getElementById may have unexpected side effects in other browsers and could be slower.

I'm exceedingly leery of inverting this logic, mostly out of personal experience that any change to the rpc setup API causes odd and unfortunate breaks. That said, I wouldn't be opposed to adding a method that opts in a library user to this behavior eg:

John Hjelmstad
added a comment - 09/Feb/10 22:33 I'm exceedingly leery of inverting this logic, mostly out of personal experience that any change to the rpc setup API causes odd and unfortunate breaks. That said, I wouldn't be opposed to adding a method that opts in a library user to this behavior eg:
gadgets.rpc.useIdOverFrameName();
--> all subsequent requests use document.getElementById(...) first.

Jacky Wang
added a comment - 09/Feb/10 07:32 Hi Vadim,
Which version of Shindig are u using? On PHP one, we have a known issue opened there - the RPC communication between container and gadget will fail because of a javascript inclusion problem.
If it's the case, you may like to apply the patch on SHINDIG-1260 : https://issues.apache.org/jira/secure/attachment/12435197/shindig-1260-revised.patch
Hope it helps.
Regards,
Jacky