- From: Rick <graham.rick@gmail.com>
- Date: Thu, 8 Aug 2013 14:17:06 -0400
- To: Philip Rogers <pdr@google.com>
- Cc: Cameron McCormack <cam@mcc.id.au>, www-svg <www-svg@w3.org>
- Message-ID: <CAGDjS3fWWxeQWx=gE9x7sct6o5RgbXH1kgZhk_zXcoi098M+OA@mail.gmail.com>
On Thu, Aug 8, 2013 at 12:56 PM, Philip Rogers <pdr@google.com> wrote: > Rick, > > Both Chrome and Safari use an HTML5 parser for SVG in HTML and an XML > parser for standalone SVG. The HTML5 parser is much more lax in terms of > error handling and I prefer wrapping my SVG examples in HTML for that > reason. > You mean WebKit then. I use WebKit standalone, a lot. Now I'm curious to see if I have been missing better error handling. I'll check it out. Thank you Philip. > > > On Thu, Aug 8, 2013 at 7:46 AM, Rick <graham.rick@gmail.com> wrote: > >> >> >> >> On Thu, Aug 8, 2013 at 8:16 AM, Cameron McCormack <cam@mcc.id.au> wrote: >> >>> Hi Rick, >>> >>> If you are lucky, adding a <link xmlns="http://www.w3.org/1999/**xhtml<http://www.w3.org/1999/xhtml>" >>> rel="favicon" href="..." type="..."/> to your SVG document will work. I >>> haven't tested it. >>> >> >> Thanks Cameron. >> >> I haven't tested it on all browsers. I think I tried two and they failed. >> >> It works if you use an XHTML wrapper, which I could just do. >> >> I see this as a pretty basic requirement, provide a way for people to >> visually file their SVG documents like they do and have done with all their >> other web documents for over a decade. Because it works. >> >> Does everyone wrap their SVG in XHTML? I don't think you should have to >> do that to be a first class web doc. >> >> Cheers! >> >> -- >> *Once ... in the wilds of Afghanistan, I lost my corkscrew, and we were >> forced to live on nothing but food and water for days. >> -- W. C. Fields* >> >> > -- *Once ... in the wilds of Afghanistan, I lost my corkscrew, and we were forced to live on nothing but food and water for days. -- W. C. Fields*
Received on Thursday, 8 August 2013 18:17:34 UTC