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

Unable to read full text from Tackle Operator description #53

Open
dewan-ahmed opened this issue Jul 19, 2021 · 6 comments
Open

Unable to read full text from Tackle Operator description #53

dewan-ahmed opened this issue Jul 19, 2021 · 6 comments

Comments

@dewan-ahmed
Copy link

Screen Shot 2021-07-19 at 5 06 17 PM

From the above image, you can see that some part of the text is trimmed at the end. Hovering over that section does not help either.

@mrizzi
Copy link
Contributor

mrizzi commented Jul 20, 2021

Hi @dewan-ahmed, thanks for getting in touch reporting this.
The description you referred to is shown according to OpenShift's UI and it's out of Tackle operator's control.
You can anyway read the full text clicking on the Create instance link shown in your screenshot and it will take you to a screen that shows the full description as the next screenshot demonstrates.

Screenshot from 2021-07-20 10-01-54

@dewan-ahmed
Copy link
Author

Hi @mrizzi thanks for the info. Please let me know the appropriate github repo for OpenShift UI and I can open up the issue there (I can also link this issue there).

@mrizzi
Copy link
Contributor

mrizzi commented Jul 21, 2021

TBH, I think this is a feature rather than a bug to ensure the OCP UI displays all custom resources cards of an operator with the same size letting the user read the complete description once a specific custom resource is selected.

@dewan-ahmed
Copy link
Author

If this is not a bug from OpenShift UI, probably there is a character limitation on how much text that card can display and operators would limit their operator description accordingly.

@PhilipCattanach
Copy link

This is a really trivial issue. It is clear from the ... that the description is only partially visible. And there is enough information visible to understand what the Operator is for. If the user decide they do want proceed to deploy tackle then all of the description will become visible.

@dewan-ahmed
Copy link
Author

It is a tiny and possibly trivial issue from an Engineering perspective. From a developer/user's experience perspective; I would not call this trivial. This can definitely be a lower-priority issue.

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

No branches or pull requests

3 participants