# 새 주제 탐색 시 게시글 히스토리가 20개 이전으로 되돌아갑니다

**URL:** https://meta.discourse.org/t/discourse-jumps-back-20-posts-in-post-history-when-navigating-to-new-topic/242739
**Category:** Bug
**Created:** [10월 24, 2022, 1:40오전 UTC](https://meta.discourse.org/t/discourse-jumps-back-20-posts-in-post-history-when-navigating-to-new-topic/242739 "2022-10-24T01:40:01Z")
**Posts on this page:** 1
**Showing post:** 36

<div class="post-metadata">

### Author: ![Firepup650](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/firepup650/32/465200_2.png) [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [8월 28, 2023, 8:26오후 UTC](https://meta.discourse.org/t/discourse-jumps-back-20-posts-in-post-history-when-navigating-to-new-topic/242739/36 "2023-08-28T20:26:12Z")

</div>

이 문제가 최근 다시 발생한 것으로 보이며, 수정이 곧 이루어질 것입니다 (해당 변경 사항은 이미 병합되었으므로).  
새로운 게시글:

> [@게시물이 잘못된 글로 이동합니다](https://meta.discourse.org/t/topics-jumping-to-wrong-post/276305/31):
>
> Thanks so much for the clear reproduction steps @Don pray Yup, that’s it! Two things going on here at the same time Loading slider service needs to remove the still-loading class from the body LockOn needs to scroll to the right place They were both scheduled in the afterRender part of Ember’s runloop. And since the ‘lock on’ stuff is technically scheduled first, it was being run first. And so LockOn was running while all the post HTML was in the DOM, but still had display: none. …

GitHub PR:

> <https://github.com/discourse/discourse/pull/23290>
>
> When the 'loading slider' navigation indicator is enabled, and a connection is v…ery slow, we \`display: none\` most of the page and display a spinner. The \`still-loading\` body class for this was being added in the \`afterRender\` step in the Ember runloop. This meant that, depending on the order they were scheduled, other \`afterRender\` jobs may run before it. This caused an issue with topic scroll locations because we would attempt to scroll to an element which was \`display: none\` at the point its position was calculated.
> 
> This commit moves the \`still-loading\` class manipulations to the \`render\` step of the runloop, which is technically more correct, and means that anything scheduled in the \`afterRender\` step is guaranteed to run without the \`display: none\` CSS.
> 
> https://meta.discourse.org/t/276305/29

---

_[View the full topic](https://meta.discourse.org/t/discourse-jumps-back-20-posts-in-post-history-when-navigating-to-new-topic/242739)._