I think its probably best to refer to it as fallback content in canvas. I
know associate Shadow DOM with the work that is being done in Web
Components.
mark
On Tue, Aug 19, 2014 at 9:31 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
> Canvas fallback content is a shadow DOM of sorts. I am confused.
>
>
> Rich Schwerdtfeger
>
> [image: Inactive hide details for Rik Cabanier ---08/15/2014 01:29:11
> PM---On Wed, Aug 13, 2014 at 9:57 AM, lisa.seeman <lisa.seeman@zo]Rik
> Cabanier ---08/15/2014 01:29:11 PM---On Wed, Aug 13, 2014 at 9:57 AM,
> lisa.seeman <lisa.seeman@zoho.com> wrote: > Hi Folks
>
> From: Rik Cabanier <cabanier@gmail.com>
> To: "lisa.seeman" <lisa.seeman@zoho.com>
> Cc: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
> Date: 08/15/2014 01:29 PM
> Subject: Re: Shadow Dom stuff
> ------------------------------
>
>
>
>
>
>
> On Wed, Aug 13, 2014 at 9:57 AM, lisa.seeman <*lisa.seeman@zoho.com*
> <lisa.seeman@zoho.com>> wrote:
>
> Hi Folks
> I was thinking that we need people to use the shadow DOM to make
> existing inaccessible Canvas implementations accessible and see how hard
> it is and how to explain how to do it to developers. (With the
> understanding that we can not get everything working yet - like
> magnification.)
>
> Is anyone working on this?
>
>
> Can you rephrase the question? Are you asking if someone is educating
> authors?
> Why would magnification not work?
>
>
