17610 2012-06-27 01:20:42 +0000 suggest video element support non-buffered video play 2013-03-11 16:39:48 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT RESOLVED NEEDSINFO P2 normal --- 1 eric.sun robin mahdishams00 mike odinho philipj public-html-admin robin silviapfeiffer1 public-html-bugzilla oldest_to_newest 69445 0 eric.sun 2012-06-27 01:20:42 +0000 During development of some cloud service using html5, we find it is benefitial to send frame to video element for display and interaction. But when we study the internal implementation, it seems that video element must decode metadata, then buffer enough amount of data for display. Even if we set the video attribute autoplay, we can not prevent the buffer behavior of video element, should it be better if video can support a non-buffer mode? I think video game, video interaction will be very popular in the future. We have consider using Canvas, but a little more complex, and we need direct video to Canvas using JS, which is not good for real time. Can anyone give some hint or comment? 69728 1 odinho 2012-07-09 08:44:24 +0000 I think maybe WebRTC is something you're looking for? 70239 2 contributor 2012-07-18 07:11:59 +0000 This bug was cloned to create bug 17884 as part of operation convergence. 71318 3 philipj 2012-07-23 14:29:39 +0000 The buffering behavior is controlled by the preload attribute, currently having the values none, metadata and auto. It sounds like preload="none" might be what you want? 73879 4 robin 2012-09-14 10:43:41 +0000 Eric: do Odin and Philip's suggestions address your concern? 84247 5 robin 2013-03-11 16:39:48 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Additional Information Needed Change Description: none yet Rationale: it's unclear whether the existing suggestions address the bug to the OP's satifaction or not.