Many times, we are all in chrome front-end debugging problems, sudden need to support IE11, IE11 and found the problem, this is really the feeling to life. Fortunately, however, after several hours of exploration, finally we found some ways. Summary down for future reference:
1 js error codes, using IE in the Debugger Break on all exceptions
Js such issues as described above, is probably determined angularjs related issues, but which is not positioned row, the first embodiment is used by way of puncturing the code, the code segment desired location, after a few hours of struggle, the final give up. Oh, this bug is not even have to give up, I go and change for a bug found or need to debug the js, then fumbled for this feature, open the Break on all exceptions, as long as the F12 to open the debug mode, no matter what was wrong gave breadk live and can debugging, I finally found the error code.
2, using the code debugger
I found the break point was not easy in IE, maybe I did not use method.
Summary, found the front end of things, it is to learn more about, at least know which place which may have a pit, do not see the problem, or two of a smear, very time-consuming to solve. And more familiar with some commonly used libraries. Common methods, as well as their corresponding defect, or a pit.