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 12:54:19 -0800
To: Charles Pritchard <chuck@jumis.com>, Maciej Stachowiak <mjs@apple.com>
CC: 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: <CB56F962.172C0%lrosenth@adobe.com>
This is interestingŠ

What makes you think that Canvas is (or should be) anything more than a
programmatically described image?


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"
>In all implementations, fixing Canvas seems to be about changing the
>object it inherits from.
>Canvas is not <img>, it's <input>.
Received on Tuesday, 7 February 2012 20:57:27 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:48 UTC