- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 17 Feb 2009 21:21:05 +0100
- To: Maciej Stachowiak <mjs@apple.com>
- CC: Larry Masinter <masinter@adobe.com>, HTML WG <public-html@w3.org>
Maciej Stachowiak wrote: > But usually it is precisely when nested fragments are transmitted that > no MIME type is available. And even when a MIME type may be sent in such > cases, using a currently unknown MIME type is likely to lead to content > that won't degrade gracefully in existing UAs. For example, Atom <text> Yes. > elements have a MIME attribute that may only be "xhtml", "html" or > "text". Atom <content> elements may specify a MIME type, but XHTML is You mean <atom:content>, using the atomContent grammar production? That can have type=text/html/xhtml *or* type=someMediaType. See <http://greenbytes.de/tech/webdav/rfc4287.html#rfc.section.4.1.3>. > treated as a special case and the MIME type is given as "xhtml". Using a > custom MIME type will not display content the same way in existing feed > readers. The SVG <foreignObject> element does not allow a MIME type for Yes, that's likely. > ... BR, Julian
Received on Tuesday, 17 February 2009 20:23:47 UTC