1. subdom content should not be rendered at all. It has no visual location.
2. We need the new API Frank has created to provide the location of content
in the subdom. If we need finer granularity on individual characters we
will deal with that when we can get consensus on rich text editing. We
don't have that at this point.
I think we are jumping the gun trying to address the complex case right
now.
Rich
Rich
Rich Schwerdtfeger
From: Steve Faulkner <faulkner.steve@gmail.com>
To: public-canvas-api@w3.org,
Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, ChCharles Pritchard
<chuck@jumis.com>, Frank Olivier <franko@microsoft.com>
Date: 02/17/2012 03:54 AM
Subject: questions arising from AT vendor in regards to Mozillas
implementation of the canvas subdom
Hi all,
I would like to draw your attention to the following bug as it includes
questions about how the location of canvas subdom content is to be conveyed
to AT:
Expose alternative content in Canvas element to ATs
https://bugzilla.mozilla.org/show_bug.cgi?id=495912
any insights you may have would be benenficial
--
with regards
Steve Faulkner
Technical Director - TPG
