-
Notifications
You must be signed in to change notification settings - Fork 42
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
Remove ConversationView.add_reply_from_reply_box #834
Conversation
Checked in with @redshiftzero about this PR before her leave; this is still a valuable change, we can pick this up from her in coming weeks. |
329e944
to
4a4e672
Compare
I just updated the work that @redshiftzero did to get it ready for review. I don't think it fixes an error at this point, but it is a nice refactor that simplifies our logic around adding reply widgets. I tried to change very little so that this remains a simply refactor. |
(tests should fail because I didn't even run them locally yet after my update) |
Signed-off-by: Allie Crevier <[email protected]>
910c095
to
3aeef6e
Compare
This is a nice change that definitely simplifies the reply and draft logic, tests look good, and replies still show up in the reply box. I did once notice a reply that seemed to briefly disappear after being sent and re-appear on sync, but I haven't been able to reproduce it despite a lot of attempts. I also noticed this issue, but it's not a regression since it's also present on main. From a preliminary review it looks good to me. |
Closing because commits from here are being cherry-picked into #1432 |
Description
Fixes #821.
I had a suspicion that adding widgets to the conversation view outside of
ConversationView.update_conversation
might be a cause for the odd bubbles appearing on top of each other behavior that some are seeing (I've not seen this myself yet), so putting this diff up which I had locally (because I don't think this method is required anymore) in case it's related to that. Will look more tomorrow to try to reproduce the underlying behavior if no one beats me to it.Test Plan
Check you can still send replies and they are confirmed as usual
Checklist
If these changes modify code paths involving cryptography, the opening of files in VMs or network (via the RPC service) traffic, Qubes testing in the staging environment is required. For fine tuning of the graphical user interface, testing in any environment in Qubes is required. Please check as applicable:
If these changes add or remove files other than client code, packaging logic (e.g., the AppArmor profile) may need to be updated. Please check as applicable: