W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2009

[Bug 7878] 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

From: <bugzilla@wiggum.w3.org>
Date: Sun, 11 Oct 2009 08:44:48 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Mwu2q-0007Qf-MI@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7878


Simon Pieters <simonp@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
           Keywords|                            |NE
         Resolution|                            |NEEDSINFO




--- Comment #1 from Simon Pieters <simonp@opera.com>  2009-10-11 08:44:48 ---
(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?


-- 
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 Sunday, 11 October 2009 08:44:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 11 October 2009 08:44:52 GMT