- From: Karl Tomlinson <karlt+public-audio@karlt.net>
- Date: Fri, 21 Mar 2014 15:20:55 +1300
- To: KeonHo Kim <keonho07.kim@samsung.com>
- Cc: 'Chris Wilson' <cwilso@google.com>, 'Raymond Toy' <rtoy@google.com>, public-audio@w3.org
KeonHo Kim writes: > Well, I'm not sure my testing is related with that bug. > I tested blink and webkit were the latest and built locally. > The patch from the bug was applied both. I think it is not related this bug. Perhaps I don't understand. Please see my question below. > KeonHo Kim writes: > >> 1. When JS calls start(0) without setting a buffer. >> Blink/Webkit -> Immediately SourceNode's playback state changed to >> FINISHED_STATE, no DOMexception. >> Gecko -> Just slience, no DOMexception. >> >> 2. When JS calls start(0) with setting 'null' javacript object. >> Blink/Webkit -> DOMexception. "Cannot set to null" >> Gecko -> Just slience, no DOMexception. >> >> 3. After 1 or 2, Then set a buffer after calling start(0) Blink/Webkit >> -> Previsouly DOMexception causes error, no sound. >> Gecko -> Playing from beginning of buffer. There is no DOMexception after only 1 (without 2), so where does the DOMexception come from or what do you mean by "After 1 or 2"?
Received on Friday, 21 March 2014 02:21:58 UTC