ansaurus

Question

Why isn't this .change event firing in jQuery?

Answer 1

A:

Try this instead:

$(function() { //Shortcut for $(document).ready();
   $("#SearchFor").change(function() {
     alert($(this).val());
   });
});

Also, best to use script tags like this still:

<script src="../../Scripts/jquery-1.3.2.js" type="text/javascript"></script>

See this question for more detail: Why don’t self-closing script tags work?

Nick Craver 2010-02-04 20:24:38

Crockford advises against providing the "type" attribute at all.

Pointy 2010-02-04 20:28:00

@Pointy - Who? It's a required attribute: http://www.w3.org/TR/REC-html40/interact/scripts.html#h-18.2.1

Nick Craver 2010-02-04 20:31:15

Douglas Crockford - http://javascript.crockford.com/script.html

Pointy 2010-02-04 20:40:14

@Pointy - While that's mostly good advice, I wouldn't leave out the type attribute. Simple rule for me: Having it won't cause any issues, *not* having it can (and **will** in older browsers).

Nick Craver 2010-02-04 20:46:47

The reason it's problematic is that you've got to worry about what your server is going to return. In other words, the attribute on the tag second-guesses the MIME type that'll be returned in the HTTP request to actually fetch the script. In my opinion the attribute on the tag was simply a design mistake.

Pointy 2010-02-04 21:00:02

Also, since Netscape 2 the default interpretation of script content has been Javascript, so there's no realistic concern with "older browsers". If you find a browser where the default type isn't Javascript or where the lack of the attribute fails, I suspect that a vast number of other things would be likely to fail too.

Pointy 2010-02-04 21:01:25

@Pointy - I can't put it better than this: http://weblogs.asp.net/bleroy/archive/2007/09/17/should-i-use-a-type-attribute-on-script-tags.aspx pay attention to the comments for a lot of great points.

Nick Craver 2010-02-04 22:39:52

Well the conclusion in that article is "be standards-compliant, oh except don't". The attribute is required, but the standards-compliant values don't work. Again, the whole thing seems like a mistake, so slavish standards-compliance seems pointless to me. *Chacun à son goût.*

Pointy 2010-02-05 00:24:53

Answer 2

A:

should just be

$(function() {
  $("#SearchFor").change(function() {
                alert($(this).val());
        });
    });

Pointy 2010-02-04 20:25:02

Answer 3

+3 A:

Your document.ready statement is incorrect. Should be:

$(document).ready(function() { 

    ...

});

KP 2010-02-04 20:26:46

oh /facepalm thanks :)

shogun 2010-02-04 20:28:33

While the other two answers are correct, this one actually answers the question.

TheJuice 2010-02-04 20:29:25

Yeah extra set of eyes always helps...

KP 2010-02-04 20:30:25

Answer 4

A:

$document is not a valid reference to a jQuery object, try

$(document)

Notice the parenthesis

Cody Caughlan 2010-02-04 20:27:03

Answer 5

+1 A:

You wrote

$document.ready(function() {

But should be this instead:

$(document).ready(function() {

Seb 2010-02-04 20:27:05

ansaurus

tags:

views:

answers:

Why isn't this .change event firing in jQuery?

related questions