Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The first thing that comes to my mind when i hear the word ID is that it’s something which is unique, Well it is in the case of ASP.NET server tags. But it seems that there is nothing wrong using same id’s for multiple tags if it’s not a server tag. So is it a problem at all?
Your DOM selectors will fail.
document.getElementByIdwill only return the first match, and different javascript libraries might to their own funky stuff depending on the parsing they do on your selectors. plus, different browsers might also do their own when usingquerySelectorAll.I’d recommend to use a
classattribute instead of anid, even if you do not intend to address the elements with javascript. Repeating the sameidon a page is still invalid code and will lead to uncertain results.