Tested with latest SmartGwt nightly (SmartClient Version: v8.3d_2012-10-23/LGPL Development Only (built 2012-10-23)) - same issue. What version of GWT are you using? I've tried it with both the released 2.4.0 and 2.5.0RC2

Does not happen with Firefox or Chrome. Does with IE9. Happens in development mode (it happened in my app in compiled mode, but I am not set up to run the showcase in compiled mode so I haven't tried it with the sample I sent to you). It is not intermittent.

I cleared the brower cache. You mentioned "all" caches. What other caches are there to clear?

No steps were omitted. In the showcase directory on a Windows 7 system command prompt I did an "ant" to build followed by an "ant hosted" to run. I've also tried it by setting up an eclipse (juno) project and running dev mode from there. I see the problem in both cases.

[Isomorphic]

Augh, this is why we double-checked with you about browsers in post #2. If it's IE9-only, look into IE plugins, and if there isn't an obvious one, go try another machine.

And be sure to test compiled mode, because we can't reproduce the problem, and whether it reproduces in compiled mode is a critical thing to know in terms of suggesting causes.

Probably does not matter, but we used GWT 2.4.

We are seeing this on all of our machines. Most are developer systems with custom plugins based upon individual developer preferences. Some of these machines are plain Windows 7 installations used for doing demos at trade shows, no additional plugins installed in IE on these boxes as far as I know.

I'll try tomorrow to see if I can get the show case running in compiled mode in my tomcat server.

I've teste diwht GWT 2.4 and 2.5rc2 with the same results from both so I don't think this makes any difference.

Yes - it happens in both compiled and dev mode.

[Isomorphic]

We believe we have now resolved this issue. Please try the next nightly build and let us know if you continue to see it

Regards
Isomorphic Software

I tested it and it appears to be fixed! Thank you for sticking with me on this one. I'm curious, can you give me any hint about what the issue was?

[Isomorphic]

It was the menu.fields issue we speculated about (duplicate icon field), but it was triggered by an obscure framework bug to do with accidentally sharing the same Array across two different types of controls.

Not sure why your attempt to test for extra menu.fields didn't hit anything.