111952 2013-03-10 20:29:33 -0700 WebKit uses the duration argument passed to AudioBufferSourceNode.start as the length of the buffer when looping 2013-03-11 10:34:53 -0700 1 1 1 Unclassified WebKit Web Audio 528+ (Nightly build) Unspecified Unspecified UNCONFIRMED P2 Normal --- 0 ehsan webkit-unassigned crogers oldest_to_newest 852028 0 ehsan 2013-03-10 20:29:33 -0700 The spec says: "Note that the default values for loopStart and loopEnd are both 0, which indicates that looping should occur from the very start to the very end of the buffer. " According to this, WebKit's behavior in this test case <http://people.mozilla.org/~eakhgari/webaudio/loop-webkitbug.html> is wrong. The looping sound when pressing both the first and second buttons should be the same. 852029 1 ehsan 2013-03-10 20:32:14 -0700 I can reproduce this in Chrome Canary, but it seems like WebKit Nightly cannot decode ogg files, so I cannot run the test there. 852032 2 ehsan 2013-03-10 20:34:39 -0700 Furthermore, the spec says: "in loop mode will continue playing until it reaches the actualLoopEnd position in the buffer (or the end of the buffer), at which point it will wrap back around to the actualLoopStart position in the buffer, and continue playing according to this pattern", which seems to suggest that the duration argument should be completely ignored in looping mode. 852053 3 crogers 2013-03-10 22:48:39 -0700 Let me have a look. There may be some work in the spec we need to do. 852348 4 ehsan 2013-03-11 08:32:08 -0700 (In reply to comment #3) > Let me have a look. There may be some work in the spec we need to do. Are you planning to change the spec for this? I'm currently implementing what the current spec says, and this just seems like a bug in WebKit. 852448 5 crogers 2013-03-11 10:34:53 -0700 (In reply to comment #4) > (In reply to comment #3) > > Let me have a look. There may be some work in the spec we need to do. > > Are you planning to change the spec for this? I'm currently implementing what the current spec says, and this just seems like a bug in WebKit. Let me take a closer look today