+1. I covered a similar question here:
http://article.gmane.org/gmane.comp.web.dojo.user/2307/
To sum it up: "disabled" is one of the most screwed up attributes. Try
to avoid it, if possible.
Thanks,
Eugene
Mike Shaver wrote:
On 1/10/06, Bob Ippolito <[EMAIL PROTECTED]> wrote:
Sounds like you've probably found a bug in Firefox. I don't see
anything in the code that should cause that behavior.
My reading of HTML 4 is that "disabled" is a boolean attribute,
meaning that having it present with any value[*] renders the input
disabled, and to re-enable it requires that the attribute is removed,
not set to the string "false" or "FALSE" or "0" or "no, thank you",
etc..
[*] Actually, it seems that the only legal constructs are <input
disabled> and <input disabled="disabled">, and all else is undefined.
http://www.w3.org/TR/REC-html40/intro/sgmltut.html#h-3.3.4.2
"Some attributes play the role of boolean variables (e.g., the
selected attribute for the OPTION element). Their appearance in the
start tag of an element implies that the value of the attribute is
"true". Their absence implies a value of "false"."
Setting the JS property .disabled to a false boolean value is
equivalent to removing the attribute via the DOM.
Mike
