W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2014

Re: Shadow Dom stuff

From: Mark Sadecki <mark@sadecki.com>
Date: Tue, 19 Aug 2014 11:30:24 -0400
Message-ID: <CAOego5MA+qcW_znGXCyPGTUfgjL4CY6Qc-GHtUddGur8xBqWTg@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
Cc: Rik Cabanier <cabanier@gmail.com>, "lisa.seeman" <lisa.seeman@zoho.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Hi Rich,

I agree with you and was also confused by Lisa’s original suggestion.  I
was hoping she would clarify if she indeed meant Shadow DOM, or fallback
content by making the distinction.  I think we should also make it clear
that Hit Regions now support associating that fallback content with regions
on the canvas for the purpose of informing the AAPI, which should alleviate
any concern she has about magnification.

Mark


On Tue, Aug 19, 2014 at 10:55 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:

> Mark,
>
> I understand that. While that is true, the approach that Lisa was talking
> about in concept is in concept what she was asking for so there is no need
> to have an alternative shadow DOM strategy.
>
> Rich
>
>
> Rich Schwerdtfeger
>
> [image: Inactive hide details for Mark Sadecki ---08/19/2014 09:22:23
> AM---I think its probably best to refer to it as fallback content]Mark
> Sadecki ---08/19/2014 09:22:23 AM---I think its probably best to refer to
> it as fallback content in canvas.  I know associate Shadow DOM
>
> From: Mark Sadecki <mark@sadecki.com>
> To: Richard Schwerdtfeger/Austin/IBM@IBMUS
> Cc: Rik Cabanier <cabanier@gmail.com>, "lisa.seeman" <lisa.seeman@zoho.com>,
> "public-canvas-api@w3.org" <public-canvas-api@w3.org>
> Date: 08/19/2014 09:22 AM
>
> Subject: Re: Shadow Dom stuff
> Sent by: mark.sadecki@gmail.com
> ------------------------------
>
>
>
> 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* <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* <lisa.seeman@zoho.com>> wrote: >
>    Hi Folks
>
>    From: Rik Cabanier <*cabanier@gmail.com* <cabanier@gmail.com>>
>    To: "lisa.seeman" <*lisa.seeman@zoho.com* <lisa.seeman@zoho.com>>
>    Cc: "*public-canvas-api@w3.org* <public-canvas-api@w3.org>" <
>    *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?
>
>
>



graycol.gif
(image/gif attachment: graycol.gif)

Received on Wednesday, 20 August 2014 07:02:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:57 UTC