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

Option names overlap, hard to read #927

Closed
alexanderdd opened this issue May 11, 2020 · 7 comments
Closed

Option names overlap, hard to read #927

alexanderdd opened this issue May 11, 2020 · 7 comments
Labels
Milestone

Comments

@alexanderdd
Copy link

When using text options, the options overlap and make it hard/impossible to read. Note also that the first option is cut off at the left:
Bildschirmfoto vom 2020-05-11 19-44-46

Nextcloud 18.0.2
Polls 1.4.3

Tell me if you need more info.

Too bad, I just wanted to use Polls for the first time, aaaaand nope, can't use it =(

@dartcafe
Copy link
Collaborator

Hyphens are missing. A workaround could be to use the table view, there is more space for the text.

@dartcafe dartcafe added this to the 1.5 milestone May 12, 2020
@dartcafe dartcafe added the bug label May 12, 2020
@dartcafe
Copy link
Collaborator

Hyphens are working, but still no effect with chrome and some other browsers:
https://caniuse.com/#feat=css-hyphens
And there is some strange behavior depending of the used language:
https://stackoverflow.com/questions/28976543/css-hyphens-not-working-in-firefox

Maybe, we should default to the table layout in text polls.

@dartcafe
Copy link
Collaborator

Avoiding with switch to list layout.

Copy link

github-actions bot commented Jun 7, 2024

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 7, 2024
@alexanderdd
Copy link
Author

I think we should keep this open!?

@alexanderdd alexanderdd reopened this Jun 27, 2024
@dartcafe
Copy link
Collaborator

Why should we keep an outdated and four years ago closed issue open?

@alexanderdd
Copy link
Author

@dartcafe in 2020 you closed this issue, suggesting a workaround, which to me is not enough to close an issue, an actual fix is needed (or a "wontfix" decision).

I just checked, and this bug is indeed fixed in NC 29.0.3

So it can stay closed

sorry for the misunderstanding

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

No branches or pull requests

2 participants