keybase / keybase/client

GUI gets surprised when ambushed by hidden conversations

Open
#16,072 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

As described in #14625 (closed by the reporter) opening a new conversation with someone you've previously hidden will cause the conversation window to close after a variable amount of time. Sending the message is impossible even if you manage to hit enter before the window closes.

Unhiding the conversation first works, but that is a hassle when you're not sure you've got one tucked away.

Ideally, I would like the option to close/forget a conversation, which would remove it entirely and the next conversation to start from scratch.

If that's not possible, can you automatically unhide any pre-existing conversation when I initiate a "new" one?

Apparently I can't tag any @keybase/react-hackers :|

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the GUI behavior described here: initiate a new conversation with someone whose conversation is hidden and verify that the window closes before a message can be sent. Use #14625 for background, then compare the behavior with an unhidden conversation; done means a new conversation can be opened and a message sent without the window closing unexpectedly.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.