Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to set breakpoints in Chrome dev tools, version 26.0.1410.64 m

I need to debug some JavaScript an' I use Chrome dev tools. I'm a newby in JavaScript (just started to learn a couple of days ago), an' at work I could set breakpoints via the Resources pane. But at home for some reason I can't do this: after the click no breakpoint appeares.

I have Chrome version: 26.0.1410.64 m.

What could be the case?

like image 943
Aleksei Chepovoi Avatar asked May 07 '13 18:05

Aleksei Chepovoi


People also ask

What allows to set breakpoints?

Set breakpoints in source code To set a breakpoint in source code, click in the far left margin next to a line of code. You can also select the line and press F9, select Debug > Toggle Breakpoint, or right-click and select Breakpoint > Insert breakpoint. The breakpoint appears as a red dot in the left margin.

How do I fix dev tools in Chrome?

# Open the Issues tab Open DevTools. Click the Go to Issues button in the yellow warning bar. Alternatively, select Issues from the More tools menu. Once you're on the Issues tab, click the Reload page button if necessary.

How do I enable Chrome debugging?

Press Command + Option + J (Mac) or Control + Shift + J (Windows, Linux, ChromeOS) to jump straight into the Console panel.


3 Answers

clicking on the De-Obfuscate Source button (i.e. {}) solved this issue for me.

like image 56
Lotus Avatar answered Oct 16 '22 12:10

Lotus


I'm a fool! haha! breakpoints are set in the Source pane )))

like image 45
Aleksei Chepovoi Avatar answered Oct 16 '22 11:10

Aleksei Chepovoi


It's been a while, but in version 33.0.1750.146, but my problem was that I was on the Sources pane (I'd call this a tab; it's one of the items at the very top of the window), but I was on the Content scripts tab (on the left hand side). I needed to switch to the Sources tab.

To be clear, there are two sets of Sources tabs; one is within the other.

UPDATE 2016-01-07: Now I'm on 47.0.2526.106. The only thing that worked for me today was to close DevTools and re-open. It was a little finicky. It worked once, then stopped, and I had to close the DevTools and re-open again. I saw @johntrepreneur's answer about closing the browser, but unfortunately I have too many tabs open on too many workspaces, so that's too much of a pain, so I didn't try that, although I have to assume that would work.

like image 4
Tyler Collier Avatar answered Oct 16 '22 11:10

Tyler Collier