7878 2009-10-10 13:59:42 +0000 An attribute to actually find out if something is playing would be nice (.isplaying). Unless I'm wrong currently you can't actually tell if something is playing without setting var with JS when you start to play and you can't go by the playback position s 2010-10-04 14:46:07 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#mediaevents NE P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28228 0 contributor 2009-10-10 13:59:42 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#mediaevents Comment: An attribute to actually find out if something is playing would be nice (.isplaying). Unless I'm wrong currently you can't actually tell if something is playing without setting var with JS when you start to play and you can't go by the playback position since it returns the value in seconds leaving a whole second where it should return 0 and thus you can't tell! An attribute that returns the playback state would also work, with 0 meaning not playing, 1 playing and 2 paused. Posted from: 86.154.2.114 28240 1 zcorpan 2009-10-11 08:44:48 +0000 (In reply to comment #0) > Section: http://www.whatwg.org/specs/web-apps/current-work/#mediaevents > > Comment: > An attribute to actually find out if something is playing would be nice > (.isplaying). Isn't .paused what you're looking for? > Unless I'm wrong currently you can't actually tell if something > is playing without setting var with JS when you start to play and you can't go > by the playback position since it returns the value in seconds leaving a whole > second where it should return 0 and thus you can't tell! .currentTime isn't rounded to whole seconds. > An attribute that > returns the playback state would also work, with 0 meaning not playing, 1 > playing and 2 paused. What's the difference between not playing and paused?