I cannot answer the original question but I can say that I have come across (ok - created) cases where I needed to use id on an element that may be under the control of a style higher up in the hierarchy. My assumption is that classes are overruled by ids and perhaps to be on the safe side for CSS control (AJAX aside) this may be the reason?
On May 22, 12:28 am, Chris <[EMAIL PROTECTED]> wrote: > > Well if you are using AJAX it's necessary to have the id of an html > > That is not necessarily true! There are lots of ways for a programmer > to access their elements and update them through ajax. You should > checkout mootools.net. > > On May 21, 7:40 pm, Jashugan <[EMAIL PROTECTED]> wrote: > > > On May 21, 2:05 pm, Chris <[EMAIL PROTECTED]> wrote: > > > > I wasn't saying that django was performing bad practice, I was just > > > curious as to why id over classes. > > > > Thanks for the input. > > > Well if you are using AJAX it's necessary to have the id of an html > > element set, so that the javascript function would know which element > > to update. I find them pretty useful --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
