W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2013

Re: [whatwg] A question about the drawimage() canvas function

From: Glenn Maynard <glenn@zewt.org>
Date: Fri, 1 Mar 2013 16:40:56 -0600
Message-ID: <CABirCh-6UkHLanotXA8cu4_CCoE3ZDKdrSDtJwG1PE7tS5tPxA@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
Cc: "Kang-Hao \(Kenny\) Lu" <kanghaol@oupeng.com>, 王铁套 <wang.tietao@outlook.com>, WHAT Working Group <whatwg@whatwg.org>
On Fri, Mar 1, 2013 at 4:24 PM, Rik Cabanier <cabanier@gmail.com> wrote:

> I think it should say:
>> 1. If the image argument is an HTMLImageElement object in the broken
>> state, then throw an InvalidStateError exception, return aborted and abort
>> these steps.
>> 2. If the image argument is an HTMLImageElement object that is not fully
>> decodable, or if the image argument is an HTMLVideoElement object whose
>> readyState attribute is either HAVE_NOTHING or HAVE_METADATA, then return
>> bad and abort these steps.
>> 3. (original step 2, unchanged)
> I think original step 2 should be updated to *CanvasImageSource* instead
> of HTMLImageElement. This is certainly how webkit implemented it.

That sounds fine too, as long as you mean in addition to the above and not
instead of.

(If you mean instead of, I disagree.  As far as throwing or not throwing
based on the broken or loading state question, it seems like WebKit should
change to match FF and IE, since those two already agree, and WebKit also
agrees with one of the two drawImage overloads tested.)

Glenn Maynard
Received on Friday, 1 March 2013 22:41:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:20 UTC