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