Skip to content

Feature: Classic chat scroll animation - #205

Open
levochkaa wants to merge 9 commits into
Swiftgram:masterfrom
levochkaa:classic-chat-scroll-animation
Open

levochkaa wants to merge 9 commits into
Swiftgram:masterfrom
levochkaa:classic-chat-scroll-animation

Conversation

@levochkaa

@levochkaa levochkaa commented Oct 26, 2026 •

Copy link
Copy Markdown

В 13.0 история чата перешла на бэкенд CoreList, и прокрутка по умолчанию (например, кнопкой «вниз») стала пружиной на 1.15 с с долгим медленным хвостом.

Тумблер «Swiftgram → Other → Classic chat scroll animation», по умолчанию выключен, возвращает кривую 12.x: безье .slide на 0.3 с из ListViewImpl, или ease-in-out, если вызывающий код передал длительность. Строка переведена на все языки.

Кнопка «вниз» в симуляторе: с тумблером прокрутка занимает 0.30 с, без него около 0.6 с видимого движения и затем хвост.


In 13.0 the chat history moved to the CoreList backend, and the default scroll (for example, with the "down" button) became a 1.15 s spring with a long slow tail.

Toggle "Swiftgram → Other → Classic chat scroll animation", off by default, brings back the 12.x curve: the 0.3 s .slide bezier from ListViewImpl, or ease-in-out if the caller passed a duration. The string is translated into all languages.

The "down" button in the simulator: with the toggle the scroll takes 0.30 s, without it about 0.6 s of visible motion and then a tail.

Generated with Claude Opus 5.5 in T3 Code.

Since 13.0 the chat history runs on the CoreList backend, whose default
scroll-to animation (the scroll-to-bottom button, for one) is a 1.15s
critically damped spring with a long slow tail. Swiftgram > Other >
"Classic chat scroll animation" (off by default) brings back the 12.x
curve: ListViewImpl's 0.3s slide bezier, or ease-in-out when the caller
gives a duration.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants