|
Is that what was causing those errors? I never made the connection between display errors and HTML.
HTML exploits are more caused by poorly designed browsers than the code itself. In theory if a browser parses correctly and follows all W3C standards it should be secure from any HTML exploits (as I'm sure you know). This naturally doesn't take into account any extensions or other markup languages such as PHP; all the same, I don't see HTML as being a huge security risk although if it's what was causing the threads to render incorrectly I'm still in favour of disabling it.
When it comes to browser exploits, I like to think of such things as Darwinian computing.
__________________
I wake up in the morning more tired than before I slept
I get through cryin' and I'm sadder than before I wept
I get through thinkin' now, and the thoughts have left my head
I get through speakin' and I can't remember, not a word that I said
- Ben Harper, Show Me A Little Shame
|