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

Question

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?

Solution 1

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

Solution 2

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

Solution 3

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.

Solution 4

Other solutions didn't work for me. Had to close and restart browser to be able to set breakpoints again.

View more solutions

Comments

[Tanner]

Thank you... debugged 1000 times before! I too am a fool!

[Aleksei Chepovoi]

Yeah, yesterday downloaded this version. It can mislead developers at the first time:)

[mwardm]

Also known as "Pretty print" - but yes, this was my not-exactly-intuitive problem also.

[Eric]

Ha, ha ... I just had this issue, and I came across your post ... and I realized that I had already given it an upvote over a year ago. So much for learning from my mistakes. But thanks, again!

[Vasyl Boroviak]

Thank you. This saved my day. Close and open devtools - such a weird bug!