Skip to main content

How to use the javascript call method in jQuery?



Is it possible to use the call method of javascript (as described in the [mdn documentation]) in order to pass the argument this ?





Having for example this code:







console.log(this);

$('#image_id').load(function () {

console.log(this);

});







I want that the second this (the one included in the load function ) refers to the same as the first one.





I've tried with







console.log(this);

$('#image_id').load.call(this, function () {

console.log(this);

});







But it doesn't work.





Thank you all in advance for any suggestion.


Comments

  1. You don't need call (or apply)

    You should do this instead:

    var that = this;
    console.log(this);
    $('#image_id').load( function () {
    console.log(that);
    });


    Javascript has lexical scoping, which means that the variable that is available to your callback, and has the value of where it is defined. In this case, that is defined to be this in the outer scope.

    ReplyDelete
  2. Yes you can .call jQuerys function with whatever, but that only affects that function. The function you pass is a separate callback function with this controlled by jQuery.

    You can use $.proxy to force a context of the callback.

    $('#image_id').bind( "load", $.proxy( console.log, console, this ) );


    If you wish to do more than logging it becomes more ugly:

    $('#image_id').bind( "load", $.proxy( function(){
    console.log( this );
    alert( this );
    }, this ) );

    ReplyDelete
  3. Have you tried this?

    console.log(this);
    $('#image_id').load(function () {
    console.log($('#image_id'));
    });

    ReplyDelete
  4. var self = this;
    $('#image_id').load.call(function(){
    (function(){
    console.log(this);
    }).call(self);
    });

    ReplyDelete
  5. Not like that, because you're not calling the callback. It's being called internally.

    You could use .bind though.

    console.log(this);
    $('#image_id').load( function () {
    console.log(this);
    }.bind(this));


    But it isn't available in older browsers. (This is native .bind(), not jQuery's.)



    jQuery has something that will work called $.proxy...

    console.log(this);
    $('#image_id').load.($.proxy(function () {
    console.log(this);
    },this));


    ...where the first argument is your function, and the second argument is the value you want to use for this in the callback.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex