Jeff Schiller wrote: > On Mon, Mar 30, 2009 at 4:47 AM, Sam Ruby <rubys@intertwingly.net> wrote: >> As someone who routinely hand authors XHTML + SVG (and have done so for >> years), it disappoints me that this discussion so far has focused on the >> easily correctable issues. Ones that can be corrected in seconds by the use >> of the following web service: >> >> http://services.philip.html5.org/html-to-xhtml/ > > Well as another hand-author, I, for one, was not aware that service > existed until 4 days ago as part of this discussion. Therefore I am > not at all disappointed. In fact, quite the opposite. OK, so that was a good outcome. I remain disappointed that we have not moved on from that point. I actually thought that we had rough consensus that user agents (in particular browsers) which encounter inline SVG in content served as text/html is to treat the following as identical: <svg xmlns='http://www.w3.org/2000/svg'><circle r='20'/></svg> <svg><circle r=20></svg> Anybody want to put forward a concrete proposal as to what the DOM produced should look like in the second case? > Jeff - Sam RubyReceived on Monday, 30 March 2009 12:23:56 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:40:29 GMT