IE issue

Hi dear Isomorphic Administrator,

I’m currently using isomorphic for writting an intranet application and I would like to thank you for the great job you have made.

The application uses several Forms, ListGrids bounded to differents Web services in .Net (C#).

All work fine on my computer with Internet Explorer version 6.0.2900.2180.xpsp2. Near to the project’s dead line, I have tested the application on the target computers with Internet Explorer 6.0.2800.1106.xpsp2. The application begins to work fine and then crashes Internet Explorer (IE disappears) after differents user interaction.

The crash seems to occur when the mouse comes from an section header to a button (in the mouseOver event of the button ?) without activating any personal treatment.

I have tried to follow the crah in isc.showConsole, nothing special appears before the crash except this:

TMR9:DEBUG:visual state: isc_IButton_31 : state changed to stretchImgButtonOver
TMR9:INFO:IButton:isc_IButton_31 : call to deprecated setClassName() property - use setStyleName() instead

I have tried to follow the crash in firebug. But the application works fine in Firefox and does not complain about any error.

Any idea or clue to find a way to debug ?

Hi corniquet,

We’ve never had reports of a hard crash of this kind. Questions:

  1. Is this reproducible on more than one machine?

  2. Do you know what exact OS version you have to install in order to obtain that exact version number? A fresh Windows XP install is higher than that.

In terms of troubleshooting - although it will be somewhat laborious with an outright browser crash, the best approach is going to be to try to produce a minimal test case as described in the Issue Reports section of the Debugging topic.

  1. The crash occurs on all machines I have tried on our intranet.

  2. The OS version is windows Xp , sp1, which is not a very updated version but i can’t change it. We are a big company and migration is a big work for system administrators.

I’m trying to make a minimal test case but I can’t for the moment reproduce it
except on the final version.


On these machines, I have the same crash on your “showCase application” demo.

Step to reproduce the crash:

  • open the feature explorer,
  • open the Showcase application,
  • click the button “show example”,
  • when application is loaded, close it with the black cross with an red underground,
  • move the mouse over the tabbed headers
    on [view][JS][XML][supplyCategory][supplyItem]

IE crashes hard.

Hi corniquet,

This now sounds suspiciously like a bug in IE that we had previously thought was limited to Win2k and not XP.

Can you try the following quick hack: immediately after SmartClient is loaded, add “isc.Browser.isWin2k = true;”

Hi Isomorphic,

I have added the line in my program, after the Isomorphic modules loading but the crash is always there.

But I found a way to avoid the problem: I have replaced all “IButton”(s) in the application by “Button”(s). The replaced buttons looks very simple, without any skin applied, but the application works fine and never crashes.

If you don’t find another clue, this way will be fine for the end of the project. But it could be interesting to investigate…

Hi corniquet,

That confirms that this is the same as the Win2k hard crash. This crash is related to using scaled, translucent PNGs. The best way to avoid it is to switch to lower-media skins (eg “standard”), in which many elements that are normally based on the StretchImg component instead use a simpler CSS-only rendering (including IButtons, ListGrid headers, SectionStack headers, pieces of the Window component).

We don’t know of actual workaround this IE hard crash other than installing the latest OS patches (which we understand you cannot do yet).