agreed, this is not the best way to handle this issue. I'm considering it as a temporary work-around to a technical issue with the underlying cms.
On Feb 24, 9:49 am, the_woodsman <[EMAIL PROTECTED]> wrote: > Seriously, if you want this to scale when you have more names in the > future, it'd be better to do at least some of the work server side, if > you can- perhaps put all names in a span with class personName, then > play around with those elements in JQ on the client side.
