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

bug: telemetry data is over wizard #1553

Open
1 task done
patrickelectric opened this issue Jan 8, 2025 · 2 comments
Open
1 task done

bug: telemetry data is over wizard #1553

patrickelectric opened this issue Jan 8, 2025 · 2 comments
Labels
bug Something isn't working ui UI related issues

Comments

@patrickelectric
Copy link
Member

Bug description

image

Steps to reproduce

  1. Run wizard
  2. Click next until telemetry window is over wizard

Primary pain point(s)

Can't read wizard, the wizard also does not come up the telemetry window if clicked over it

Additional context

bad initial experience

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.
@patrickelectric patrickelectric added bug Something isn't working ui UI related issues labels Jan 8, 2025
@rafaellehmkuhl
Copy link
Member

@ArturoManzoli can you check if your PR deals with that?

@ArturoManzoli
Copy link
Contributor

@ArturoManzoli can you check if your PR deals with that

The PR doesn't deal with that situation. Actually, this layering was thought on the Tutorial feature implementation.

If you click on the tutorial screen (just like in any other window management system) it will bring up the selected window, and the tutorial will be over the telemetry screen again and vice-versa.

Also in very small screens (not our attention priority for now), the layers order gets very problematic and the user needs to close the telemetry window to access back the tutorial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ui UI related issues
Projects
None yet
Development

No branches or pull requests

3 participants