W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2005

[whatwg] Canvas element

From: Dimitri Glazkov <dimitri.glazkov@gmail.com>
Date: Wed, 20 Apr 2005 13:28:33 -0500
Message-ID: <fb15ac21050420112840ff9300@mail.gmail.com>
I guess I am still struggling to grasp the concepts, so please be
patient with me.

Isn't the main functional value behind the canvas element is the
rendering context? If so, what is the significance of the canvas
element itself? Take away the behavior, and you've got yourself
another SPACER tag.

Why not allow creating rendering context on all block-level elements?
Why does the content have to contain information which block level
element is meant for drawing?

Also, I am having hard time the "fallback content" phrase. IMHO, it's
not the fallback content, it's _the content_ of the element. The
rendering context is presentation (hopefully, visual interpretation of
the content), and so are all functional behaviors that come with it.

However, if the rendering context is available on all block-level
elements, you can do some really neat stuff, such as using the content
of a block-level element as arguments for rendering. For instance, the
markup of an ordered list of links and images is transformed into an
image gallery.

:DG<

On 4/20/05, Anne van Kesteren <fora at annevankesteren.nl> wrote:
> Dean Jackson wrote:
> > Obviously this has pretty significant accessibility problems. There
> > is no content in <canvas> - it's just script. With document-based
> > graphics solutions, such as SVG and even Flash, there is real content
> > in the document. Accessibility tools can access that content and
> > provide alternate renderings (such as voice).
> 
> The content from the CANVAS element is the fallback content.
> 
>   <canvas>
>    ... alternate content ...
>   </canvas>
> 
> --
>  Anne van Kesteren
>  <http://annevankesteren.nl/>
> 
>
Received on Wednesday, 20 April 2005 11:28:33 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:40 UTC