Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Vue warnings after Recent Objects target animation ends #6201

Closed
7 tasks
ozyx opened this issue Jan 26, 2023 · 2 comments · Fixed by #6203
Closed
7 tasks

Vue warnings after Recent Objects target animation ends #6201

ozyx opened this issue Jan 26, 2023 · 2 comments · Fixed by #6203

Comments

@ozyx
Copy link
Member

ozyx commented Jan 26, 2023

Summary

Title says all

Expected vs Current Behavior

No vue warnings

Steps to Reproduce

  1. Click on an object to populate the Recent Objects list
  2. Click the target button for the object
  3. See the object highlight and flash
  4. Once the animation ends, notice vue warning(s) in the console:
    image

No functional impact.

Environment

  • Open MCT Version: 2.1.6-SNAPSHOT
  • Deployment Type: local
  • OS: MacOS
  • 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

@ozyx
Copy link
Member Author

ozyx commented Jan 26, 2023

Testing Instructions

  1. Open console
  2. In recent objects, use the "target" button to scroll to and highlight an object in the tree
  3. Wait until animation ends and confirm no vue warnings pop up in the console

@michaelrogers
Copy link
Contributor

Fix verified during testathon on 2022-02-02. No console errors were observed when the target button is triggered. Additionally, spamming the target button and interrupting and existing animation does not cause any problems and works as expected.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants