Are you dealing with a gadget that uses a library that modfies the fragment? This is a common problem with those libraries, which is why all internal libraries use gadgets.util.getUrlParams to access any original input. We capture this immediately at load time to ensure that nothing the app does can damage the original data.
On Tue, Feb 10, 2009 at 2:27 AM, Arnaud Bailly <[email protected]> wrote: > Hello, > We are running on a subtle problem with developing gadget on IE6: The > URI fragment that contains the rpcToken used for authentication > 'vanishes' after iframe's content is loaded. The 'src' attribute of > the iframe contains the fragment, but doing document.location.href or > window.location.href within the iframe yields no fragment. > > This of course implies that gadget cannot authenticate themselves with > the container and cannot do any rpc. > > Help greatly appreciated, > -- > Arnaud Bailly, PhD > OQube - Software Engineering > > web> http://www.oqube.com >
