This illustrates the reliability issues with the Never pause here functionality
in Chrome DevTools, which actually is just a special case of a conditional breakpoint
with condition set to false.
This is an example that was brought up in comment 18 of crbug/465666.
crbug-1401339-sw-install.js in the Sources panel and set Never pause here on line 4 (on the call to subscribe)
crbug-1401339-ignore-hidden.js to the Ignore Listcrbug-1401339-ignore.js in the Sources panel and set Never pause here on line 2 (on the call to someLibraryFunction)Set constructor throwing)
crbug-1401339-set.js in the Sources panel and set Never pause here on line 2 (on the call to the Set constructor)Promise reject callback)
crbug-1401339-reject.js in the Sources panel and set Never pause here on line 4 (on the throw statement)reject), click , and observe the result