- From: Joe D Williams <joedwil@earthlink.net>
- Date: Wed, 3 Mar 2010 08:28:19 -0800
- To: "Dan Connolly" <connolly@w3.org>, "Karl Dubost" <karl+w3c@la-grange.net>
- Cc: <public-html@w3.org>
typo; sorry. I meant text/html. > What is happening to this source code case when you send it with a > proper text/plain on the server side? > > <object > data="http://example.org/source/example.html" > type="text/plain"> > <p>Source code of the > <a href="/source/example.html">HTML file</a></p> > </object> > Whatever the mime, if the data could not be fetched and displayed as an object contenxt, then the text would be shown. If the resource could be run, then the <.p> would never appear. Good Luck, Joe ----- Original Message ----- From: "Dan Connolly" <connolly@w3.org> To: "Karl Dubost" <karl+w3c@la-grange.net> Cc: <public-html@w3.org> Sent: Wednesday, March 03, 2010 7:24 AM Subject: Re: Re-registration of text/html On Sun, 2010-02-28 at 08:46 -0500, Karl Dubost wrote: > Le 25 févr. 2010 à 16:57, Dan Connolly a écrit : > > Serving a document as text/plain licenses processing > > by user agents as specified in this spec. > > (specifically, section 8.2 Parsing HTML documents) > > Documents served as text/plain *should* conform > > to the HTML 5 syntax, but consumers should beware > > that existing content varies considerably; note especially > > section 11 on Obsolete features. > > > text/plain? I might misunderstand. typo; sorry. I meant text/html. > What is happening to this source code case when you send it with a > proper text/plain on the server side? > > <object > data="http://example.org/source/example.html" > type="text/plain"> > <p>Source code of the > <a href="/source/example.html">HTML file</a></p> > </object> > > > -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ gpg D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Wednesday, 3 March 2010 16:28:56 UTC