W3C home > Mailing lists > Public > public-media-capture@w3.org > July 2013

[Bug 22692] New: <video> readyState should be HAVE_NOTHING before video arrives

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Jul 2013 08:54:28 +0000
To: public-media-capture@w3.org
Message-ID: <bug-22692-5753@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22692

            Bug ID: 22692
           Summary: <video> readyState should be HAVE_NOTHING before video
                    arrives
    Classification: Unclassified
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Capture and Streams
          Assignee: public-media-capture@w3.org
          Reporter: harald@alvestrand.no
                CC: public-media-capture@w3.org

In the current MediaCaptureAndStreams spec (4 July version), the following
description is given:

readyState    unsigned short    HAVE_ENOUGH_DATA

with comment: "The media is provided locally in real time, so there is always
enough data to play. (A MediaStream with no Tracks is equivalent to a
downloaded file that contains no playable data.)"

This gives surprising behaviour for remote media streams, which pop into
existence before the first frame of the video arrives. It's also potentially an
issue with cameras that have long initialization times.

I suggest that we change this to be:

HAVE_NOTHING   before the first video frame arrives
HAVE_ENOUGH_DATA   after the arrival of the first video frame

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 16 July 2013 08:54:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:18 UTC