Hi again,

Could you finally test this issue with ExtJS 5?

Could this problem be tested with current Ext.NET 3 version? or should it be tested directly with ExtJS 5?

Thanks again for your king support.