I started using Google Chrome dev tools, but sometimes the break points become inactive and an asterisk appears on the file tab in the debug window. Anyone know why? I guess it is a common behavior, but I want to know how to avoid this. Thanks

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.
This is because you’ve edited the javascript file inside Chrome’s inspector.
Chrome let’s you edit the javascript right in the browser, but once you’ve edited the javascript the breakpoints you set will not be hit until you save the edited file (ctrl-s).
You can tell that you’ve modified the file because of the asterisk next to the name in the tab. i.e.
on_cell_change.js*– the*means the file is edited.To avoid having this happen at all, don’t type inside the javascript source.