mirror of
https://github.com/discourse/discourse.git
synced 2024-11-28 08:53:45 +08:00
12131c8e21
With certain conditions, this issue does not show up. The easiest way to reproduce this is probably to do either of this - Use a 3G slow connection or; - Add a breakpoint to scrolling-post-stream.topRefresh (anon) - (and optionally lock-on.lock) This issue is happening because there are multiple areas that set scroll location in the post stream when loading a topic. In our case, sometimes lock-on is triggering and scrolling to post_1, before ?page=2's post_21 is being scrolled to, due to posts above post_21 can finishing loading at different times. This causes some calculations to not add up, as being in the middle of a post stream has different calculations than being at the top of the post stream. |
||
|---|---|---|
| .. | ||
| assets | ||
| controllers | ||
| helpers | ||
| jobs | ||
| mailers | ||
| models | ||
| serializers | ||
| services | ||
| views | ||