Loading more items for an activity feed that uses a global page counter

Posted on


I have this script which is for a news feed. A button click will grab more data from the server if there is any and then add it to the box. It doesn’t allow any more than 10 pages of results currently and how to properly store that page counter is what this question is about. loadMoreFeedItems() is the function attached to the onclick event of the aforementioned button.

<script type="text/javascript">

    window.page = 0;

    function loadMoreFeedItems() {
        var options = {};
        options.page = window.page;
            url: "home/feed",
            data: options,
            dataType: "html",
            success: function (data) {
                // Code to append the data received into the feed element
                // Code to hide "load more" button if window.page exceeds 10

    (function () {


So I did a little reading about global variables in JavaScript[1][2][3] and while this works, I got the vibe that this could be problematic, so I’m wondering if there is a better way. One alternative I thought of was to create some kind of hidden that stores the value in page rather than the browser, and then I’d modify/retrieve it using a jQuery selector, but that seems even dirtier.


This doesn’t have anything to do with ajax or the options exactly, just about “counting up” so i will show my example using a function called countUp which logs ever increasing numbers.

In short you can make page a member of countUp. You will recall that in javascript that functions are very much first class citizens and they are objects. Its easier to see this of course if you write your function definitions like:

var countUp = function () { /* .. function body */ }

So the variable countUp can have in it any number of members. The member we are interested in is page or more precisely this.page. So lets put this all together.

var countUp = function ()
    this.page = (typeof this.page !== "undefined") ? this.page : 0;

// logs 1 2 3

var options = {};
options.page = window.page;

This is kind of a dirty way to populate an object. It’s just like creating a blank array only to populate it’s indexes in the line after, like this:

var arr = [];
arr[0] = ...;
arr[1] = ...;

That’s a little gross looking, right? It would look a lot more clean if you just setup the page property as soon as the object was created, like this:

var options = {page:window.page};

Why are you storing the page variable in the window object? There is no need (at least with the code that is shown) to have that variable in scope for every other script in that page: only this script is accessing it, so it should be declared with var.

That would look like this:

var page = 0;

Now, when accessing the page variable, you no longer use window.page, you just use page.

Leave a Reply

Your email address will not be published. Required fields are marked *