- 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>
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 Tuesday, 7 February 2012 20:57:27 UTC