It's not happening on our end.

So is there anyway to get the Infinite Scroll turned back off? Seeing as how I'd already done the steps to turn it off and yet it's reappeared?

Thanks for testing IBobi.

Strangely enough it is also happening from my laptop at home, a different machine to my work PC. Such an odd littler quirk!

At this moment, no. You're only options are the following.

Stop supporting FT, get ABP, and use the 'Block an ad on this page' for each of the modules.

enter "?styleid=17" at the end of each FT URL. (might as well just select the FT desktop option from the dropbox at the bottom :mad:)

or get the Tampermonkey extension and use that script that Spanish made.
Keep in mind the script still is a tad buggy and needs to be disabled after the first refresh as otherwise your browser will be sent into a refresh loop.

Something tells me the aadmins (despite this being a typo, I kinda want to keep this :D) disabled the 'opt out' function from actually working which means that despite making the style FT Desktop, it will no longer use it and revert to I.S.

We'll keep you posted. :mad::(:o

Update: And now suddeny certain threads revert to I.S. while others dont.. Weird.

I do not know why the script is refreshing screen constantly for you. Is it keep adding "?styleid=17" over and over? I already fix that issue for me.

I run Debian Jessie with Iceweasel & Windows 8.1 with the Firefox. Neither are having issue with the script.

Do you have the following in script?

if (window.location.href.toString().indexOf("?styleid =17") != -1) return false;
if ( ! /\?styleid=17$/.test (oldUrlPath) )

That is the part preventing it from continuously adding. It asking itself "Does URL already end in ?styleid=17, and if so, we will leave the URL alone."

Mine working great. Happy to help if you having any questions.

Copied the script verbatim into Tamper monkey on Windows 10 Aniversary Edition with the latest version of Chrome. For some reason, it just keeps testing the URL and even if it passes or has already updated the URL it'll just keep going

I haven't tried running this directly as a GreaseMonkey script, but just reading things over I think there's an extra space in the version in the wiki:

there's a space between styleid and =17 that should be removed.

Took the one directly from his post. However, I could see that being a fatal error as when it looks for that query in the URL it won't find it or add the proper path in place of it. Hence a refresh loop, though the space doesn't exist for my copy of the script. I'll review it again when I can and record the outcome.

Using iOS I tried replicating with Chrome, Safari. Nope, not for me.

You very correct. There should be no spacing there! I do not know how the space got to my posting, because it is not on my script.

The space ruins the argument completely. No wonder you having issues with it. I will correct the previous postings. One of you should correct the Wiki. I have not enough time / postings on the Flyertalk.

Thank you.

EDIT: For some reason the space is not able to be removed! Very strange. Some strange glitch.

Just checked my code and there was no spacing. :P

Something must be wrong on my end

EDIT: Never mind. Somehow it took three checks to see it. I must just be tired
​​​​​

There is something very weird going on. If you try to edit the wiki, you will find that the editor is quite sure there is no space there. I even did a cut'n'paste from another instance, and the result still magically gains a space when you view the wiki or copy from it. Lemme try wrapping it in a Code element...

Update: Much better?

I love how its gotten to the point where we're having to write scripts to get around this crap. Good job FT Admins :o:eek::rolleyes:

Not sure why, but after opting out of the first implementation I have not been affected by the second implementation at all. If this thread wasn't here I wouldn't know that people are still fighting it. :confused:

We have deployed significant fixes and testing to make sure that if you're opt'ed out you will not be using infinite scroll. It may be worth nuking the cookies in your browser and making sure the only option configured in Edit Options is "Disable Infinite Scroll, YES (Checkbox)" as suggested in the wiki.