Problem upgrading to RC2 with IE7

[ARK]

Hi all,

I just upgrade my project to 1.4 RC2 and found one strange problem
with IE7. I think IE6 also has this problem but in Firefox, it works
well.

To reproduce this problem: open one new IE window and input my
project address: http://www.shoofr.com
OK. everything works well.
Open a new tab in IE7 and open the website again. It will show
"Internet Explorer cannot open the Internet site http://www.shoofr.com.
Operation aborted."

You also can try IE6 (open two window, but I only have IE6 so I am not
sure u can reproduce it in IE6).

It is a very strange problem which never happen before upgrading to
Rc2, I am thinking whether it is related. Any suggestions are make
sense to me.

PS: I use some google icons because I like google UI every well and it
is my personal project. If it is not suitable I will change it. sorry.

Thanks,Ark

[ARK]

Type mistake in previous post. just change it.

On Aug 27, 12:32 am, ARK <ark.w...@gmail.com> wrote:
> Hi all,
>
> I just upgrade my project to 1.4 RC2 and found one strange problem
> with IE7. I think IE6 also has this problem but in Firefox, it works
> well.
>
> To reproduce this problem: open one new IE window and input my
> project address:http://www.shoofr.com
> OK. everything works well.
> Open a new tab in IE7 and open the website again. It will show

> "Internet Explorer cannot open the Internet sitehttp://www.shoofr.com.

> Operation aborted."
>
> You also can try IE6 (open two window, but I only have IE6 so I am not

~~~IE7

[ori s]

I'm also having a similar issue. Upgrading to 1.4.2 from 1.4.1 will
now generate "operation aborted" errors in IE6.

> > Thanks,Ark- Hide quoted text -
>
> - Show quoted text -

[smeagol]

It happens to me too with RC2 and IE6 except that it occurs very
randomly. I haven't seen it happen in hosted mode yet.

This is the line that always fail for me.

function java_lang_String_$length__Ljava_lang_String_2(this$static){
return this$static.length;
}

I don't remember what was the error message, i have been trying to
reproduce it for the last 10 minutes without success. I'll try to
collect more data when I can.

[ARK]

I've changed back to RC1. 1.4.10. So it is not possible to reproduce
this problem using the URL I provided.

[asg]

I have had same problem "Operation aborted" with GWT 1.4.59 & 1.4.60
in IE6 and IE7.
Very frustrating because does not happen every time but quite often,
and if user clicks OK in "Operation aborted" dialog and F5(refresh)
everything works okay until next time.
I've rolled back to 1.4.10 and everything works just fine now.
Thank you for the hint, ARK, saved me a lot of time.

[Bob Lebel]

I think i have found a workaround. I moved the <script> declaration to
the end of my html pages and the problem went away (but the script
start a little slower). I will use browser detection and only do this
for IE. For the other browsers, i'll let the script at the beginning
of the pages. Let me know if it works for you too.

[sargual]

Now the error doesn't appear, but links don't do what they should
anymore. Instead of loading a screen by its token, they reload the
app.
(i must say my app is embedded in an external page)
In my .html document, the order of relevant (?) things is:
- the <meta name="gwt:module" cont="com.domain...MyEntryPoint">
- the <iframe...> declaration
- then, the html links to my screens:
<a href="#token">Name</a>
which Don't work as expected anymore.
- then the div which holds my gwt content
- the <script language="javascript" src="gwt.js"> declaration

Could it be a matter of how things are ordered in my html, since
that's the only thing that's changed?

TIA

[sargual]

by the way, what i did was moving the <script language="javascript"
src="gwt.js"> to the end, instead of changing to the older version. i
haven't tried that.

[Sumit Chandel]

Hi ARK,

Thanks for bringing this issue up. It's hard to say what might be going wrong here with the current information available. Could you list out the steps you took to upgrade from RC1 to RC2? For anyone else who's experiencing this problem, please feel free to post up the steps you took to upgrade from RC1 to RC2/1.4.

@sargual, it seems that the current bootstrap model your application is using is following the old 1.3 version. This has been changed for better application load time performance. You might want to take a look at the new bootstrap model for 1.4 and update your application accordingly. Check out the FAQ below for details on the new bootstrap model:

http://code.google.com/support/bin/answer.py?answer=75278&topic=12430

Thanks,
-Sumit Chandel

[Bob Lebel]

I don't think the problem is in the steps we took to upgrade. I used
several rc2 build without having this problem and I think the problem
was introduced with revision r1205. They talk about it on the
contributor forum here:

http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_frm/thread/1165e4db9d3945c8/6bb9e5efdb224bae?lnk=gst&q=onModuleLoad&rnum=12#6bb9e5efdb224bae

There is also more detail on this issue here :

http://code.google.com/p/google-web-toolkit/issues/detail?id=1578&sort=-id

[ARK]

Is there any update what's the current status of this problem?

On Sep 6, 8:58 pm, Bob Lebel <boble...@gmail.com> wrote:
> I don't think the problem is in the steps we took to upgrade. I used
> several rc2 build without having this problem and I think the problem
> was introduced with revision r1205. They talk about it on the
> contributor forum here:
>

> http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse...

>
> There is also more detail on this issue here :
>

> http://code.google.com/p/google-web-toolkit/issues/detail?id=1578&sor...

[Sumit Chandel]

Hi ARK,

This issue has been given critical priority in the Issue Tracker to make sure it gets addressed for the 1.5 RC.

http://code.google.com/p/google-web-toolkit/issues/detail?id=1578

In the meantime, it seems that using the 1.3 bootstrap model (using gwt.js instead of <app>.nocache.js) is a suitable workaround until this issue gets fixed. I would suggest that anyone experiencing this problem try using the older bootstrap model to see if that resolves the issue. Please report back on the issue report if the problem persists.

@sargual: I'm not sure why the <a href="#token"> links would no longer work as a result of pushing down the <script> tag. Could you create an new issue report for this problem? If pushing the <script> tag down does indeed cause the problem of broken links, it should be reported as a separate issue on the Issue Tracker. Please attach your project source code to the issue report if possible.

Thanks,
-Sumit Chandel

[jeeg]

Hi Sumit Chandel,

I have the same problem with 1.4.60 and in my case using the 1.3
bootstrap model did not help. The only workaround that works ist
moving the bootstrap ( <app>.nocache.js ) at the end of the body
in the host page.

Thanks
-jeeg