Connect for Lemmy App

2785 readers

6 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago

MODERATORS

kuro_neko

[Client specifc anomaly] Navigating comment threads is extremely broken / Combined issues (self.lemmyconnect)

submitted 1 week ago* (last edited 1 week ago) by remotelove to c/lemmyconnect

3 comments fedilink hide all child comments

Edit: This is a weird thread, and might be a one-off. Maybe I have one of those users blocked and it's hiding the rest of the thread? I dunno, and I'll check. // It doesn't appear that I have any of those users blocked.

After opening my profile history, I can open a thread in my profile view. Clicking into a reply comment takes me to my comment on the post.

I cannot see the full comment thread when I view the full posts history on a post and trying to actually get to new comments is like trying finding the exit at IKEA.

Basically, I can't navigate to a thread to reply, and I had an awesome snarky comment prepared, but forgot it trying to get there.

Navigation behavior is so strange, either I have developed pre-release Alzheimer's, or Connect is bugged. (I don't discount either scenario.)

Sorry, I got jokes today.

top 3 comments

sorted by: hot top controversial new old

[–] remotelove 3 points 1 week ago

Same thread, different views:

[–] kuro_neko 3 points 1 week ago (1 children)

Hi, I'll take a look. How can I reproduce the issue you are seeing? I tried clicking through to the comment you mentioned from your profile but it seems like the full comment thread is there. Cheers!

[–] remotelove 2 points 1 week ago

It still happens on that one specific thread for me: I click on my original post in my profile and only see one reply, just like the pictures. However, in my profile, I see almost all of the thread, less the newest reply.

I can't reproduce what I am seeing on any other post but that one. Super weird. (Maybe we can chalk this one up to a cosmic ray permanently bit flipping something it shouldn't have.)

Relevant or not, that post was open when I updated to the new beta. I cleared my cache immediately after the update.

(Logically, there is something local I am overlooking because that thread works for you.)