It is a technical chat interface problem: while reading a long answer, the page automatically scrolls the user back down, making it impossible to calmly review the earlier part of the text.<\/em><\/p>\n In this case, it is best to speak not about a theological question, but about a properly written bug report for the developers. If the problem occurs specifically on the site sda.bible-llm.com<\/a>, it should be described simply, specifically, and reproducibly. This will help the team find the cause more quickly and fix the chat behavior.<\/p>\n The symptom looks like this: when the assistant generates a long response, the user tries to scroll up in the chat to reread previous paragraphs, but the interface automatically pulls them back down. As a result, reading long messages becomes very inconvenient or completely impossible.<\/p>\n This is usually related to the auto-scroll mechanism being tied to every message update. During streamed text generation, the chat window may continually be \u201cpushed\u201d to the last line, even if the user has intentionally scrolled up. To the user, this looks like broken scrolling, although technically the problem often lies in the auto-scroll logic.<\/p>\n The best option is to send a short bug report in English or Ukrainian. Here is a ready-made text in Ukrainian:<\/p>\n The chat forcibly scrolls down while reading long responses<\/p>\n On the site sda.bible-llm.com<\/a> during long assistant responses, if you scroll the chat upward, the interface automatically returns the view to the bottom. Because of this, it is impossible to read the upper part of the response.<\/p>\n If the user scrolls the chat upward, the current scroll position should be preserved. Automatic scrolling to the bottom should be temporarily disabled until the user manually returns to the bottom part of the chat.<\/p>\n The chat constantly \u201cjumps\u201d to the latest message or to the very bottom of the thread.<\/p>\n 1. Open the chat at sda.bible-llm.com<\/a>. This format is especially useful because it includes not only a complaint, but also clear conditions for reproducing the bug.<\/p>\n Although only the site team can determine the exact cause, the most likely possibilities are:<\/p>\n \u2022 the auto-scroll logic triggers on every message update; For a developer, these are already useful enough clues to check the relevant places in the code. Usually, the fix is to disable automatic scrolling as soon as the user moves away from the bottom edge of the chat, and to enable it again only when the user returns to the bottom on their own.<\/p>\n If you need the most concise version possible, you can send the following message:<\/p>\nWhat is the problem<\/h2>\n
How to describe this to developers<\/h2>\n
Title:<\/h2>\n
Description:<\/h2>\n
Expected behavior:<\/h2>\n
Actual behavior:<\/h2>\n
Steps to reproduce:<\/h2>\n
\n2. Ask a question that triggers a long response.
\n3. During generation or after the long text appears, scroll the chat upward.
\n4. Observe how the interface automatically returns the view downward.<\/p>\nPossible technical causes<\/h2>\n
\n\u2022 the scroll position is not preserved during streamed text output;
\n\u2022 a change in the height of the message container triggers another scroll-to-bottom;
\n\u2022 the application does not distinguish between manual user scrolling and programmatic scrolling;
\n\u2022 the chat component overrides the scroll position after every re-render.<\/p>\nShort version to send<\/h2>\n