SelectItem Issue

[ESherbakova]

Hi,

We have an issue of the select item with long list of items. When we click the picker icon. Some part of the list is displayed on the left side of the screen.

We are using 2012-03-01_v82p build. It worked well on 2012-01-30_v82p_PowerEdition.

Steps to reproduce:

Click the picker icon of the selected field, then you will find some part of the list is displayed on the left side of the screen.

var myVM = new Array();

for (var i =0; i<174; i++) {
   myVM[i] = "Service "+ i;
};

isc.DynamicForm.create({
    top: 45,
    width: 500,
    numCols: 4,
    autoDraw: true,
    fields: [
        {name: "division",
         title: "Division",
         type: "select",
         valueMap: myVM
         }
    ]
});

[Isomorphic]

This issue will be resolved in the next nightly build. Sorry for the inconvenience

Regards
Isomorphic Software

[ESherbakova]

Thanks for your quick response!

[acarur01]

We have another issue with SelectField value maps - It sounds familiar but I can't recall. The problem is IE9 specific. If you run the testcase in FF or IE8, the valueMap shows as expected - Thang Test 2 shows up first. If you run the testcase using IE9, "test test" shows up first.

isc.DynamicForm.create({
width: 500,
fields: [{
name: "shipTo", title: "Ship to", type: "select",
hint: "<nobr>Overnight shipping available for countries in bold</nobr>",
valueMap:{1560014: "Thang Test 2 ID: 1512041",1514010: "Karim The BEst ID: 1512002",1561126: "Thang Test ID: 1512024",1513003: "test test ID: 1314010"}
}]
});

[Isomorphic]

In IE9 and recent Chrome, when you use numeric keys in JavaScript Objects, those keys no longer have predictable order. So when you pass the Object to us, the order is lost before we get it.

We consider this a huge mistake and hope that the ECMAScript standard will evolve to require consistent ordering for numeric and non-numeric keys.

In the meantime, the only workaround is to use optionDataSource instead for these cases.

[acarur01]

SO, if I change the keys to be string, then it should work consistently across all browsers?

[acarur01]

Hmm ok - I even tried putting quotes around the numbers and it still renders the same problem. I had to make the values completely string values (added letters to each one) for it to work as expected

[Isomorphic]

Right, if the values are parseable as numbers then the problem occurs. This is why it's just a bad behavior on the part of the browser.