Brandon, Dave,
Thank you for the summaries. We have had a LOT of discussion about 1.1
over the last month+ and maybe it is time to create a wiki page the
keeps a running list of decisions and issues. Links to bugs would be
cool also.
This would be really good for all. I would avoid rehashing a
On 12/7/06, Dave Methvin <[EMAIL PROTECTED]> wrote:
> I think the outcome of the past month's discussion was this:
>
> 1) .val() will be dead in jQuery 1.1, as will all of the macro properties.
>
> 2) It's easy to get the value of a non-input element with .attr("value").
>
> 3) Mike Alsup added fie
> On 12/7/06, Erik Beeson <[EMAIL PROTECTED]> wrote:
>> Oh no! Not again! We had a 40 response long discussion about this LAST
>> month. It started here:
>>
http://www.nabble.com/%24.val%28%29-limited-in-functionality--p7351019.html
>
> Perhaps it is time to merge the form plugin's method with
>
On 12/7/06, Erik Beeson <[EMAIL PROTECTED]> wrote:
> Oh no! Not again! We had a 40 response long discussion about this LAST
> month. It started here:
> http://www.nabble.com/%24.val%28%29-limited-in-functionality--p7351019.html
Perhaps it is time to merge the form plugin's method with the .val()
m
Great! Thanks Mike.
Mike Alsup wrote:
>> I guess i could make a plugin that extends .val to suite my needs.
>
> The form plugin handles this. Use "fieldValue" to get the value of a
> form element.
>
> http://jquery.com/dev/svn/trunk/plugins/form/form.js?format=txt
>
> _
> I guess i could make a plugin that extends .val to suite my needs.
The form plugin handles this. Use "fieldValue" to get the value of a
form element.
http://jquery.com/dev/svn/trunk/plugins/form/form.js?format=txt
___
jQuery mailing list
discuss@jqu
Hehe, well i won't bring up the discussion again :)
I just thought it was strange that .val didn't have any "built in" logic
form form elements.
I guess i could make a plugin that extends .val to suite my needs.
Best regards
Christian
Erik Beeson wrote:
> Oh no! Not again! We had a 40 respon
Oh no! Not again! We had a 40 response long discussion about this LAST
month. It started here:
http://www.nabble.com/%24.val%28%29-limited-in-functionality--p7351019.html
--Erik
On 12/7/06, Christian Bach < [EMAIL PROTECTED]> wrote:
Hi,
Perhaps I'm doing something wrong, but when using .val()
I think that it's correct. Have you tried to select checked elements
using something like:
$("[EMAIL PROTECTED]:checked").val();
2006/12/7, Christian Bach <[EMAIL PROTECTED]>:
> Hi,
>
> Perhaps I'm doing something wrong, but when using .val() on check boxes
> they method seems to always return '
Hi,
Perhaps I'm doing something wrong, but when using .val() on check boxes
they method seems to always return 'on' disregarding the state of the
checked attribute.
Is this correct behavior?
The tests are made with the latest "stable" release of jQuery and not the
svn version.
Best regards
10 matches
Mail list logo