Also reported in Apple BugReporter as #4363014 - - - Bug already regressed. Reproducible with any WebKit release after 412.7. Bug originated somewhere between 412.7 and 416.13. JavaScript action used to cause an audio object on a page correctly returns audio controller to beginning of audio timeline, but audio continues to play. Multiple itterations of the audio will play if a command is sent to play the audio when the user becomes confused as to why the audio controller says it has stopped, when in fact it has not. Use of the controller itself is normal, functionality there is not inhibited in any way. But if a custom button is designed to provide a more visually appealing interface for the audio playback a JavaScript must be used. Tested with QuickTime 6 and QuickTime 7. Tested with Windows Media 9 and Real Media Player for OS X as well. All exhibit the behavior. I have example content as well that will be uploaded with this bug.
Cannot upload example content, filesize is too large. 1176kb. If content is desired for regression or testing contact me via email or by calling me at 513-293-1539.
The HTML and JavaScript alone, without the media file, will probably suffice as a testcase. Please attach them to this bug or provide a URL for them.
Updated with URL. Content was created for Walt Disney Company for internal training purposes. Do not distribute the URL. Content was developed using a content authoring tool known as Lectora (www.trivantis.com), and published using HTML. Their developers are confident that they have used only standards based code in the content published from their tool.
Issue occurs on the second page of the content. Sorry, should have specified that in the last update.
I successfully reproduced the issue in release Safari but I am unable to reproduce in "TOT" (the latest development version). I think this was either bug 5365 or bug 5306. Reporter, please download the latest WebKit nightly build from http://nightly.webkit.org/ and verify that the bug is fixed in the nightly. If not, please re-open the bug. I am clearing the URL field since it wasn't supposed to be public. *** This bug has been marked as a duplicate of 5365 ***