Sometimes the chat will not "stick" to the bottom when it should (when it was scrolled down before and a new message gets posted).
It does not always happen, but once it happens once, it will happen a lot after that, until you reload the entire tab. Manually scrolling to the bottom, either via a regular scroll or clicking the blinking-arrow icon, will not resolve the issue in a permanent manner; it might go away for a few new messages just to reappear, or immediately reappear.
When this happens, the following code (deminified because MS/Volafile(tm) is not free and open software!) somehow misbehaves, getting feed erronous values
When the bug happens, data.bottom will exceed the tolerance. I observed values (in the debugger) of sometimes 48 sometimes even 120 (when scrollDown was previously true).
The scrolling code is an enigma wrapped in setTimeouts and custom event dispatches, so I will stop here for now :tired_face:
Either data.bottom is calculated wrong (or at the wrong time) or it's an async scroll issue.
Affected are at least:
Latest Desktop Chrome (somewhat regularly)
Latest Firefox Nightly E10s (less regularly)
Sometimes the chat will not "stick" to the bottom when it should (when it was scrolled down before and a new message gets posted).
It does not always happen, but once it happens once, it will happen a lot after that, until you reload the entire tab. Manually scrolling to the bottom, either via a regular scroll or clicking the blinking-arrow icon, will not resolve the issue in a permanent manner; it might go away for a few new messages just to reappear, or immediately reappear.
When this happens, the following code (deminified because MS/Volafile(tm) is not free and open software!) somehow misbehaves, getting feed erronous values
When the bug happens,
data.bottom
will exceed the tolerance. I observed values (in the debugger) of sometimes 48 sometimes even 120 (whenscrollDown
was previouslytrue
). The scrolling code is an enigma wrapped in setTimeouts and custom event dispatches, so I will stop here for now :tired_face:Either
data.bottom
is calculated wrong (or at the wrong time) or it's an async scroll issue.Affected are at least: Latest Desktop Chrome (somewhat regularly) Latest Firefox Nightly E10s (less regularly)