* Gisle Aas <[EMAIL PROTECTED]> [November 10 2004, 21:25]: > then closed the connection. Since there was no way for the server to > indicate any other Content-Type than text/html the <plaintext> tag was > introduced so that text files could be served by just prefixing the > file content with this tag. > > This was before the <img> tag was invented so luckily we don't have a > similar unclosed <gif> tag :)
Thank you very much for this enlightment! It explains everything! BTW, by that time I had even seen computers once or twice from far away :) > my current browsers both Konqueror and MSIE support this. Firefox > support it in the same way as <xmp>, i.e. it allow you to escape out > of it with </plaintext>. This Firefox behaviour is likely to have confused me. Look, what if I've got such a html: `<plaintext></plaintext><script>nasties;</script>'? HTML::Parser stops parsing after `<plaintext>' so that no interesting event is triggered on `<script>' tag and my sanitizer has no chance to rip out the nasties. Firefox (my 1st browser to test) happily resumes parsing after `</plaintext>' and that's the problem. Maybe it is the gecko people who are at fault. > > It results in weird effects for me as I write a HTML sanitizer for > > WebMail. > Howcome? Do you have a need to suppress this behaviour in HTML::Parser? Yes, I'd like to have an option to resume parsing after `</plaintext>' just as firefox does. As I understand the original intentions now I'll try to produce a patch. -- Alex Kapranoff, #!/usr/bin/perl -w $SIG{__WARN__}=sub{print substr("@_",-43+ord$_,1)for '6.823O1US90:350:739OJ;0:*'=~m}.}g},$}='PJlshrk';reset$}+43;