Hard to tell without a specific test case but this was likely done intentionally. Please re-open if you have a specific test case.

Replying to [comment:1 john]:

Hard to tell without a specific test case but this was likely done intentionally. Please re-open if you have a specific test case.

Hi John,

it's definitively the bug.

test case is very simple, just test this on the site where is jQuery 1.4 ( #foo element doesn't exist ):

$('#foo').val() - return value is undefined

and then try

$('#foo').attr('value') - return value is null

And then try the same on the site where is jQuery 1.3:

$('#foo').val() - return value is undefined

and then try

$('#foo').attr('value') - return value is undefined

It's inconsistency, because the methods are doing the same, so they must return the same value when domelement doesn't exist.

Ah, it wasn't clear that the element didn't exist in this case, I can check in to that.

Replying to [comment:3 john]:

Ah, it wasn't clear that the element didn't exist in this case, I can check in to that.

Hi,

ok, John can you add me to the cc pls ? I forgot

I thought, that if I craete ticket, i will added to the CC automatically, this could be changed too.

Thank you

Fixed.

http://github.com/jquery/jquery/commit/abcc1a76ee2a6733177b2cd104bc32cee5443ec4