Re: Mark up validation errors in BP Default theme
I’m amazed, interest in validation 
There are and have been ID errors for for ever and a day, I’ve mentioned them in the past and there’s probably a ticket lying around.
The repeated use of an Id is a common error when writing things like loops and sticking an id within one trouble is mid tier coders tend not to look at frontend output much.
Changing a DTD to get around validation errors is bad practice, new documents should always be written to a strict schema, this common use of Transitional is wrong but hey ho. What would make more sense especially given the use of attributes such as ‘roles’ (even though an XHTML spec and even though it’s actually only a working draft attribute) is a move to what is referred to as an HTML5 DTD or more accurately a DTD without a formal public identifier. TwentyTen has chosen to do this I would suggest BP can follow suite?
