I'm not sure what the correct term for this(!) - but the new feature that seems to have popped up on all major websites is that when you are scrolling down when you get to the bottom of the page the next page loads automatically. I would call it "seamless paging", but not sure what the true term is... but anyways, you know what I mean.....

...my issue is this:

When you scroll and the next page loads up, for some odd reason all the javascript is disabled on the new page... I'm not sure if this is a problem for just myself, or whether others are having issues - I use FFox 5 - but I have IE 8 and the same problem occurs in this too.

Does anyone have an explanation for this, or could someone possibly shed some further light on this ? Many thanks!

I would call it "seamless paging", but not sure what the true term is... but anyways, you know what I mean....

Not necessarily.

When you scroll and the next page loads up, for some odd reason all the javascript is disabled on the new page... I'm not sure if this is a problem for just myself, or whether others are having issues - I use FFox 5 - but I have IE 8 and the same problem occurs in this too.

And do we get to see this problem so we can at least try to debug it?

As Chris stated, there's not much we can do without any kind of information, like a link to the page.

My guess is that you have some kind of events on certain elements, that isn't triggered on the elements of the newly loaded content? I only recently noticed (althoug it has been there for some time) that the javascript library jQuery has a binding function called delegate() which allows you to bind event handlers to current and future elements. It basically means that the handler will also be bound to any element that may be loaded at a later time. You might wanna look into it.

If you're using some other library I'm sure it has some similar functionality.

for example.... if you scroll to the bottom of any thread longer than 2 pages on EVEN THIS WEBSITE a little box in the bottom right will say "loading next page", then after a sceond or so you can just simply keep scrolling down to read the next page, as opposed to clicking a link to the next page (as was the case before this rule can into existence) - what is the correct term for this type of 'seamless scrolling' ?

Anyway, when I get to the following page by using this method
-by scrolling, for some reason all the javascript is disabled on this next page. Why is this happening ?

Perhaps the usability god has intervened.

Originally Posted by PaulW

Perhaps the usability god has intervened.

....huh ?

....this 'scroll to next page' script has been around for a while, it's even in place on THIS site... go to any thread longer than 2 pages, scroll down to the bottom and you can get to the following page simply by scrolling.

But, again, on the following page, javascript is disabled... why is this ?

Originally Posted by offsmack

....huh ?

....this 'scroll to next page' script has been around for a while, it's even in place on THIS site... go to any thread longer than 2 pages, scroll down to the bottom and you can get to the following page simply by scrolling.

But, again, on the following page, javascript is disabled... why is this ?

Huh?? Not in any browser I've ever used here.

Originally Posted by chrishirst

Huh?? Not in any browser I've ever used here.

onsmack?

Re usability - can anyone seriously think this is a desirable behaviour?

I know what feature you're talking about. I do not know what it is called though. But again, it is probably some event you have registered on page load which of course does not affect elements that has not yet been loaded.

If we stop the discussion of what the effect is called, perhaps you'd like to get back to solving the issue? It would help if you gave us some information. What script is it that doesn't work on the loaded page? Again, a link would help.

My guess is that the OP had some kind of "accelerator" browser plugin/extension that preloaded "next page" links, and it has been disabled in the upgrade to Firefox 5.

Possibly this one

after a quick bit of "Googling".

The Google Image Search has this feature