So does the frame.setURL always cause's refresh ???? that was not the case with me? if it refreshes the URL my problem would be solved ..
On Jul 9, 10:22 pm, Paulo Coutinho <[email protected]> wrote: > I have the same problem e post the same problem in the list, when u > chage the frame url on non-ie browser, it work, but on IE it dont > work. > > 2009/7/10 Jerome <[email protected]>: > > > > > > > > > Hi , > > > I am running in to a problem when I try to load a URL in a frame, URL > > which is also a GWT application but compiled and deployed in GWT 1.5 > > when I try to load the app it says version mismatch and doesn’t load > > at all. In the web mode still I could see only the plain blank frame. > > If I do a right click and refresh it loads the page. > > > This is the exception I am getting this exception in hosted mode in we > > b mode no exceptions: > > > [ERROR] Invalid version number "1.5" passed to external.gwtOnLoad(), > > expected "1.6"; your hosted mode bootstrap file may be out of date; if > > you are using -noserver try recompiling and redeploying your app > > > Any idea why it is causing that problem …. Is there is any way to > > bypass or any ways to programmatically simulate the right-click > > refresh? If you can gets the code to refresh the frame using JSNI that > > will be great … > > > Thank you for reading the post. > > > Regards, > > Jerome. > > > On Jun 4, 2:34 pm, twdarkflame <[email protected]> wrote: > >> Ok, the solution of shareing the history function of the top window > >> ver native javascript worked great. > > >> But I'm running into a silly problem compileing the sub frames > >> code....as the function it refers to isnt there, it claims error and > >> wont let me compile. > >> (because, of course, the function wouldnt be there untill its being > >> hosted as a sub-page of the main page). > > >> How do I tell it to overide or ignore this? > > >> I thought about putting an if statement to test the url and only run > >> the function if the url isnt containing localhost...but thats a pretty > >> crude fix. > > >> 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 passvariablesto 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)- Hide quoted text - > > >> - Show quoted text - > > -- > Atenciosamente, > Paulo Coutinho. > Blog:www.prsolucoes.com/blog > Site:www.prsolucoes.com > Msn: [email protected] Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
