New HTML filtering code
It is a bit more pedantic about correct HTML. It'll rebuild all HTML tags in your message now to make sure the tag is correct and not allow anything we don't want into it. You may see things like border=0 turned into border="0".
Also, it validates all URL's where applicable. This means no more javascript.
It may also reorder the attributes while rebuilding the tag. This is just a quirk of the algorithm I implemented. It's harmless.
If for some reason the code doesn't like your HTML tags, or you just casually use < and > in your message, it will convert the brackets into the appropriate SGML entities, instead of ignoring them or stripping them out like before.
I've done some extensive testing of the code and it seems to be working correctly in all cases now. If you see anything weird, please follow up.
I'll be scrubbing all of the existing messages and all of the existing signatures soon. I've been testing my code on the existing signatures and have found hundreds of mistakes people have made. Be forewarned that your signature may break soon if you have invalid HTML.
<img src="" border="" alt="">
<font color=""></font>
<b></b>
<i></i>
<u></u>
<tt></tt>
<big></big>
<small></small>
We check href and src for a valid URL, target can only be a couple of common ones (_top, _new, etc) and border can only be a number.
Any suggestions for more? The new code can control attributes much better now. I'm thinking maybe <pre></pre>?
The only thing is it can't handle forcing of nesting of tags (ie tables) correctly. It'll handle arbitrary nested tags, just won't force a specific ordering.
Trending Topics
Bringing Audi to Life for Audi Fans



