W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2011

[Bug 13871] <video> behavior when setting currentTime to current playback position

From: <bugzilla@jessica.w3.org>
Date: Mon, 05 Sep 2011 14:56:46 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1R0abO-0006mi-Kn@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13871

Glenn Adams <glenn@skynav.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |

--- Comment #18 from Glenn Adams <glenn@skynav.com> 2011-09-05 14:56:43 UTC ---
It does not "work" when there is no media controller and no media loaded. My
position is that setting currentTime to itself in this scenario should be
considered a NO-OP, and not cause an exception due to lack of media.

Furthermore, there is an inconsistency regarding treatment in the case where
readyState is HAVE_NOTHING. In particular, we have:

4.8.10.6

"On setting, ... if the media element's readyState is HAVE_NOTHING, then it
must raise an INVALID_STATE_ERR exception; ..."

4.8.10.9

"1. If the media element's readyState is HAVE_NOTHING, abort these steps."

Why should the first above (4.8.10.6) raise an exception when the second
(4.8.10.9) does not?

I'm suggesting that in the case of HAVE_NOTHING, that setting currentTime to
itself should not raise an exception and should be a NO-OP. One might also make
the argument that setting currentTime to *any* value in the case of
HAVE_NOTHING should also be a NO-OP.

-- 
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 Monday, 5 September 2011 14:56:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:03 UTC