To test, open DevTools, right-click on the hidden folder and add it to the ignore list, enable the relevant break settings, and click a button below.

Scenarios

• Stepping:
  • One repeated callback
  • Two callbacks
  • Async Two callbacks
• Exceptions:
  • Uncaught:
    • Top frame ignored
    • All frames ignored
    • Async Top frame ignored
    • Async All synchronous frames ignored
    • Async All frames ignored
    • Runtime error - Top frame ignored
    • Runtime error - All frames ignored
    • Runtime error - No call stack
    • Async Runtime error - No call stack
    • WebAssembly trap
    • WebAssembly trap - no JS frames
  • Caught:
    • Caught in non ignore listed code Caught in non ignore listed code
    • Within ignore listed code Within ignore listed code
    • Passing through non ignore listed code Passing through non ignore listed code
    • Async Passing through non ignore listed code Async Passing through non ignore listed code
• Trusted types:
  • CSP Violation
    <div onmouseenter="window.alert('0wnd')">Hover here</div>
  • CSP Violation - All frames ignored
  • Async CSP Violation
• Pausing or Event Handlers
  Set a mouse click event handler breakpoint or press pause and then click:
  • Wrapped event handler
  • Fully ignored event handler
  • Async Wrapped event handler
• DOM Breakpoints
  Set a DOM breakpoint for subtree modifications on the following sentence:
  Break on me.
  Then click:
  • DOM breakpoint
  • DOM breakpoint - All frames ignored
  • DOM breakpoint - No call stack (Also an interesting event handler/pause case.)
• XHR/fetch Breakpoints
  Set a XHR/fetch breakpoint for urls including the text "ignoreme", then click:
  • XHR/fetch breakpoint
  • XHR/fetch breakpoint - All frames ignored
• debugger statement:
  • debugger statement
  • debugger statement - All frames ignored