You're wrong, I'm afraid. Disabled elements are never sent. I don't
know any browser that does not adhere to this part of the HTML spec
(http://www.w3.org/TR/html4/interact/forms.html, read sections 12 and
13.2). Maybe you are confusing this with fields set to "display:none"
- David
Am 03.03.2006 um 16:35 schrieb Robin Haswell:
Because that's how form behaviour is defined? I don't know what
browser
you're using, but anything I've ever seen sends disabled elements
along
just like every other element.
In my experience the only deviation between a browser's normal
behaviour
and the Form.serialize function is the handling of multiple submit
elements.
-Rob
David Zülke wrote:
Does anyone know why Prototype adds disabled fields to the query
string
generated by Form.serialize()?
I have looked through the code, there is no way around that, I'll
have
to do it by hand.
Nevertheless, I find that behavior a little irritating. Any ideas why
it's implemented like this?
Cheers,
- David
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
