I'm aware of that, but you must be logged in. The default behavior if you're not logged in is to have infinite scrolling. That's annoying.

I am unable to find where I can stop this infinite scroll madness. There are no options for me for changing Settings under "My Flyertalk"
Help!

As it says in the wikipost at the top of this thread:

• myflyertalk
• edit options
• infinite scroll -- disable
• save

I don't have that option either!

"Thread Display Options" is a grouping of options:


https://cimg2.ibsrv.net/gimg/www.fly...2772289807.png


At the bottom of that grouping is the following:


https://cimg1.ibsrv.net/gimg/www.fly...427c102ade.png

Agreed.

Disable or make it not the default option. Flyertalk is unusable with it enabled, who likes having their screen jump around to random parts of a thread?! Sometimes doesn't even let you scroll since it automatically kicks you to a different post. Yes I can disable in when I'm logged in, but I tend to use computers that I don't want to login to. And I'd imagine new users visiting Flyertalk for the first time aren't going to put up with a broken website for long.

Why is there no option in edit options to disable infinite scroll? (to merge)
 

Flyertalk is annoying enough to navigate as the site is a jumbled mess, but what makes it even harder is when you are just trying to scroll up to read a wiki, and it keeps loading new comments you dont want to see. The solutions online talk about disabling infinite scroll (which i believe i've done previously), but that's not an option in my settings anymore. This site is pretty much unusable for me

I actually love infinite scroll but it is hard to get to the wiki once you're down in the weeds. For example, Google searches often pick up the nth post of a thread.

IIRC there used to be a "Go to Wiki" button but maybe that on the paginated site layout. Is there any way to navigate the wiki aside from clicking the "first" button? Obviously scrolling up doesn't help!

I like Infinite Scroll in general, but Search doesn't seem to work within such a thread. That gives me no way of re-finding a comment of mine after subsequent activity puts it somewhere in the middle of the thread.

Are you referring to "Search Within Thread" or Ctrl(Apple)+F/"Find in Page"?

agreed, I used infinity scroll ever since it was introduced but disabled today. The wiki page is impossible to get to when auto-scroll kicks in unless you press the page number for page navigation

​​​​
If you type in "1" in the "Go to Page" box in the lower right corner, it will take you directly to the wiki.

If you open the menu in the upper left corner and scroll to the bottom, you should see a "Full Site" option.

Mobile skin is infinite scroll only.

allow disabling the infinite scroll in threads
 

I have looked but didnt see a way to disable infinite scroll, sorry if it exists.

Infinite scroll really makes getting back to the top of the page annoying. Would be great to have the option to just have the site act like a normal forum in this regard.

Go here: https://www.flyertalk.com/forum/prof...do=editoptions

Click "Disable Infinite Scroll" and hit "Save" at the bottom

The issue is apparently that you cannot disable infinite scroll on the mobile view. I like the mobile view just fine other than that.

Any advicr?

You can use the mobile view, or you can use the desktop view and disable infinite scroll. That's the choice.

Why not offer this option on both views? We already have page controls on the mobile view...

My belief is that no one at IB spends any meaningful amount of time on the FT mobile site as a user, i.e. looking for travel info/discussions, doing searches, and actively participating on a daily or near-daily basis. Or if they do, they don't apparently care about reading the information that has been organized in wikis, or advanced thread searches, or anything else that requires being at the top of a thread.

Because the alternative is that a frequent user of the FT mobile skin puts up with all of this on a daily basis and thinks to themselves "yup, nothing at all wrong with this experience! Great job folks!" and thinks this is awesome UX.

Just trying to scroll to the top of a long thread, or back out of one, is awful on mobile...

I second this. Would be nice if one could change that.

If you just click the double arrows either way at the bottom of the screen, they'll automatically take you to the first or last page.

Or type in the first or last page number at the bottom of the screen, you can navigate there pretty quickly.

Yes, I'm aware of that. It doesn't solve the underlying issue though.

What exactly is the underlying issue, then?

When on mobile, the (infinite?) scrolling means that as soon as I scroll up and reach a certain "border" (i.e. where the site switches to a new set of posts) I completely lose track of where I started off. Usually this entails that the site jumps over a few posts which I need to scroll down to again.

Mine seems to randomly take me to another page even when I’m not scrolling (just trying to read a post).

I cannot replicate this

Under the thread display page, I do not see the option to disable infinite scroll anymore. How do I go with disabling it?

https://www.flyertalk.com/forum/prof...do=editoptions

Select "disable infinite scroll". Save at the bottom.

Infinite scroll on iOS makes the site unusable.

I've got the setting turned off but apparently this only works on the full version.

This is such a rubbish feature 95% of the time. If I load page "8" it then proceeds to load page "7" immediately and kick me half way up page 8. I went to page 8 on purpose!!!!!

PLEASE LET ME TURN IT OFF ON MOBILE!!!! Otherwise I'll simply stop using this forum it is THAT irritating.

Infinite scroll issues
 

Hello,

I think there are a couple of issues with infinite scroll.
- The like buttons haven't worked outside of the first pages that gets loaded, I think that's a known issue for a while.
- Marking posts as read as you scroll used to work but stopped a few weeks back (maybe 3 or 4). The workaround at the moment is, if there are multiple pages to read, to refresh the page when you get to the last post.
- I haven't been able to reproduce it recently (for lack of a post to reply to) but quick reply also failed last week which I think is related.

The first 2 are true on both desktop and mobile for certain.

I have a feeling that this is linked to javascript code not loading properly via infinite scroll, but I haven't dug any further. I could have a look if you think it might help.

Do you know about these?

Thanks

I haven't ever heard about the last two, so I'll take a look. Do you have particular threads they aren't working on?

It's all threads, I reproduce it on every thread I read since some time early to mid August. I'm signed up to quite a few of them on the BAEC board. I click on the new post arrow in my subscribed threads, and if I have posts on more than the first page I haven't read, only the first one is marked as read, the others aren't unless I refresh when I reach the last page.

I have noticed this frequently as well in recent weeks, feels like maybe around the time of the last update. It *may* be more likely to occur if I navigate away from the page quickly (I am a fast reader :) ) -- maybe whatever code it is that updates the "last read" pointer hasn't had enough time to be triggered or something. It feels like if I let it sit for a while before closing the page then I have this problem less. But also it could just be that I'm refreshing the page and this is placebo effect.

BTW although I feel like the issue I reported here: https://www.flyertalk.com/forum/tech...oad-times.html

has gotten *slightly* better, but only slightly -- for example on a thread of let's say 100 pages, it will randomly load page 30 (say), and you can briefly see those old posts (often years old) but then a second or two later it will jump to the actual first new post that might be on page 99 or 100, which IMO observationally supports my blackbox testing hunch here:

I mention it here because there may be a common thread of, what all the heck is the page load code doing, and might it be over-bloated and time for some optimization...