Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Since upgrading to Rails 3.1 upgrading Chrome I’ve had problems using the Chrome Developer Tools. There seem to be phantom breakpoints in the compiled application JS- the one which pops up most often for me is in Sizzle.matchesSelecter (line 4941, YMMV)
I haven’t found any indication why the debugger thinks there’s a breakpoint there, or any way to disable these breakpoints. It’s killing my workflow.
Is this common in Rails release candidates? Is there a way to fix it?
Edit
Foot in mouth.
You probably have the chrome debugger set to break on any exception and you just need to turn that off. See Is there a way to get the google chrome script debugger to break on exception? for details.