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

message bubbles don't expand #799

Closed
redshiftzero opened this issue Feb 11, 2020 · 16 comments
Closed

message bubbles don't expand #799

redshiftzero opened this issue Feb 11, 2020 · 16 comments

Comments

@redshiftzero
Copy link
Contributor

message bubbles (I saw this for replies at least) don't expand when the content exceeds the size of the bubble, it is instead truncated

@redshiftzero redshiftzero added bug Something isn't working component/UI labels Feb 11, 2020
@eloquence eloquence added this to the 0.2.0beta milestone Feb 12, 2020
@eloquence
Copy link
Member

Tracked as release blocker because truncation may suggest loss of information to the user.

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Feb 18, 2020

I'm unable to repro, so if someone else can thoroughly check this issue for replies (also check messages while you're at it) and can't repro then I think we can close this issue. Here's an example of what I'm seeing:
Screenshot from 2020-02-18 14-05-03

@redshiftzero
Copy link
Contributor Author

Hmm so I don't have solid STR, but I see this intermittently still on latest master in non-Qubes:

Screen Shot 2020-02-19 at 5 01 17 PM

@eloquence
Copy link
Member

Can't repro in Ubuntu dev env:

Screenshot from 2020-02-19 16-54-20

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Feb 20, 2020

Here's an STR for a similar issue:

  1. Send a reply 100+ characters long without spaces

Expected

The word to be wrapped across multiple lines with an indicator of wrapping or a horizontal scrollbar

Actual

We cut off the word after around 97 characters

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Feb 20, 2020

Another STR for a different but related issue (this is for the preview of text):

  1. Send a reply less than 180 characters but 4 lines long, e.g.

one
two
three
four

OR

  1. Send a reply with word wrapping on one line that is more than 120 characters long, e.g.

Screenshot from 2020-02-20 13-21-01

Expected

three lines in the preview with a ...

Actual

Four lines in the preview, which looks a bit crowded

(minor issue but worth reporting)

@kushaldas
Copy link
Contributor

truncated_reply_reproduced

I created the reply with python3 -c "print('A' * 300)"
I think this should be counted as a proof of the error.

@sssoleileraaa
Copy link
Contributor

^ yup that confirms the related issue but not the original issue reported here by @redshiftzero where the speech bubble doesn't entirely resize top to bottom to fit its content: #799 (comment)

even though i can't repro, i wonder, since it's an intermittent issue, if it's because we are redrawing the speech bubble at the same time we are updating the text in the speech bubble

@eloquence
Copy link
Member

eloquence commented Feb 24, 2020

Screenshot from 2020-02-24 12-30-57

Possibly related, seeing some extra special behavior in (Ubuntu/Docker) dev env today. This is after a sync, where a file and a message was added for an existing source.

Restarting the client resolved:
Screenshot from 2020-02-24 12-33-02

Part of this may be due to an out-of-sync issue. You'll notice that the first screenshot shows text missing in the second one -- that's from a previous test run against a previous instantiation of the dev env. But the source is brand new and should not have been associated with that text in the first place. :/ Will see if I can get STRs for that.

@sssoleileraaa
Copy link
Contributor

ah this reminds me of what i saw when i did a bunch of testing here #688 (review)

the issue had to do with the way ConversationView widgets (the message and reply speech bubbles) were being added/ reordered using the new index variable inline

@sssoleileraaa
Copy link
Contributor

i'll try to repro by selecting a source and sending multiple messages in one sync to that source so that the GUI has to append multiple message widgets... it looks like you saw this behavior without having to send replies, so i'll just focus on messages for now

@sssoleileraaa
Copy link
Contributor

@eloquence I've tried many different scenarios and cannot come up with an STR for what you saw here: #799 (comment)

I think the only two takeaways from this issue so far are these two STRs, which I'll create issues for:

@eloquence
Copy link
Member

I've not been able to repro either, even when nuking dev env while keeping client DB unchanged. Will keep an eye on it.

@sssoleileraaa
Copy link
Contributor

Feel free to create a separate issue since I do believe it's a different issue than what @redshiftzero reported here. We can track these issues even without STRs.

@eloquence
Copy link
Member

eloquence commented Feb 25, 2020

@redshiftzero since we've been unable to reproduce the original issue in your report (as opposed to long text truncation, tracked in #815), what do you think about deprioritizing this for now, and seeing if we can reproduce during the QA stage, while pulling in #815 for immediate work?

@redshiftzero
Copy link
Contributor Author

yep, closing this in favor of those followups

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants