All the errors caught by the W3C are not exploitable. They are simply syntax warnings about how some elements might be rendered differently in X or Y web browser, and to ensure your website is compliant with W3C standards. :P
Whatever. It's something that should address concern.
Too bad FFR loads properly in every browser I've ever tried it in. Why the heck should we care if it's up to w3c standards or not? They shouldn't even call them errors, just warnings, since breaking xhtml standards doesn't necessarily break your page.
ps OP is posting about things he doesn't know anything about.
pps
Originally posted by Triplex72
Now it needs to tell us every error so we can exploit them.
let's all exploit the fact that ffr doesn't assign all its images an alt tag!! lolol!! Omg leet html hax0rs lmaoroflololbbq</sarcasm>
Comment