Feature Request - Break on [Violation]
10 views
Skip to first unread message
Robert Edgar
Jul 19, 2017, 3:11:52 AM7/19/17
to Google Chrome Developer Tools
The new [Violation] warnings are quite interesting and potentially very useful but .....
I get a console log [Violation] 'success' handler took 175ms.
The particular routine gets called a thousands of times and has a problem just once but I have no way to track down what the problem really is.
I get a console log [Violation] 'success' handler took 175ms.
The particular routine gets called a thousands of times and has a problem just once but I have no way to track down what the problem really is.
What would be useful would be the ability to break at the point a Violation is raised so I could look at what code it is actually executing.
Rob
Reply all
Reply to author
Forward
0 new messages