UPDATE 2
There has been an improvement in user flow of this feature in latest versions of chrome. Please refer to https://developer.chrome.com/devtools/docs/blackboxing
UPDATE 1
Since Chrome version 38, you no longer have to enable Developer Tools experiments.
Below details are only for history
This is possible now in chrome version 30+.
- Enable "Enable Developer Tools experiments" from
chrome://flags/#enable-devtools-experiments
. (Yes, you need to type that where you type the URL)
- Relaunch chrome
- Click on settings icon in Chrome Developer Tools
- Go to Experiments section. Notice the WARNING ;) and then tick
Enable frameworks debugging support
. (You also might want to try Show step-in candidates while debugging
)
- Now, close Chrome Dev Tools and again open it.
- Click on settings icon in Chrome Developer Tools
- In general section you will find "Skip stepping through sources with particular names". Tick that and provide (regex) for the javascript file names which you want to skip stepping into.
Source: Tips and Tricks: Ignoring library code while debugging in Chrome
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…