On Thu, Feb 26, 2009 at 10:19 PM, Ian Hickson <i...@hixie.ch> wrote: > On Wed, 25 Feb 2009, Robert O'Callahan wrote: > > > > Under "Once enough of the media data has been fetched to determine the > > duration of the media resource, its dimensions, and other metadata", > > after setting the state to HAVE_METADATA, steps 7 and 8 say > > > > > 7. Set the element's delaying-the-load-event flag to false. This stops > > > delaying the load event. > > > > > > 8. This is the point at which a user agent that is attempting to > > > reduce network usage while still fetching the metadata for each media > > > resource would stop buffering, causing the networkState attribute to > > > switch to the NETWORK_IDLE value, if the media element did not have an > > > autobuffer or autoplay attribute. > > > > I suggested HAVE_CURRENT_DATA would be a better state for these actions, > > and I still think so. These actions should not occur until the UA is > > able to display the first frame of the video. Authors would want the > > first frame of a non-autobuffered video to be visible, and the document > > load event should fire after the first frame is available by analogy > > with images. > > I've updated the note as per your suggestion. >
In step 7 you still stop delaying the load event after loading metadata. I still say we should keep delaying the load event until we reach HAVE_CURRENT_DATA. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
