OK, dug a bit more and tracked down the breakage. I had my relay URL in the wrong spot.
FF2: works if the container calls gadgets.rpc.setAuthToken, falls back to IFPC otherwise. Chrome and Safari: never works, falls back to IFPC. Given that I can no longer claim that window.frameElement makes Chrome and Safari non-functional, I have less of a case for killing it. =) I kind of still want to. Cheers, Brian On Wed, Mar 25, 2009 at 4:09 PM, John Hjelmstad <[email protected]> wrote: > Sorry, just seeing this now. > FE should only ever be used for FF2. We should ensure that getRelayChannel() > is updated so that it only selects FF2 and doesn't accidentally pick up > Safari 3.2 or Chrome (is that what's happening?), rather than removing it > altogether. > > --John > > On Tue, Mar 24, 2009 at 10:08 AM, Brian Eaton <[email protected]> wrote: > >> Good morning. Time to kill something. >> >> The "fe" channel in gadgets.rpc is broken on some major browsers. It >> works on Firefox 2. It breaks on Safari 3.2 and Chrome. Firefox 3 >> uses the standard window.postMessage channel. >> >> Any objections to removing the code? Safari 3.2 and Chrome will then >> fall back to IFPC. >> >> Cheers, >> Brian >> >
