> and also because I thought that was the group consensus. One question
> I posed back then was, "Why would you want to serialize form elements
> in a way that does not correctly utilize the element state?" In other
> words, why submit controls that are not "successful"[1]? I guess your
> on-the
Hi Klaus,
> Isn't it a bit dangerous to alter jQuery's core in a plugin?
I hear what you're saying. I ended up using "serialize" partially
based on this note from John:
> I think form.js's .serialize() should supercede the serialize() in
> ajax.js. It's all around a better plugin. If we're seri
Klaus Hartl schrieb:
> Hi,
>
> I think it is not a good idea to overload the serialize method in the
> form plugin.
>
> If existing code relies on jQuery's serialize method, introducing the
> form plugin later will break your code. That of course is the case for
> Plazes. I cannot switch that,
Hi,
I think it is not a good idea to overload the serialize method in the
form plugin.
If existing code relies on jQuery's serialize method, introducing the
form plugin later will break your code. That of course is the case for
Plazes. I cannot switch that, because there are occasions where yo
