- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:29:26 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:29:51 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=20698#10) by Joe Berkovitz / NF on W3C Bugzilla. Tue, 02 Apr 2013 21:28:14 GMT The only apparent alternative is to do what our app has to do now, namely check the user-agent string to see if the OS is Android, and impose a fixed hardcoded time correction to AudioContext.currentTime for the purposes of understanding what the user is currently hearing. I think the idea of the application being able to know what is currently playing is pretty fundamental. But I don't want to belabor the point, knowing that so many other fundamentals also need to be implemented -- I just want to clarify why this matters. --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/12#issuecomment-24244126
Received on Wednesday, 11 September 2013 14:29:51 UTC