I’ve finally created my activity feed page and it looks ok. I am just stuck at one bit. Hope you chaps can help.
If a user wants to post a comment on a wall feed item, I take the user to a new page where the original post appears and the user can post a comment/reply. The user than has to push the ‘back’ button at the top of the page. Once this button is pushed, the user goes to the top of the activity feed page as opposed to that specific feed to which he/she replies.
I created some 10 feeds and 5 replies per feed so you can imagine how far the scrolling takes the user on to. But after posting a reply, when a user goes back, the top of the page comes up and not the exact feed to which a user replies.
Hi @arun, there isn’t currently the option to ‘scroll to a post’ or to navigate to an anchor on a screen (or, indeed, create such an anchor). Maybe a good opportunity to post to the feature requests?
It seems that others are facing the same situation as well, including me. Like @adam16ster has pointed out, the scroll position is correct at first, but then snaps back to the top. Maybe this is due to rendering or something, but either way it would be very difficult without locking a scroll position. Funny thing is how I didn’t notice this issue until now. For my app, with lots of items on screen, it will probably me make-or-break as many my clients who will use the app are notoriously prone to nagging
Just a heads up, something I found by accident is, if you change the transition from your initial page to ‘slide up’ and then click back on the following page, it does seem to maintain scroll position. In my case i’m clicking a list item initially. Works on iPhone at least (PWA). I haven’t tested other transitions but hope this helps
This is going to be a major problem if users are redirected to the top of the feed after posting a comment on a post that was way down the feed. They will uninstall and forget the app. I would. Let’s upvote this or I’ll have to pay someone to do it. We can’t release without this being fixed. I spent a over a year on the UI design and to have this issue, is upsetting. It’s a basic feature that we need right away.
