Skip to main content

!Friendica Support I'm then and now experiencing a strange behaviour in Friendica web (frio): Having a post with a longer thread below, I expand the thread and interact (like, reshare) with some messages in there. If I do that, more than just once a few moments after that interaction the display somehow seems to "scroll" or "jump" or reposition, not sure by which pattern, in some cases the comment I interacted with being scrolled to back or bottom, in some cases scrolling up or down the thread. Seems to happen on all browsers I tested so far, and somehow feels related to clicking, say, a "like" thumb and the background activity triggered by that being finished. Am I the only one to see that? Anyone else? This isn't really a big deal but a bit annoying as you again and again lose track of where you were.
!Friendica Support
in reply to Kristian

Matthias ✔
Matthias ✔
• •
Do you have any plugins running in your browser?
I have noticed this extremely in combination with Tampermonkey.
in reply to Matthias ✔

Kristian
Kristian
• •
Nope. Currently using Brave in a private Tor window, with all of these disabled. That was a first idea too but it doesn't seem to be the culprit here.
in reply to Kristian

MsDropbear42 [venera] 🐨♀🌈🐧​🦘
MsDropbear42 [venera] 🐨♀🌈🐧​🦘
• •

@Kristian It happens to me a lot, & tbh it's pretty exasperating. Because of it i frequently lose my reading place in my network timeline, & need to manually scroll up & down to "rediscover" where i was. This does not happen in my Masto* account.

I have a [non-technical, entirely guessed] hypothesis. I suspect that "interacting" with the subject post somehow "triggers" #Friendica to then check for new items in the fediverse, to insert at the top of my timeline, which then abruptly displaces my "reading point" down by the number & size of new posts added.

* If true, i would mention this; Mastodon allows users to avoid this unpleasant inconvenience, by an optional #SlowMode setting in Preferences. When enabled [which many Masto users do, afaik], new toots are prevented from automatically entering the top of the timeline & displacing it down, instead generating a small notification atop the timeline noting the availability of new content. Then, at a time chosen by the user, they can manually click that actionable notice, which loads the new content. I really wish we had this in Friendica!

#friendica #slowmode @Kristian
in reply to Kristian

Michael Vogel
Michael Vogel
• •
It happens with Posts that are expanded, because the system updates the post after you sent a "like". This is not a wanted, but an expected behaviour.
in reply to Michael Vogel

Kristian
Kristian
• •
That's sort of what I expected. GIven the explanation, I assume there's no easy fix for that?
in reply to Kristian

Michael Vogel
Michael Vogel
• •
It would be easy for someone who can do frontend stuff, I guess.
in reply to Michael Vogel

Kristian
Kristian
• •
Ok, thanks... added an issue for that - https://github.com/friendica/friendica/issues/13994 - in case someone skilled enough is around to look into that.
in reply to Kristian

Hypolite Petovan
Hypolite Petovan
• •
@Kristian The main problem is that the collapsing and expanding is done entirely client-side, so when we request an updated version of the thread, the server can’t know which posts were collapsed/expanded at the time of the interaction, resulting in a display discrepancy.
@Kristian
⇧