title: Force chrome to refresh a page while debugging with breakpoints
body: <p>If I have a breakpoint in a loop or frequent interval I can't refresh chrome without forcing a reload with <code>ctrl-r</code>.</p>
  
  <p>Hitting <code>F5</code>/clicking the refresh button will do a normal refresh, loading just the modified content, unless the debugger has paused on a breakpoint in which case the debugger continues. Holding/spamming <code>F5</code> just cycles through breakpoints and I can't refresh the page after spotting a bug and making code changes. I'd prefer not to do a full reload (<code>ctrl-r</code>) because I have images and other content that get cached and don't need to be re-downloaded.</p>
  
  <p>One solution is to close the debugger, refresh and then open the debugger. However, the JS then gets a chance to run before the debugger is back up. I then have to refresh <em>again</em> so the JS runs from the beginning.</p>
  
  <p>Has anyone found a workaround?</p>
  
  <p>It could be just me, but I frequently want to make changes to my code <em>and</em> debug it at the same time.</p>
  
  <hr>
  
  <ul>
  <li><p>Refresh: <kbd>F5</kbd></p></li>
  <li><p>No, actually refresh: <kbd><img src="https://i.stack.imgur.com/m24x4.png" alt="hammer"></kbd>+<kbd>F5</kbd>?</p></li>
  </ul>