jQuery Forum

Well, that's a setter, not a getter, so when you don't return anything from your function, something is wrong.

But if that's fixed, say by

1. return {top: coord.top + 10, left: coord.left + 10};

after your alert, there still seems to be a problem, as "index" seems always set to 0.

  -- Scott

>after your alert, there still seems to be a problem, as "index" seems always set to 0.

This is the point!
Why does the each() loop stops after the first index (index=0)?

It probably stops because you (implicitly) returned undefined rather than an object. That causes an error a bit further down inside jQuery. You should be able to see it with Firebug.

I agree the docs are a bit vague, I added a sentence that I hope clarifies things.

Hi Dave,
Thanks for your good job on the jQuery team.

The sentence added help me a lot.
I hope that someone provide an example in the docs
in order to help people to understand this method. 

But I'm still seeing an issue with the value of "index".

Just to make sure that JSBin isn't part of the problem, I have a standalone page at


The code is simple:

1. $('button').click(function () {   
2.     $('div').each(function() {
3.         $(this).offset(function(index, coord) {
4.             $(this).append($("<p>index:" + index + "<\/p>"));
5.             return {top: coord.top + 20 + (10 * index), left: coord.left + 20 + (10 * index)};
   
6.         });
7.     });
8. });

This should stagger the locations of the DIVs by 10 pixels each as well as add the index of the DIV in the collection of DIVs to the contents.  Instead, each one is listed as "index: 0", and they all move right by 20 pixels.

Something seems wrong with how index is passed to this function.  Am I missing something?

  -- Scott

Right, the instance ($('div')) is a jQuery object with four elements in (four divs). $(this)  is an instance with only one element in (one div, i.e. this). So, when you get an index of 0, that's actually correct, since within that collection, there's only one element.