I'm noticing that the test server is closing the connection sooner than the 3 second window for firing a stalled event.
Chromium interprets a preemptively closed connection as an error and we stop playback before getting to fire a stalled event.
On Safari/QuickTime I noticed the following:
1st load/uncached: page stalls for a bit but then plays 3s of the video but in a loop but it doesn't fire ended events nor is loop attribute set
2nd+ load/cached: video never plays, calls to play() don't do anything but setting currentTime makes the video play in a loop again
Anyway, one way of working around the early connection close is to add a stallFor parameter to make the sure that we wait long enough, but I admit it does feel like we're sweeping the issue under the rug so I'm open to suggestions!
Created attachment 110764 [details]
Comment on attachment 110764 [details]
Clearing flags on attachment: 110764
Committed r97376: <http://trac.webkit.org/changeset/97376>
All reviewed patches have been landed. Closing bug.