WofWca

Something to note: this is only the case inside of the `` that we contain the apps in. If you open the console, choose the top context and execute ```javascript...

Yes. Although you have to get creative. I have implemented this in my code (see the `jumpPeriodMs > 0` case): https://github.com/WofWca/jumpcutter/blob/517de1973af1e9ccbe0c9dbc386407fbe940f1e0/src/entry-points/popup/Chart.svelte#L504-L535 Explanation: you want to manually call `smoothie.render(canvas, time)` with...

> This is news to me. How can I reproduce this? Sorry about that, I guess I misunderstood the source code. Apparently this can happen much rarer than I initially...

I'm noticing that our code is very similar to Signal, and Signal doesn't have this issue.

> EDIT: Adding margin-bottom: -1px; to .styles_module_reactions fixes it i think. Why this happens? Not so sure... Hmm idk. Didn't work for me

What did work is this one simple trick (scientists hate me): https://github.com/signalapp/Signal-Desktop/blob/29c404266863491a3b26a73b24602d36d7a3ac46/stylesheets/_modules.scss#L5573-L5587 Basically we gotta put `overflow-anchor: none;` on all of the messages except the one we want to stay...

I left some extra ideas in #4012. Another quite simple one I have is to have an `IntersectionObserver` set "visible" class on all the visible messages, and ensure that only...

> "if the scroll position is not more than X pixels from the bottom, and a new message arrives, scroll down - otherwise the user has scrolled up manually and...

Would anybody be against simply adjusting CSS such that reactions are more terse and don't cause height to change? Until we figure out a better approach.

OK, `display: flex; flex-direction: column-reverse;` on `#message-list` really looks promising. It solves nearly all scrolling problems, including #3763. But for some reason when more messages are fetched, the scroll position...