IE & Edge Error - ERROR TypeError: Unable to get property 'nativeElement' of undefined or null refer
Hello,
I am using the Box Content Explorer and it is not loading in IE and Edge. I've done some significant research in the community support section of Box related to IE and Edge, specifically with Polyfills, but haven't had any luck. These are some of the pages I've seen where I've tried the solutions and they didn't work:
- https://community.box.com/t5/Platform-and-Development-Forum/Getting-error-on-IE-11-with-Content-Explorer/m-p/52686
- https://community.box.com/t5/Platform-and-Development-Forum/Internet-Explorer-is-compatible-with-BOX-UI-Element/m-p/64060
These are all the polyfills I have pulling into the iFrame: https://polyfill.io/v3/polyfill.min.js?features=es2016%2Ces2015%2CIntl%2Ces2017%2Ces2018%2Ces6%2Ces7%2Ces5
This is the specific error I am seeing: "ERROR TypeError: Unable to get property 'nativeElement' of undefined or null reference" with stack trace: "TypeError: Unable to get property 'nativeElement' of undefined or null reference at Anonymous function (http://10.0.2.2:3000/main.js:5760:13) at ZoneDelegate.prototype.invokeTask (http://10.0.2.2:3000/polyfills.js:9385:13) at onInvokeTask (http://10.0.2.2:3000/vendor.js:60656:17) at ZoneDelegate.prototype.invokeTask (http://10.0.2.2:3000/polyfills.js:9385:13) at Zone.prototype.runTask (http://10.0.2.2:3000/polyfills.js:9154:21) at ZoneTask.invokeTask (http://10.0.2.2:3000/polyfills.js:9462:17) at invoke (http://10.0.2.2:3000/polyfills.js:9451:21) at timer (http://10.0.2.2:3000/polyfills.js:11020:17)" and this is the code at polyfills.js:11020: "task.invoke.apply(this, arguments);".
For some background, this is an Angular 6 application. We are injecting the BCE as an iframe, accessing it via "@ViewChild" and posting the JSON like this: "bceWindow.nativeElement['contentWindow'].postMessage(this.message)".
I hope I have provided enough information for this. Let me know what else I can do to help.
Thanks,
Jacob
"
-
Hi ,
Can you please add in the code you're using to generate the element? Alternatively you can also go right to the source and file an issue on the Elements Github repo if this is only affecting IE / Edge.
- Jon
Please sign in to leave a comment.
Comments
1 comment