Comments on: A Strong Test for Markup In Titles & Summaries http://www.elharo.com/blog/software-development/web-development/php/2007/03/17/a-strong-test-for-markup-in-titles-summaries/ Ranting and Raving Tue, 02 Dec 2008 21:12:10 +0000 http://wordpress.org/?v=2.6.3 By: Mokka mit Schlag » Is This a Security Issue? http://www.elharo.com/blog/software-development/web-development/php/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55377 Mokka mit Schlag » Is This a Security Issue? Sun, 18 Mar 2007 11:59:56 +0000 http://www.elharo.com/blog/software-development/web-development/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55377 [...] Mokka mit Schlag » Web Development: Blogging: PHP « A Strong Test for Markup In Titles & Summaries [...] [...] Mokka mit Schlag » Web Development: Blogging: PHP « A Strong Test for Markup In Titles & Summaries [...]

]]> By: Ed Davies http://www.elharo.com/blog/software-development/web-development/php/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55056 Ed Davies Sat, 17 Mar 2007 20:40:10 +0000 http://www.elharo.com/blog/software-development/web-development/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55056 Whatever with respect to the Atom stuff - this page looks bloody awful viewed directly in Firefox. I haven't followed through what's happening fully but, as far as I can see having downloaded the page with wget, the problems start with the double quotes in the double-quote delimited title attribute of the h1 element. Whatever with respect to the Atom stuff - this page looks bloody awful viewed directly in Firefox. I haven’t followed through what’s happening fully but, as far as I can see having downloaded the page with wget, the problems start with the double quotes in the double-quote delimited title attribute of the h1 element.

]]> By: Elliotte Rusty Harold http://www.elharo.com/blog/software-development/web-development/php/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55048 Elliotte Rusty Harold Sat, 17 Mar 2007 19:48:45 +0000 http://www.elharo.com/blog/software-development/web-development/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55048 The problem is that escaped HTML isn't just text. I get bug reports every time I try to treat it as just text. Escaped HTML is only really just text when you really do want to see the markup as text. For example, it's completely legitimate to include escaped in HTML a web page about HTML. However escaped HTML in other contexts just makes life difficult. I can't parse it; and even if I double parse, it's more than likely malformed. The problem is that escaped HTML isn’t just text. I get bug reports every time I try to treat it as just text. Escaped HTML is only really just text when you really do want to see the markup as text. For example, it’s completely legitimate to include escaped in HTML a web page about HTML. However escaped HTML in other contexts just makes life difficult. I can’t parse it; and even if I double parse, it’s more than likely malformed.

]]> By: John Cowan http://www.elharo.com/blog/software-development/web-development/php/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55046 John Cowan Sat, 17 Mar 2007 19:13:21 +0000 http://www.elharo.com/blog/software-development/web-development/2007/03/17/a-strong-test-for-markup-in-titles-summaries/#comment-55046 Escaped HTML isn't evil as such; it's just another text format. It's <i>unmarked</i> escaped HTML that's evil, as in the RSS variants, where you have to guess whether the person at the other end will interpret what you send as plain text or HTML. I have an RSS feed that represents a bunch of plain-text documents: consequently I have to first convert the plain text into HTML, then escape the HTML. In Atom, of course, I just mark the summary as plain. Escaped HTML isn’t evil as such; it’s just another text format. It’s unmarked escaped HTML that’s evil, as in the RSS variants, where you have to guess whether the person at the other end will interpret what you send as plain text or HTML.

I have an RSS feed that represents a bunch of plain-text documents: consequently I have to first convert the plain text into HTML, then escape the HTML. In Atom, of course, I just mark the summary as plain.

]]>