9253 2010-03-16 15:13:04 +0000 Calling putImageData() should force browsers to render the canvas to screen, otherwise animations won't work. 2010-10-05 12:59:11 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#dom-context-2d-putimagedata P3 normal LC 1 contributor ian ian mike mjs public-html-admin public-html-wg-issue-tracking warcraftthreeft public-html-bugzilla oldest_to_newest 33618 0 contributor 2010-03-16 15:13:04 +0000 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 34208 1 warcraftthreeft 2010-03-31 03:49:31 +0000 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. 34452 2 mjs 2010-04-03 00:15:50 +0000 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. 34800 3 ian 2010-04-12 22:11:45 +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: Concurred with comment 1 and comment 2.