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

[Mobile Support] Supermenus need some tweaking #7536

Open
7 tasks
rukmini-bose opened this issue Feb 29, 2024 · 0 comments · May be fixed by #7537
Open
7 tasks

[Mobile Support] Supermenus need some tweaking #7536

rukmini-bose opened this issue Feb 29, 2024 · 0 comments · May be fixed by #7537
Assignees
Labels
not_viper Temporary label to define bugs that won't affect viper deployments type:bug type:enhancement

Comments

@rukmini-bose
Copy link
Contributor

Summary

In mobile, supermenus need some design tweaking. Currently, the supermenus are too large and go off the screen. Additionally, there's a ton of extra space, since hover actions that work on desktop to show the description of the menu options, do not work in mobile.

This is what it currently looks like:
Screenshot 2024-02-29 at 2 54 36 PM

How to Fix:

  1. Remove the option for menu descriptions.
  2. Make the size of these popups smaller, such that they do not go off the screen.

Expected vs Current Behavior

Steps to Reproduce

  1. Go to Open MCT on mobile and select a phone device like an iPhone SE or 11.
  2. Go to the Time Conductor and click on one of the grid options (switching between time modes is a good one to look at).
  3. Observe that the supermenu goes off the screen and that there's a ton of unused space.

Environment

  • Open MCT Version: 4.0.0
  • Deployment Type: testathon
  • OS:
  • Browser: Chrome

Impact Check List

  • Data loss or misrepresented data?
  • Regression? Did this used to work or has it always been broken?
  • Is there a workaround available?
  • Does this impact a critical component?
  • Is this just a visual bug with no functional impact?
  • Does this block the execution of e2e tests?
  • Does this have an impact on Performance?

Additional Information

@rukmini-bose rukmini-bose added type:bug type:enhancement not_viper Temporary label to define bugs that won't affect viper deployments labels Feb 29, 2024
@rukmini-bose rukmini-bose added this to To do in Mobile Support via automation Feb 29, 2024
@rukmini-bose rukmini-bose linked a pull request Feb 29, 2024 that will close this issue
15 tasks
@rukmini-bose rukmini-bose self-assigned this Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not_viper Temporary label to define bugs that won't affect viper deployments type:bug type:enhancement
Projects
Development

Successfully merging a pull request may close this issue.

1 participant