- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 Sep 2010 00:33:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10672 Summary: the media element onplay event is not always called when the user hits the play button Product: HTML WG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: silviapfeiffer1@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org This may be a bug in browser implementations of the spec, but because all browsers make the same mistake I believe it may be a spec bug that needs some clarifying text. When a media resource that has a @controls attribute has played through to the end and has thrown an "ended" event, browsers put the state of the @controls display to a "pause" button. As a user presses the "play" button again, the video/audio starts playing back from the beginning, but the "play" event is not raised again. I believe the reason for this is that the spec says to throw the "play" event when "paused is newly false", see http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#event-media-play . I don't believe this is sufficient, because upon "ended" the state of the media resource is not set to "paused". Also, the reason is that description of the steps to run after the "play()" function is called includes the following: "2. If the playback has ended and the direction of playback is forwards, seek to the earliest possible position of the media resource. Note: This will cause the user agent to queue a task to fire a simple event named timeupdate at the media element." I suggest also adding to this not to throw the "play" event. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 22 September 2010 00:33:47 UTC