UNCONFIRMED 114923
AudioContext's currentTime doesn't start until the first source has been played back on it 
https://bugs.webkit.org/show_bug.cgi?id=114923
Summary AudioContext's currentTime doesn't start until the first source has been play...
Ehsan Akhgari [:ehsan]
Reported 2013-04-21 13:04:48 PDT
See the Blink bug I filed here: http://code.google.com/p/chromium/issues/detail?id=233977 UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20130417 Firefox/23.0 Example URL: http://jsfiddle.net/VxXRa/ Steps to reproduce the problem: See the test case URL. This test case creates a context, waits for half a second, then initializes a gain value increase from 0 at time 0 to 1 at time 1, and then starts playback. The current time reported in the first play() call is around 0 but it should be around 0.5, and the computed gain value is wrong as well (it should be around 0.5). Similarly for the second call to play(). What is the expected behavior? What went wrong? See above. Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Firefox Chrome version: 28.0.1478.0 (Official Build 194114) dev Channel: dev OS Version: OS X 10.8
Attachments
Add attachment proposed patch, testcase, etc.
Ahmad Saleem
Comment 1 2022-10-31 15:01:08 PDT
Resolved in following - https://src.chromium.org/viewvc/blink?revision=175026&view=revision I tried the test case from Chrome patch in following JSFiddle: Link - https://jsfiddle.net/hs1tmrcu/ but it is failing in all browsers (Chrome Canary 109, Safari 16.1, Firefox Nightly 109). Could be due to webkit prefixed one. As for JSFiddle from Comment 0, it does not produce any error etc. in Safari 16.1 and Chrome Canary 109.
Ahmad Saleem
Comment 2 2023-10-14 08:59:40 PDT
NOTE - the test was removed by Chrome / Blink in following commit: https://chromium.googlesource.com/chromium/src.git/+/faf1e5f751eb1b9005d05ad8fdfcaacb3fbd0e33
Note You need to log in before you can comment on or make changes to this bug.