Calling all those FReepers using an iPad

Vanity (sorry...) | 9/3/2015 | bk1000

[bk1000]

OK FReepers, I am becoming frustrated FReeping on my iPad. Ever since the most recent update to Safari (iPad 8.4), whenever I click to read an article and then click back to the forum page my browser goes to the top of the page instead of back to the point at which I clicked away. This makes for excessive scrolling just to get back to where I left off. Any of you iPad users experiencing this or is it just me? (I am logged in) I read other forums where this does not happen, and the boss says nothing has changed on FR. Aside from choosing another browser, do any of you have a remedy, or must I suffer in silence in hopes the next Apple update will rectify this intolerable first world delima?

[bk1000]

I'll be back to check any responses after my shower. Thanks in advance!

[AbolishCSEU]

Get a surface pro 3? but seriously, have not experienced this on other peoples ipads at work. . .

[Califreak]

Sorry, can’t help you.

I’m using a Kindle Fire.

[InterceptPoint]

Install Chrome.

[SeaHawkFan]

Don’t have that problem with my Galaxy Tab S.

[Oldexpat]

Same thing on my iPhone 4

[SeaHawkFan]

You could also open up an article in a new tab. Problem solved.

[Textide]

Exactly. Grab Chrome or another browser from the app store.

[Responsibility2nd]

Swordmaker has the Apple pinglist. And I forget who has the tech pinglist, but whoever has it is also a valuable resource.

[Cowboy Bob]

I have the same problem. 😡

[DanielRedfoot]

Make sure there isn’t a moose in your shower

[Lurkina.n.Learnin]

If you’d quit storing cheese in your shower that wouldn’t be a problem.

[Talisker]

You could also open up an article in a new tab. Problem solved.

That.

[jettester]

I get two different results depending n the route taken. If I hit the “Browse” link at the top of the story page, I will be returned to the top of the list of posts. However, if I hit the back arrow on the Safari toolbar, I will go back to the same spot I was at in the posting list. Try it and see if it works that way for you.

[ClockDoc]

Go to your Account > Preferences > Windows.Set it up like I did. "Windows Most browsers are capable of creating new browser windows. You may elect to allow the forum to create new browser windows when clicking marked links. Links which are programmed to open in another browser window will be marked with a ^.

Self Links will not be opened in new browser windows.

Blank Marked links will be opened in a new browser window.

Slave Marked links will be opened in a single "slave" browser window.

This allows one to leave open a list of articles in the master window, while reading the articles in a slave window."

[ADemocratNoMore]

Almost the same problem here... Things go along like they should with new articles opening up in new tabs and the Freep articles page stays right where I left it, until I switch to another app. When I come back to “Latest Articles”, sometimes the page will refresh to the most current, and sometimes it stays where I left off. Drives me up a wall.

[bk1000]

The slave window thing seems to work. Relief! Thanks!

[Swordmaker]

Freeper bk1000 is seeking advice on Freeping with his iPad from fellow iPad users. . . — PING!

Calling all fellow Apple iPad Freeper users
Ping!

The Latest Apple/Mac/iOS Pings can be found by searching Keyword “ApplePingList” on Freerepublic’s Search.

If you want on or off the Mac Ping List, Freepmail me.

[Drago]

I scrolled down the list of articles, clicked on one to read it, and then clicked the “back” button and I am still at the same point in the article list (about 1/2 way down). I am on iOS 8.4.1 and use the “Comments” tab on FR. Maybe I am not set-up the same as you on FR? (I am set to “50 articles per thread” & “100 threads per page”...use “Account/My Prefs” on FR to set).

[bk1000]

Ok, I tried the slave window thing. It seemed normal for a few minutes, hitting the back button going back to my place on the page. Then it started opening the slave window, as it should in regards to that setting. While that works, it is still somewhat cumbersome. I went back to the previous setting and my problem came back. So, it is not a problem 100% of the time, it seems.