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
> 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 Ma
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 func
>>and in 2008, does it really matter?
If you are managing a major media related site every inch counts in
order to have a fast and deliverable page!
I wasn't saying that django was performing bad practice, I was just
curious as to why id over classes.
Thanks for the input.
On May 21, 3:32 p
On Wed, May 21, 2008 at 3:16 PM, Chris <[EMAIL PROTECTED]> wrote:
> Why does django by default output html id's in form fields? I thought
> that it was good practice to use the class attribute in child elements
> of an html form and to only use id on your container (parent) element
> such as the f
Why does django by default output html id's in form fields? I thought
that it was good practice to use the class attribute in child elements
of an html form and to only use id on your container (parent) element
such as the form element. I think I read somewhere that classes are
faster to create an
6 matches
Mail list logo
