- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 6 Jun 2013 17:45:29 +0900
- To: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>
- Cc: www-svg <www-svg@w3.org>
On Thu, Jun 6, 2013 at 5:39 PM, Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de> wrote: >> <svg:textArea> has several logistical problems: >> >> 1) Its name conflicts with the HTML <textarea> element, and it compounds >> this by having different functionality than <textarea>; this will make >> it confusing for authors, and makes parsing SVG in HTML (a very common >> case today, with script libraries like D3.js and Raphael) much harder (I >> suspect browser vendors would not implement this, because of the parsing >> conflict); > > Compared to XHTML textarea it has another name ;o) > As you know, there are already elements with different > meaning and the same name in SVG and (X)HTML. > And it is in another namespace, therefore no real problems. > And textArea is already in the SVG namespace, therefore > a little bit late now to care about such HTML5-specific problems. > If authors want to to provide meaningful content, they should > not use HTML-tag-soup ;o) The four name clashes are a major headache for author-friendly parsers. New ones will come into SVG over my dead body. ~TJ
Received on Thursday, 6 June 2013 08:46:16 UTC