We found the problem is in IE Implementation.js file by temporarily replacing the IE implementation file from an older version and doing so would fixes the issue mentioned. So there could be some issue in the latest IE implementation file.

 

Please check the file and update us.

 

Thanks,

Shaveta