FormItem prompt message stuck in IE11 status bar

[cyuen]

The prompt message of a FormItem (e.g. CheckboxItem) is stuck in the status bar of Internet Explorer 11 using SmartClient Version: v9.1p_2015-08-21/Pro Deployment (built 2015-08-21)

The problem can be reproduced by the following code snippet:

    var v = isc.VLayout.create();
    v.addMember(isc.DynamicForm.create({
        fields: [
        {
            name: "checkbox",
            prompt: "click me",
            type: "checkbox"
        }
      ]}));
    v.addMember(isc.DynamicForm.create({
        fields: [
        {
            name: "textItem1",
            type: "text",
            showTitle: false
        },
        {
            name: "textItem2",
            type: "text",
            showTitle: false
        }
      ]}));
   v.addMember(isc.IButton.create({title: 'Click'}));

Steps to reproduce:
1) Click on the 'checkbox' and 'click me' prompt appears on the IE11 status bar
2) Click on any other component (e.g. textItems, button)
ERROR) The 'click me' prompt message still appears on the IE11 status bar

This problem may seem intermittent at times but reloading the page and repeat the above steps seem always able to reproduce the issue.

----------------
SmartClient Version: v9.1p_2015-08-21/Pro Deployment (built 2015-08-21)
Windows 7 Internet Explorer 11.0.9600.17728CO

[Isomorphic]

This would be one to report to Microsoft - we are not explicitly setting the status bar, the browser is doing so based on some kind of heuristic, which appears to work imperfectly / intermittently as you've noticed.

[cyuen]

Creating a generic HTML checkbox does not exhibit the same issue though.

<input type="checkbox" name="cb" value="Blah" title="Click Me"/>

I understand usually the browser try to prevent JS from setting the status bar but I just wonder if there is something Isomorphic does internally that would trigger this behavior or if there would be a work around from Isomorphic on this issue (e.g. an option to turn off prompt message on status bar)?

[Isomorphic]

Whatever the bug is in IE, it seems to be dependent on DOM structure.

We already have to very, very carefully design the DOM we use to work around dozens of other IE bugs - sorry, but this is so minor, we're not going to look into whether the DOM could be rejiggered to avoid tripping this bug. We need some flexibility to further modify the DOM for the future bugs IE introduces.