[I'm CC-ing libwww@perl.org because HTML::Parser is theirs] * Blake Kaplan <[EMAIL PROTECTED]> [June 02 2005, 02:07]: > I just wanted to let you know that I'm checking full <plaintext> > support back into Mozilla for the upcoming Gecko 1.8 (and by extension > Firefox 1.1) release (details in > https://bugzilla.mozilla.org/show_bug.cgi?id=287990). You mentioned > that you'd submitted a patch to the PERL HTML::Parser module to > imitate our old behavior, so I thought I'd let you know.
Great you found time for this! I personally exploited this incompatibility and that's why I filed the bug long ago. Yes, there's now a non-default option 'closing_plaintext' to resume parsing after '</plaintext>' (as gecko did before your commit). Default HTML::Parser still ignores this closing tag. > On a similar note, while we now have "proper" support for <plaintext>, > it would be better to not have any support at all (as Boris Zbarsky > said in https://bugzilla.mozilla.org/show_bug.cgi?id=269116) > <plaintext> is obsolete (and doesn't even appear in the standard). So > I was wondering if it would be possible for the HTML::Parser to > deprecate and remove support for <plaintext> at some point in the > future [I'm not really sure who to contact about this, but since you > contribute...]. This is up to maintainer of HTML::Parser. As for me, I don't think gecko will be better without support for '<plaintext>'. HTML is a heap of hacks and the web is full of bad HTML, old software and malicous people. -- Alex Kapranoff, $n=["1another7Perl213Just3hacker49"=~/\d|\D*/g]; $$n[0]={grep/\d/,@$n};print"@$n{1..4}\n"
