- From: Jon Ferraiolo <jonf@adobe.com>
- Date: Fri, 7 Apr 2006 14:42:53 -0700
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: <www-svg@w3.org>
Anne, Your option #1 (textContent) sounds the best to me, especially since the uDOM does not provide APIs to access CDATA. (Only Element and Document nodes are supported.) Jon -----Original Message----- From: Anne van Kesteren [mailto:annevk@opera.com] Sent: Friday, April 07, 2006 7:10 AM To: Jon Ferraiolo Cc: www-svg@w3.org Subject: Re: [SVGMobile12] SVGT12-207: <title> does not define what the title is On Fri, 07 Apr 2006 16:00:51 +0200, Jon Ferraiolo <jonf@adobe.com> wrote: > And keep in mind we are talking about the SVG *Tiny* specification > which is targeting constrained devices. Virtually no one is going to > use anything except plain text for titles. In fact, we should all be > ecstatic if content developers use titles at all. > > The plain text case is the one that we should make sure works. One > approach is to say that it is OK for Tiny user agents to just extract > the strings from the text nodes and concatenate them together. If you > put markup within <title>, the author cannot be sure what will happen, > so don't do that if you want it to work interoperably across Tiny UAs. > We can consider more advanced features for <title> in subsequent > versions or more powerful profiles (e.g., Full). So what the SVG Tiny specification should define is how to extract the text version of a <title>. I see two options that make sense: 1. Use textContent; 2. Go through childNodes and ignore everything except CDATASection and Text nodes. I guess this could be a small paragraph at the end of the definition of the <title> element. -- Anne van Kesteren <http://annevankesteren.nl/> <http://www.opera.com/>
Received on Friday, 7 April 2006 21:43:16 UTC