Why am I having a battle with the scroll bar in the messages/1on1 chat section?
It has a mind of its own as in I can't move it myself. I mean the one that specifically scrolls through the messages in a single chat, not that scrolls through the entire webpage. It won't let me scroll all the way down... to see the newest message I have to click on another convo and then come back to the convo that has the new message for the scroll bar to be low enough for me to see the new message. This happens both as a listener and member. The scroll bar is fine everywhere else on the site I'm using chrome and will try a new browser soon... does anyone know what's going wrong?
@brightTangerine5186
i have no clue what's wrong but it happens to me too...
@brightTangerine5186 I'm having this battle too, in Chromium (similar to Google Chrome).
Why is it happening? I think that's a complex multi-layered question.
Philosophically, I think we're having this battle because 7 Cups has never gone along with the user-centric model of software development that most tech startups adopt. This was confirmed in the podcast we learned about recently, if you know what to listen out for (from around 1:06:44). So fixing a bug like this that adversely impacts users of the site has low priority compared to, say, tinkering with emoji.
Structurally, I think we're having this battle because no one is really in charge of quality, overall. I know @EvelyneRose is working hard to improve quality in some limited ways, and I believe that's important work, but I don't think anyone at 7 Cups can decide that this kind of bug will be fixed and then make the fix happen.
Procedurally, I think we're having this battle because the community isn't involved in reviewing design documentation (or no design documentation even exists), and the community isn't involved in testing. So a mixture of design faults and coding errors get pushed into production code without adequate safeguards.
Technically, I don't yet know exactly what's going wrong. It's too difficult to chat to a member and debug it at the same time. The design appears to be that you can scroll up manually to read older messages, and when you do that the automatic scrolling (when new messages, tips and "typing" notifications arrive) is turned off for a short time (30 seconds, if I remember right). This is to prevent the annoying situation where you scroll up and the thing immediately scrolls back down, preventing you from reading what you wanted to read. But there's some weirdness in the code that I haven't been able to investigate properly.
One idea I've just had—just a wild guess, really—is that whoever coded this assumed scrolling is instant. So maybe there can sometimes be a timing issue if you have smooth scrolling turned on. I'm going to try disabling smooth scrolling to see if that helps. In Chromium and Chrome, the setting is: chrome://flags/#smooth-scrolling
Charlie
I am not sure why it does that, but I do know it’s a known glitch that happens to me too. They’re working on it :)
