- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Aug 2011 06:14:34 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13060
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch
--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-11 06:14:33 UTC ---
A resource delivered as a mutipart/replace package containing a series of JPEG
payloads is no a single image; it's a whole series of images.
As currently specced, a <canvas> element's drawImage() method would do nothing
if invoked with an <img> using an infinite multipart/replace resource, because
such an image is never fully decodable. In fact, how to handle
multipart/replace isn't really defined by the spec at all even for regular
<img> purposes.
I guess what I should do is update the tasks queued by the "update the image
data" algorithm so that if the resource is actually a multipart/replace
resource, each subresource updates the image data and the image is marked as
fully decodable as soon as the first one is found. Then it should all just
work.
Does that seem ok?
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 11 August 2011 06:14:35 UTC