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

Highest priority inspector tab is not auto selected #7442

Open
3 of 7 tasks
shefalijoshi opened this issue Jan 30, 2024 · 1 comment
Open
3 of 7 tasks

Highest priority inspector tab is not auto selected #7442

shefalijoshi opened this issue Jan 30, 2024 · 1 comment
Labels
bug:regression It used to work. Now it doesn't :( severity:medium type:bug

Comments

@shefalijoshi
Copy link
Contributor

shefalijoshi commented Jan 30, 2024

Summary

When an inspector tab has the highest priority and a different tab is currently highlighted, the highest priority tab should be selected by default.

Expected vs Current Behavior

The previously highlighted tab stays selected even if it is lower priority than other tabs.

Steps to Reproduce

  1. View a timelist object with activities listed
  2. In the inspector view notice that the Properties tab is selected by default. (It should be the View Properties tab.
  3. Select an activity (row) and notice that an Activity tab is now added to the inspector tabs
  4. Notice that the Activity tab is not selected by default and the Properties tab is still selected.

Environment

  • Open MCT Version: 4.0.0
  • Deployment Type: Open MCT VIPER
  • OS: All
  • Browser: All

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

@akhenry
Copy link
Contributor

akhenry commented Mar 22, 2024

This sounds like a medium rather than a critical, but I haven't seen it in action. @shefalijoshi , @charlesh88 - thoughts on user impact?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:regression It used to work. Now it doesn't :( severity:medium type:bug
Projects
None yet
Development

No branches or pull requests

3 participants