20584 2013-01-07 04:09:16 +0000 [HTML5] <media> element proposal 2013-01-25 01:37:53 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All RESOLVED WONTFIX P2 major --- 1 alexei03a eoconnor alexei03a eoconnor mike public-html-admin public-html-wg-issue-tracking robin public-html-bugzilla oldest_to_newest 80973 0 alexei03a 2013-01-07 04:09:16 +0000 I have idea to implement <media width="width" height="height"></media> element. Behavior similar to Canvas element. By instead of graphics you can fill other content. Differences of <div> element. - Supported interactivity. - JavaScript name - "HTMLMediaContainerElement". - Stretched like canvas element (proportional or not, depending on CSS). - The text does not change the size of an element, as its scalable model is similar to canvas, but not DIV or span. - "width" and "height" work not as CSS (img, video), but as canvas (i.e. own original size). - is not <div> replacement, but addition. Examples: <media id="media" width="300" height="150" style="width:600px;"> <!-- final size must be 600x300 --> <svg width="100%" height="100%"> ... </svg> </media> <media id="media" width="10" height="1" style="overflow: hidden;"> Text must be cropped. </media> <media id="media" class="video-player" width="$generated by script$" height="$generated by script$"> <!-- Work like <video> element. --> <div style="width: 100%; height: 100%; position: relative;"> ... </div> </media> 81696 1 robin 2013-01-21 15:58:48 +0000 Mass move to "HTML WG" 81814 2 robin 2013-01-21 16:01:34 +0000 Mass move to "HTML WG" 81907 3 alexei03a 2013-01-21 23:39:51 +0000 Dublicate of: https://www.w3.org/Bugs/Public/show_bug.cgi?id=20306 81994 4 alexei03a 2013-01-23 11:18:46 +0000 *** Bug 20306 has been marked as a duplicate of this bug. *** 82121 5 eoconnor 2013-01-25 01:37:53 +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: Rejected Change Description: No spec change. Rationale: As Robin said in bug 20306 comment 7, everything proposed can already be achieved using existing Web platform features.