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

Large view from flexible layout panel leads to blurry charts and nonworking buttons #7535

Closed
3 of 7 tasks
inad9300 opened this issue Feb 29, 2024 · 2 comments · Fixed by #7459
Closed
3 of 7 tasks
Labels
type:bug verified Tested or intentionally closed
Milestone

Comments

@inad9300
Copy link

inad9300 commented Feb 29, 2024

Summary

When going into "Large View" mode in a chart, particularly from a panel within a flexible layout, the plotted graph lacks sharpness, as well as the ability to interact with it by hovering over individual points, zooming in with the mouse or the buttons, panning, etc. When trying to perform these actions, the graph stays frozen in its blurry state, it never gets redrawn from its original form.

Steps to Reproduce

  1. Create a new flexible layout
  2. Assign telemetry to the two panels presented by default
  3. Maximize either of them by clicking "Large View"
  4. Observe the blurriness in the chart
  5. Rub your eyes to make sure it isn't an artifact of your vision system 🙃

Environment

  • Open MCT Version: 3.2.0, Feb 23 2024 (4c2b59d)
  • Deployment Type: npm run build:prod
  • OS: Ubuntu 22.04
  • 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

An example:

blurry-open-mct-chart

@ozyx ozyx added this to the Target:4.0.0 milestone Mar 4, 2024
@ozyx
Copy link
Contributor

ozyx commented Mar 4, 2024

@inad9300 Thanks for reporting this. I was able to reproduce the issue on v3.2.1, but not on 86e636c, so this will be fixed in the next release (which should be released by the end of this month). Once I identify the commit that fixed the issue, I'll follow up in this thread so you can build your own from source for the meantime, if needed.

@ozyx ozyx closed this as completed Mar 4, 2024
@ozyx ozyx mentioned this issue Mar 4, 2024
15 tasks
@ozyx
Copy link
Contributor

ozyx commented Mar 5, 2024

Verified fixed -- Testathon 3/5/24

Looks good!

@ozyx ozyx added the verified Tested or intentionally closed label Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug verified Tested or intentionally closed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants