Ah, yes the second solution looks best. No SOP issues here, as I'm writting both the inner and outer stuff. That should work quite nearly. Cheers :)
*also stars both topics* On May 29, 1:06 am, Thomas Broyer <[email protected]> wrote: > On 28 mai, 13:51, twdarkflame <[email protected]> wrote: > > > Ok, in my long-quest to get around IE's token problems, Ive had > > another idea; > > Your problem is a "known quirk" > Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=2152 > andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=2868 > > > Could I use a DOM call to set the contents of a hidden text box in an > > iFrame, then have the application in the iFrame listen for the change? > > If you're not facing SOP, then how about exposing History.newItem() to > JavaScript and just call it from the "outer > window"?http://code.google.com/webtoolkit/doc/1.6/FAQ_Client.html#How_do_I_ca... > > > Thus, I can pass variables to the "inner" application without using > > tokens at all? > > Another possibility: set the iframe's window.name and check for > changes from a repeating timer (this is how history is implemented > BTW, checking for changes to the URL's hash) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
