This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10054 - Suggestions for HTML5
Summary: Suggestions for HTML5
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P5 enhancement
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://techcrunch.com/2010/06/29/yout...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 02:44 UTC by ryan14
Modified: 2010-10-04 14:49 UTC (History)
4 users (show)

See Also:


Attachments

Description ryan14 2010-06-30 02:44:22 UTC
Here is what HTML5 needs:

1)Dynamically adjusting quality control and buffering.

2)Embed HTML5 video with annotations into external websites.

3)Play HTML5 videos in full-screen.

4)Standard for Camera and Microphone access from the browser.
Comment 1 Ian 'Hixie' Hickson 2010-08-28 04:50:20 UTC
> 1)Dynamically adjusting quality control and buffering.

I assume you mean of video? If so, this would be a transport issue, and out of scope for HTML.

> 2)Embed HTML5 video with annotations into external websites.

This is possible now. Just use an <iframe> and you can embed whatever you want.

> 3)Play HTML5 videos in full-screen.

That's presentational, so out of scope for HTML. (Work on this is ongoing.)

> 4)Standard for Camera and Microphone access from the browser.

Work on this is ongoing (see the <device> element in http://whatwg.org/html).


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: Rejected
Change Description: no spec change
Rationale: see above