-
Notifications
You must be signed in to change notification settings - Fork 487
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
Left panel "Find Traces" is not scrollable #16
Comments
It also happens to me in a Mac with a resolution of 1280 x 800. |
Gathering some feedback on this, should we make each side scrollable or just have the whole page scroll without having the "Find Traces" section fixed? |
I would vote for
|
I think that having both sides scrollable won't help if the user is not familiar with the UI. He won't understand that he has to scroll the right side to see a button that he has know idea that it exists. My four cents (not in order of priority):
|
I don't like making the panel horizontal - it's what Zipkin does and it looks awful. I prefer making the search params panel scrollable. To improve its usability
|
Another option might be to place some of the components within collapsible regions - for example the lookback, min/max durations could be collapsed in a region entitled "Time Range". This would reduce the initial height so overcome the original problem. |
We're exploring possible solution in #20 |
The original issue of the search form not scrolling was resolved in #53 with the removal of The other UX directions discussed in this ticket have not been implemented. @yurishkuro Is there a consensus on where the other UX changes have landed? |
it's not ideal but at least makes the form usable with zoom-in. I suggest closing this; #20 will take care of it in the long term. |
Fixed by #53. |
When I zoom in browser I am not able to see the bottom of left panel "Find Traces" neither to scroll down. I'm only able to scroll down trace instances.
This issue was reported here in Red Hat MSA project when Jaeger is embedded in an iframe:
The text was updated successfully, but these errors were encountered: