title: JavaScript print blocked by Chrome, Workaround?
body: <p>I know it has been discussed here before, yet I found no practical solution/workaround for this, I'm hoping if someone has any idea how to resolve this problem!</p>
  
  <p>Here's it is:</p>
  
  <p>If you try to call <code>window.print()</code> method frequently within a single page(as if a user clicks on a print button) in google Chrome, the browser throws a warning message in the console, stating:</p>
  
  <blockquote>
    <p>Ignoring too frequent calls to print()</p>
  </blockquote>
  
  <p>And nothing happens! After several seconds, things go back to normal and print dialog appears the moment you call <code>window.print()</code> command again! To make matters worse, the good Chrome folks use exponential wait time for a page that calls print command, meaning the more user clicks on a button to print, the more he has to wait for the print dialog to appear!</p>
  
  <p>This issue has been in chrome for quite some time (14 subsequent versions) and <strong>it is confirmed</strong> as being an <code>Area-UI</code> bug, I <a href="http://code.google.com/p/chromium/issues/detail?id=50186" rel="noreferrer">posted it again for google team</a> yesterday hoping if someone from Chrome team can verify when this incredible annoying feature is going to be fixed!</p>
  
  <p>However, what I'm looking for here is a workaround for this problem, is there <strong>anything</strong> I can do be able to get this working? My company is developing a highly transactional financial system with lots of reports that needs printing, and for just this one little glitch, the whole project is at risk of running in my favorite google Chrome browser!</p>
  
  <p>Update:</p>
  
  <p><a href="http://git.chromium.org/gitweb/?p=chromium.git;a=commitdiff_plain;h=8a86b38e5c593998369f4c3a789489e3fd9e8354" rel="noreferrer">Here's the code in Chrome browser</a> that causes this feature and it looks like that at least 2 seconds is needed before someone calls print command again, so a timer of 2 seconds interval in UI could possibly prevent getting into an infinite wait callback! any other thoughts?</p>