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 9253 - Calling putImageData() should force browsers to render the canvas to screen, otherwise animations won't work.
Summary: Calling putImageData() should force browsers to render the canvas to screen, ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 15:13 UTC by contributor
Modified: 2010-10-05 12:59 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-03-16 15:13:04 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-context-2d-putimagedata

Comment:
Calling putImageData() should force browsers to render the canvas to screen,
otherwise animations won't work.

Posted from: 143.97.2.35
Comment 1 Sirisian 2010-03-31 03:49:31 UTC 
Yeah this doesn't make any sense. If you want to render an animation use a timer and store the state in variables performing the animation in the timer callback.
Comment 2 Maciej Stachowiak 2010-04-03 00:15:50 UTC 
If putImageData forced a synchronous flush to the screen, it would actually break some animations, e.g. ones which want to do a putImageData plus other drawing atomically. It's not a good idea to try to animate with a busy loop anyway, the right way is to use timers.
Comment 3 Ian 'Hixie' Hickson 2010-04-12 22:11:45 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: no spec change
Rationale: Concurred with comment 1 and comment 2.