# fix\(mobile\): a thread re-render no longer turns following back on · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/a701ab26afd00d94b9614e822ab6bbd0d19e8f81)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: a701ab26afd00d94b9614e822ab6bbd0d19e8f81

Requested commit: a701ab26afd00d94b9614e822ab6bbd0d19e8f81

Commit: a701ab26afd00d94b9614e822ab6bbd0d19e8f81

Tree: 7aaafb5bd71f6e117b8ac4eb2ea993693a026a40

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): a thread re-render no longer turns following back on

The thread feed reset following and its scroll session when the thread
changed or a message was sent. The effects listed the feed's own
handlers as dependencies, and those change whenever the parent passes a
new follow callback, so any such re-render reset them too. A reader
scrolled up through a thread could find following switched back on, and
a fold's width reflow lost its place partway through.

The resets now run as an effect event, triggered only by the thread
key and the submitted message.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [fdfc6ea1c154022451eda16aed4ef66b5d19b610](https://git.cafe/pingdotgg/t3code/commit/fdfc6ea1c154022451eda16aed4ef66b5d19b610?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/a701ab26afd00d94b9614e822ab6bbd0d19e8f81?format=markdown)