title: HTML5 audio - currentTime attribute inaccurate?
body: <p>I'm playing around a bit with the HTML5 <code>&lt;audio&gt;</code> tag and I noticed some strange behaviour that has to do with the <code>currentTime</code> attribute.</p>
  
  <p>I wanted to have a local audio file played and let the <code>timeupdate</code> event detect when it finishes by comparing the <code>currentTime</code> attribute to the <code>duration</code> attribute.</p>
  
  <p>This actually works pretty fine if I let the song play from the beginning to the end - the end of the song is determined correctly.</p>
  
  <p>However, changing the <code>currentTime</code> manually (either directly through JavaScript or by using the browser-based audio controls) results in the API not giving back the correct value of the <code>currentTime</code> anymore but seems to set it some seconds ahead of the position that's actually playing.</p>
  
  <p>(These "some seconds" ahead are based on Chrome, Firefox seems to completely going crazy which results in the discrepancy being way bigger.)</p>
  
  <p>A little jsFiddle example about the problem: <a href="http://jsfiddle.net/yp3o8cyw/2/" rel="noreferrer">http://jsfiddle.net/yp3o8cyw/2/</a></p>
  
  <p>Can anybody tell me why this happens - or did I just not getting right what the API should do?</p>
  
  <p>P.S.: I just noticed this actually only happens with MP3-encoded files, OGG files are totally doing fine.</p>