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 8802 - The drawImage function should be able to handle animated pictures by adding an additional parameter 'restart'. If restart is set to true, then the first frame is loaded - otherwise, it moves one frame forward from the last time drawImage was called on the
Summary: The drawImage function should be able to handle animated pictures by adding a...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (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-01-23 23:30 UTC by contributor
Modified: 2010-10-04 14:30 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-23 23:30:41 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#images

Comment:
The drawImage function should be able to handle animated pictures by adding an
additional parameter 'restart'. If restart is set to true, then the first
frame is loaded - otherwise, it moves one frame forward from the last time
drawImage was called on the same picture. And when the last frame is reached,
the behaviour depends on the image's loop settings.

Posted from: 82.122.7.67
Comment 1 Ian 'Hixie' Hickson 2010-02-13 11:35:35 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: At the risk of missing the obvious, what's the use case? Is this just to make drawing animated sprites easier? It seems like in most cases animated sprites are going to have to jump around from animation to animation and in practice are unlikely to just spin around a single set of frames... in fact, it seems frankly easier just to write the 4 or 5 line function to do animation manually, and just yank the frames from a larger sprite image where the frames are all given in a long strip.