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.
google-chrome google-chrome-devtools
andrew Oct 20 2018-11-21T00: 00Z
source share