- From: ~:'' ありがとうございました。 <j.chetwynd@btinternet.com>
- Date: Mon, 10 Dec 2007 11:44:07 +0000
- To: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Cc: www-svg@w3.org
'foreignObject' can be a child of any container element, but must be a descendent of a switch? I don't know the SVG1.2 DTD, but would this express your suggestion? seems sensible to me for SVG1.1 regards Jonathan Chetwynd Accessibility Consultant on Media Literacy and the Internet On 10 Dec 2007, at 11:26, Dr. Olaf Hoffmann wrote: Jonathan, it is not a suggestion, I'm just guessing, why there has to be a switch around the foreignObject in 1.1. Of course, if you provide alternatives in a more clever way, you will not need it, but if there is no attribute for conditional processing in the foreignObject, the switch chooses it always, therefore it is not really a problem, only to put a switch around the foreignObject, even it is not useful in such a case. The switch here is more a help for the author to keep in mind, that a not supported format in foreignObject typically will cause accessibility problems for the user of the file. If this is avoided with other techniques, this is ok too, if not, maybe this helps authors to care about the problem at all ;o)
Received on Monday, 10 December 2007 11:44:27 UTC