Does Each DIV Need To Be Unique?

[font=verdana]Asking the difference between a div and a class is like asking the difference between a car and blue … they aren’t even the same type of thing. Pretty much every time you’ve asked about a div, what you should be asking about is an ID.

A <div> is an HTML element, and is a generic container for text, images and other elements, used to group them together or as a hook for styles and scripts where there’s nothing more specific that would be suitable (eg a paragraph or heading).

IDs and classes are used to apply styling or scripts to <div>s and other elements.

The following discussions and articles may be helpful…

http://www.tizag.com/cssT/cssid.php
http://css-tricks.com/the-difference-between-id-and-class/

…but in a nutshell, for styling purposes, IDs and classes are used in similar ways, but there are a few key differences.

[list][]An ID can only be used once on a page, a class can be used again and again. So if you want to apply the same styling to multiple items, you’ll need to use a class.[]An ID is more specific than a class, so if you have conflicting style rules (where two rules giving contradictory styles apply to the same element) then a rule that uses an ID will usually outrank a rule that just uses classes.
[]You can only apply one ID to an element, but you can apply multiple classes to an element (even if you’ve given it an ID as well), so you could have <div id="section1" class="article box">, where ‘article’ and ‘box’ are separate classes.
[
]You can use an ID for an internal link (eg <a href=“#section1”> jumps to the item with id=“section1”.
[*]If you’re using it as a Javascript hook, getElementByID is better supported than getElementByClass, so you should use an ID.[/list]

So if you’re not using the last couple of points there, then yes I would recommend changing homesocialtopcell to a class.[/font]