Quote:
Originally Posted by m7sen
Why do not you reform w3c errors and warnings ! :down:
must tell everyone use this product if they use it with vbseo
they will get errors and warnings from w3c
i will tell all my friends
bad product :down:
your product is joke if the pro version have the same problem !!!
|
The reason why is that the time and labour cost involved in doing so massively outstrips any benefit gained. Our customers would prefer we spend 100 hours creating new features for our product than checking over every line of code to make sure every single '&' is picked up perfectly by W3C validity tools. None of the 'errors' showing have any impact on users of the site.
If I can make an analogy, would you rather be treated by the surgeon with the neatest stitching, or the one who has spent more hours practising actual surgery? Personally, I would prefer the latter.
I hope that explains why we do not see W3C validation as a high priority for our limited time.
Kind Regards
Iain