W3C home > Mailing lists > Public > public-html@w3.org > February 2012

Re: Canvas as input vs. img (was Using @aria-describedby for long described image links [Was: Using an image map for long described image links [Was: Revert Request]])

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Tue, 7 Feb 2012 13:22:02 -0800
To: Charles Pritchard <chuck@jumis.com>
CC: Maciej Stachowiak <mjs@apple.com>, Steve Faulkner <faulkner.steve@gmail.com>, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, John Foliot <john@foliot.ca>, Matthew Turvey <mcturvey@gmail.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Laura Carlson <laura.lee.carlson@gmail.com>, Sam Ruby <rubys@intertwingly.net>, Paul Cotton <Paul.Cotton@microsoft.com>, HTML WG <public-html@w3.org>
Message-ID: <CB56FFD9.172D2%lrosenth@adobe.com>
How is this different than the various SVG-based image editors (etc.) that
have existed for years?  SVG elements, as well as the Canvas element (and
static <img>) all live in the DOM can be interacted with.

Input, to me at least, means not so much that the user can interact BUT
that the values from input will be read/submitted.

Leonard

On 2/7/12 4:09 PM, "Charles Pritchard" <chuck@jumis.com> wrote:

>Canvas is widely used for interactivity. The basic example in the HTML5
>specs is a checkbox example.
>
>
>The majority of Canvas uses are for UI, not simply for procedurally
>generated images.
>While you can generate some interesting images via script, a static PNG
>file makes more sense in distribution.
>
>I found that one out with an extension to a drawing application. I'm
>sure people in Adobe have seen this as well with things like illustrator.
>
>I was so happy that we were capturing all of the information needed to
>redraw an image. Then, I noticed that it took longer to redraw
>the image than it did to download a copy that had already been rendered.
>
>The name of this site is a little silly, but it gives a nice view of how
>programmers are using JavaScript in experimentation:
>http://badassjs.com/
>
>Notice, the Js1k demos are just programmatic images. Those are demos
>though, intentionally tricky and small.
>
>For actual apps, you have something like "Morning Star: An Impressive
>Audio Synth in JavaScript".
>http://badassjs.com/post/16764713909/morning-star-an-impressive-audio-synt
>h-in-javascript
>
>
>-Charles
>
>On 2/7/2012 12:54 PM, Leonard Rosenthol wrote:
>> This is interesting©
>>
>> What makes you think that Canvas is (or should be) anything more than a
>> programmatically described image?
>>
>> Leonard
>>
>> On 2/7/12 3:40 PM, "Charles Pritchard"<chuck@jumis.com>  wrote:
>>
>>> The issue with Canvas is that implementers did not realize that Canvas
>>> is in some abstract sense, a form element.
>>> "the best way to fix it is to make [it] more like a form control"
>>> https://bugs.webkit.org/show_bug.cgi?id=50126
>>>
>>> In all implementations, fixing Canvas seems to be about changing the
>>> object it inherits from.
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=495912
>>>
>>> Canvas is not<img>, it's<input>.
>>>
>
>
Received on Wednesday, 8 February 2012 20:03:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:43 GMT