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

text on the gui becomes unreadable when connect failed #6546

Closed
jnweiger opened this issue May 24, 2018 · 8 comments
Closed

text on the gui becomes unreadable when connect failed #6546

jnweiger opened this issue May 24, 2018 · 8 comments
Assignees
Labels
Design & UX ReadyToTest QA, please validate the fix/enhancement
Milestone

Comments

@jnweiger
Copy link
Contributor

jnweiger commented May 24, 2018

First screenshot below shows the next screen of the gui after entering login credentials.
If the credentiasl were invalid, and user presses the [Connect...] button, the screen changes to the second screenshot below.

40486212-ef587c14-5f60-11e8-8737-82adebd2e20f

Note the lines get squeezed to make room for the pink error message. Here everything is still readable, but sometimes one can no longer decipher the texts.

Seen on Kubuntu18.04 with Plasma desktop.

@guruz guruz added this to the 2.5.0 milestone May 24, 2018
@ckamm
Copy link
Contributor

ckamm commented May 25, 2018

@jnweiger I'll check it out and will be able to reproduce the label appearing -- but how did you get to this screen with invalid credentials? That shouldn't happen as far as I know!

@michaelstingl
Copy link
Contributor

Server issue/hack is needed to get stuck with this error.

@ckamm ckamm added the ReadyToTest QA, please validate the fix/enhancement label May 25, 2018
@guruz
Copy link
Contributor

guruz commented May 29, 2018

@jnweiger fix is in alpha, feel free to test and close

@SamuAlfageme
Copy link
Contributor

SamuAlfageme commented Jun 4, 2018

Still reproducible in 2.5 (tested with a build based on 76bb76a):

screenshot 2018-06-04 12 25 53

Hints to reproduce:

  • Set up mitmproxy on the client and set it to intercept all (.*) requests
  • Get to the "Connect to ownCloud" page on the wizard and click connect
  • Hit a to accept the request, then enter to inspect it
  • Hit tab to switch to Response and e to edit, then o to tamper the HTTP code to e.g. 500
  • Forward the response to the client (a to accept it)

@SamuAlfageme SamuAlfageme removed the ReadyToTest QA, please validate the fix/enhancement label Jun 4, 2018
@ckamm
Copy link
Contributor

ckamm commented Jun 11, 2018

@SamuAlfageme Yes, this still happens for a multi-line error message, I had only tested with single-line errors.

The underlying problem is that this layout has no vertical wriggle room. So when an error message becomes visible and needs more space than expected there's not enough space left over all and the layout becomes squished. I'm checking whether I can give the middle spacer some shrinking flexibility.

@ckamm
Copy link
Contributor

ckamm commented Jun 11, 2018

@SamuAlfageme There's a new PR to check out.

@jnweiger
Copy link
Contributor Author

@michaelstingl @ckamm no server hackery needed. This was simply a client with preconfigured server url

@jnweiger
Copy link
Contributor Author

reproduce attempt with #6589 results in a nice little scrollbar next to the error mssage, no more squeezed widgets.
Thanks!
grafik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design & UX ReadyToTest QA, please validate the fix/enhancement
Projects
None yet
Development

No branches or pull requests

5 participants