Re: single-origin error, shouldn't be happening?
Created issue http://code.google.com/p/google-web-toolkit/issues/detail?id=3795 to track ... On Jun 26, 9:29 am, Brice bdr...@gmail.com wrote: I was able to use the emulate IE7 hack to get IE8 to work, but that's nasty and I keep hoping there's going to be a way I can upgrade to a recent release of GWT. On Jun 25, 11:20 pm, Brice bdr...@gmail.com wrote: Good evening, I'm revisiting a project that I worked on a year back that ran into trouble when I tried to upgrade to 1.5.3 from 1.5.2. Here's a post that I made at that time: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... In a nutshell, the project uses GWT to provide a rich interface for a CD-ROM product, so it runs w/o any backend web-server. However, it *does* use RequestBuilder to load XML and JSON data from the CD - but the data is all local to where the GWT app is initialized from. This works fabulously in Safari, FireFox, and IE7 - yay. But, when I tried to upgrade last year to 1.5.3, I found that GWT was throwing an exception about violating single-origin-policy. This is *not* hosted mode, this is compiled-mode, loading the GWT app from the local file- system. I tried upgrading to 1.6.x a month back and found that I still get the same problem. With the recent release of IE8, I can't continue to use GWT 1.5.2 and hope to stay compatible in new browsers, so what can I do?! I'm assuming GWT is using some kind of internal logic to determine if an SOP violation would occur, without actually giving the browser the request, since the browser seems perfectly happy loading the XML and JSON from the local file-system in 1.5.2. Any way to dig into something and disable this check? Or change the way I'm loading? Thanks much! Brice --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: single-origin error, shouldn't be happening?
I was able to use the emulate IE7 hack to get IE8 to work, but that's nasty and I keep hoping there's going to be a way I can upgrade to a recent release of GWT. On Jun 25, 11:20 pm, Brice bdr...@gmail.com wrote: Good evening, I'm revisiting a project that I worked on a year back that ran into trouble when I tried to upgrade to 1.5.3 from 1.5.2. Here's a post that I made at that time: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... In a nutshell, the project uses GWT to provide a rich interface for a CD-ROM product, so it runs w/o any backend web-server. However, it *does* use RequestBuilder to load XML and JSON data from the CD - but the data is all local to where the GWT app is initialized from. This works fabulously in Safari, FireFox, and IE7 - yay. But, when I tried to upgrade last year to 1.5.3, I found that GWT was throwing an exception about violating single-origin-policy. This is *not* hosted mode, this is compiled-mode, loading the GWT app from the local file- system. I tried upgrading to 1.6.x a month back and found that I still get the same problem. With the recent release of IE8, I can't continue to use GWT 1.5.2 and hope to stay compatible in new browsers, so what can I do?! I'm assuming GWT is using some kind of internal logic to determine if an SOP violation would occur, without actually giving the browser the request, since the browser seems perfectly happy loading the XML and JSON from the local file-system in 1.5.2. Any way to dig into something and disable this check? Or change the way I'm loading? Thanks much! Brice --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
single-origin error, shouldn't be happening?
Good evening, I'm revisiting a project that I worked on a year back that ran into trouble when I tried to upgrade to 1.5.3 from 1.5.2. Here's a post that I made at that time: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/4fefe354a5182cbb In a nutshell, the project uses GWT to provide a rich interface for a CD-ROM product, so it runs w/o any backend web-server. However, it *does* use RequestBuilder to load XML and JSON data from the CD - but the data is all local to where the GWT app is initialized from. This works fabulously in Safari, FireFox, and IE7 - yay. But, when I tried to upgrade last year to 1.5.3, I found that GWT was throwing an exception about violating single-origin-policy. This is *not* hosted mode, this is compiled-mode, loading the GWT app from the local file- system. I tried upgrading to 1.6.x a month back and found that I still get the same problem. With the recent release of IE8, I can't continue to use GWT 1.5.2 and hope to stay compatible in new browsers, so what can I do?! I'm assuming GWT is using some kind of internal logic to determine if an SOP violation would occur, without actually giving the browser the request, since the browser seems perfectly happy loading the XML and JSON from the local file-system in 1.5.2. Any way to dig into something and disable this check? Or change the way I'm loading? Thanks much! Brice --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---