IE and FireFox - different error patterns about idx

[yungsters]

@joselcc Thanks for investigating and providing all the actual patterns that materialize on the different browsers. This is way more thorough than anything I originally did because I never intended for the actual idx runtime function to be used in production.

Given that there may not be a way around this in Edge / IE and that babel-plugin-idx exists, I'm not sure there is much to be done here. What do you think?

[sunilkumar060]

FireFox
// Access to a property of an object set as undefined
var a = undefined;
a.someProperty
TypeError: a is undefined
// Access to a property of undefined (global object)
undefined.someProperty
TypeError: undefined has no properties

IE and EDGE
// Access to a property of an object set as undefined
var a = undefined;
a.someProperty
Unable to get property 'someProperty' of undefined or null reference
// Access to a property of undefined (global object)
undefined.someProperty
Unable to get property 'someProperty' of undefined or null reference

can I get solution to these errors