Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usercard doesn't show old message history when channel scrollback is increased #4324

Closed
4 tasks done
dnsge opened this issue Jan 22, 2023 · 1 comment · Fixed by #4496
Closed
4 tasks done

Usercard doesn't show old message history when channel scrollback is increased #4324

dnsge opened this issue Jan 22, 2023 · 1 comment · Fixed by #4496
Labels
issue-report An issue reported by a user.

Comments

@dnsge
Copy link
Contributor

dnsge commented Jan 22, 2023

Checklist

  • I'm reporting a problem with Chatterino
  • I've verified that I'm running the most recent nightly build or stable release
  • I've looked for my problem on the wiki
  • I've searched the issues and pull requests for similar looking reports

Describe your issue

If you open a user's usercard in a channel, only "recent" messages of theirs will be shown in their message history. If the channel scrollback setting has been increased, messages from much earlier (I imagine >1000 messages ago) aren't shown.

To easily replicate: increase your message scrollback history and wait a while in a busy chat. Scroll all the way up and open a random user's usercard. You will likely see "No recent messages" despite obviously seeing the message in the split you have open.

Screenshots

image

In this image, a message from pajlada at 14:20 is still visible in the channel history. However, his usercard begins showing messages at 16:55.

OS and Chatterino Version

Chatterino Nightly 2.4.0 (commit d5a0420 modified) built on 2023-01-16 with Qt 5.15.2, Windows SDK, MSVC 193431937 Running on Windows 10 Version 2009, kernel: 10.0.19045

@dnsge dnsge added the issue-report An issue reported by a user. label Jan 22, 2023
@dnsge
Copy link
Contributor Author

dnsge commented Jan 22, 2023

Never mind, this is a different setting :)

@dnsge dnsge closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue-report An issue reported by a user.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant