Looking at the Sizzle code:
filters: {
enabled: function(elem){
return elem.disabled === false && elem.type !== "hidden";
},
disabled: function(elem){
return elem.disabled === true;
},
This honestly doesn't make sense. :not(:enabled) != :disabled and
:enabled != :not(:disabled) like it logically should be.
This will exclude any type="hidden" elements. It seams natural to
believe that $('#formid :enabled') should return any form input that
would be submitted if the form were submitted. Afact in a project at
work using the custom framework I use a selector much like that when our
.ajax call gets a form input as it's data parameter (ie: It goes through
the enabled inputs and extracts the value of all the named ones and
converts it into the urlencoded data string).
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
-Nadir-Point (http://nadir-point.com)
-Wiki-Tools (http://wiki-tools.com)
-MonkeyScript (http://monkeyscript.nadir-point.com)
-Animepedia (http://anime.wikia.com)
-Narutopedia (http://naruto.wikia.com)
-Soul Eater Wiki (http://souleater.wikia.com)
Jacob wrote:
> In a normal form POST, a form element with <item type="hidden"> will
> send those hidden elements as request variables alongside visible
> enabled variables.
>
> In jQuery 1.3.1, filtering on $(":enabled", myForm) will only find
> VISIBLE enabled elements, which is changed since jQuery 1.2.6. I don't
> believe this change is correct. Is there an explanation for this
> change? Can we revert it to the earlier behavior, or is there a good
> alternative?
>
> Thanks for your time,
> Jacob
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
