Problem report - ListGrid with canExpandRecords=true and Simplicity Skin

[jaredm]

The problem can be reproduced in the Isomorphic showcase samples. It can only be reproduced if using Simplicity Skin and a ListGrid configured to support expanding rows).

The problem does not appear when using other skins (tested using Enterprise and EnterpriseBlue). It also only seems to affect Internet Explorer (version 11 tested only).

Steps:
1. Navigate to the fetch sample and select Simplicity skin if not already chosen: http://www.smartclient.com/?skin=Sim...tchOperationFS
2. Add the property 'canExpandRecords' and set to true:

isc.ListGrid.create({
    ID:"dsListGrid", 
    width: "100%",
    height: "100%",
    minFieldWidth:80,
    autoFetchData: true,
    canExpandRecords: true,
    dataSource: "supplyItem" 
});

3. Click 'Run'
4. Scrolling via the mouse scroll wheel works as expected.
5. Scrolling by selecting and dragging the scroll bar track-piece causes the entire scrollbar to disappear.
6. Scrolling via the scroll wheel continues to work, but the vertical scroll bar is entirely corrupted and can no longer be selected or used with the mouse.

Tested on:
IE 11.0.9600.17914 (affected)
FireFox 39.0.3 (not affected)
Chrome 44.0.2403.130 m (not affected)

Screenshot (IE 11) attached. https://www.evernote.com/l/AA3NGNFbg...pkMB/image.png


Unfortunately, the app is set to go into production soon at a licensed customer where IE is the target browser. Would really appreciate if Isomorphic could help out on this one.

I'll continue my own investigation in the meantime. I have identified that the disappearance is triggered by the next server call to get further paged data.

[jaredm]

We've found that we can temporarily work around this issue by changing the 'showCustomScrollbars' on the Canvas to true in the case of IE.

Appears to definitely be a problem with native scrolling on IE.

[Isomorphic]

We've just made a fix for another customer that might also address the problems you mention.

See http://forums.smartclient.com/showth...t=30654&page=3

[jaredm]

Thanks Isomorphic, our developers have tested the latest build and the issue appears resolved. It's over with the test team now but hope is they won't find any problems either.