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

[Bug 23663] Section 2.4.4 is not clear about whether it runs while seeking.

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Oct 2013 23:55:48 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23663-2486-3VpURHz65x@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23663

--- Comment #1 from Aaron Colwell <acolwell@google.com> ---
Section 2.4.4 does not run during seeking. It only runs during playback as the
first sentence in the section states. One thing that might make the seeking
behavior a little more obvious is to to change the "The media element waits for
the necessary media segments to be passed to appendBuffer() or appendStream()."
step in Section 2.4.3 to something more along the lines of "The media element
waits until an appendBuffer() or appendStream() call causes the coded frame
processing algorithm to set the HTMLMediaElement.readyState attribute to a
value greater than HAVE_METADATA." I think this would make it easier for the
reader to figure out how the element gets out of the HAVE_METADATA state during
a seek.

As for adding more informative paragraphs around the spec, the concensus in the
task force to similar requests in the past has been to keep the spec primarily
algorithmic when it comes to specifying behavior. There have been discussions
about creating a primer that includes more informative descriptions of the
behavior for folks that are not implementing MSE in a UA, but no one has
stepped forward to take on that work yet.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 28 October 2013 23:55:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC