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 20078 - Remove <canvas> element and replace to image URI with dynamic rendering
Summary: Remove <canvas> element and replace to image URI with dynamic rendering
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-25 23:47 UTC by Alexei03a
Modified: 2013-01-23 11:19 UTC (History)
5 users (show)

See Also:


Attachments

Description Alexei03a 2012-11-25 23:47:28 UTC
I have idea with new Canvas system. This system are script-based.

<script type="application/javascript">
var canvas = URL.createCanvas("example", 150, 150); //Create Canvas 150x150 pixels
var ctx = canvas.getContext("2d"); //Can be WebGL
URL.fakeURL("http://broken.com/image.png", "canvas: example"); //Replace URL

//var url = URL.getOriginalURL("http://broken.com/image.png"); //Secret URL for direct to original link
//URL.fakeURL("http://broken.com/image.png", url); //You can retrive URL
</script>

<img src="canvas: example" alt="canvas">
<img src="http://broken.com/image.png" alt="canvas"> <!-- Faked, redirect to Canvas element. -->
<video src="canvas: example"></video> <!-- Can Be Controlable -->

My system need for dynamic animated images, dynamic videos and etc.
Comment 1 Robin Berjon 2013-01-21 15:59:20 UTC
Mass move to "HTML WG"
Comment 2 Robin Berjon 2013-01-21 16:02:07 UTC
Mass move to "HTML WG"
Comment 3 Robin Berjon 2013-01-23 11:18:18 UTC
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: none
Rationale: There is nothing described in this bug that cannot already be achieved using the existing stack.