Chrome DOM breakpoint allows

Yes, in the console, I made a terrible mistake by setting the DOM breakpoint on an element that did not receive the contents into which it was inserted, which I expected from it.

Well, now when I load this page, the breakpoint triggers. Uncheck the box next to it. He is coming back. I right-click on it and click on “Delete breakpoint”. It disappears from the list and seems to work fine until the next hard update, then the BAM breakpoint.

I click the "Disable all breakpoints" button. It works again until the next update, then the BAM breakpoint. Closed chrome, reopened. Same. Closed all tabs individually and closed Chrome through the menu, destroying all the tab memory. Also.

I put on a loincloth and did an intricate dance, I knew it was a stretch, but I gave it a chance. I found an exorcist to help with my plight, but he ran off promptly, screaming in fright. With the light of Eärendil, my machine I did annoint, hoping to rid it of this [expletive deleted] breakpoint. But nothing has worked, no matter how hard I fought, so now I humbly ask assistance of you lot. 

Has anyone encountered this problem?

I am in Windows 7, Chrome 14.0.835.202 m.

+43
google-chrome google-chrome-devtools
Oct 20 2018-11-21T00:
source share
4 answers

here: http://code.google.com/p/chromium/issues/detail?id=91666

To clear all control points, open the inspector on the inspector (first open the inspector and press Ctrl-shift-I to open the second one) and run "WebInspector.settings.domBreakpoints.set ([])" in the second inspector of the console.

+27
Feb 10 '12 at 10:20
source share
— -

Sometimes, when you set breakpoints, you can also "pause exceptions." This will give unwanted Sustainable breakpointy behavior. Scroll the “pause on exceptions” button (bottom left) to disable it (note: it is not on / off, but there are three possible states)

+7
Feb 11 '13 at 14:46
source share

Fixed, had to upgrade Chrome to 15.0.874.106.

 Settings > About Google Chrome > Relaunch 

My breakpoint no longer starts, but I'm tired of checking if the real bug is fixed or not. Chrome no longer has DOM access points.

+3
Oct 29 '11 at 7:18
source share

I have this problem in Chrome 33. In the small inspector in the section, in the window of which there are sub-windows for “Breakpoints” and “Call Stack”, etc., at the top of the window there is a little icon icon that allows you to disable breakpoints . New windows require re-shutdown.

Not the best solution, but it allowed me to continue to work in Chrome at the moment.

0
Oct 17 '14 at 20:13
source share



All Articles