1

I have an angular application (works great in chrome and edge) that will crash IE 11 dev tools immediately upon opening.

I overwrote console.log to output to my window to try and get some information and bypass some older IE issues, and I'm getting a areq error on a controller. Iv'e gotten the rest of my app to work in IE11, but not in this one controller.

Are there any known issues with IE11 dev mode and angular or 3rd part extensions?

Is there any way to find out what (presumably) syntax fopaw is killing this single controller in IE without Dev Tools?

Listed are my deps:

'ngRoute',
'ui.bootstrap',
'ngAnimate',
'ngCookies',
'agGrid',
'checklist-model',
'nvd3',
'datatables'

Any and all insight into this VERY frustrating IE issue would be much appreciated.

4
  • have you tried having the dev tools detached? Commented Mar 3, 2016 at 20:12
  • did you try $log instead console.log? Commented Mar 3, 2016 at 20:17
  • yea i'm doing $log. I haven't tried detached. I will right now. Commented Mar 3, 2016 at 21:26
  • Detached doesn't work either. Commented Mar 3, 2016 at 21:27

1 Answer 1

1

This turned out to be a known issue with IE.

https://social.msdn.microsoft.com/Forums/ie/en-US/932b6322-7a9c-4801-a30f-8403bafe1997/dev-tools-crashing-ie-with-angular-app?forum=iewebdevelopment#ed33def7-2769-4af7-831c-ef2822a44174

When I completed my GULP build process for dev and production the issues went away. IE team is supposed to be patching this, i haven't confirmed if the latest update fixes or not, but it should be good according to them.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.