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

New objects sporadically overlap in treeview #4464

Closed
2 of 5 tasks
charlesh88 opened this issue Nov 15, 2021 · 3 comments · Fixed by #4472
Closed
2 of 5 tasks

New objects sporadically overlap in treeview #4464

charlesh88 opened this issue Nov 15, 2021 · 3 comments · Fixed by #4472
Labels
bug:visual Visual problem. Not a functional issue severity:critical type:bug
Milestone

Comments

@charlesh88
Copy link
Contributor

charlesh88 commented Nov 15, 2021

Summary

Creating a new object in the tree sporadically causes it to overlap an existing item:

Screen Shot 2021-11-15 at 2 48 39 PM

In the screenshot, note the two tree nodes (orange arrows) getting the same top property. Refreshing the page will fix the problem.

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?

Steps to Reproduce

Create a new item in My/Shared items, or a descendant of My/Shared items.
See that none of the following occurs.

  • General borkage of tree (you cannot expand nor collpase nodes)
  • General borkage of object view (uneditable, unsavable, etc.)
  • The created object is overlayed on top of an existing object
  • The created object is created twice
  • A gap exists between tree items (you may have to scroll down)
    For true tree enthusiasts
  • Add the first descendant to a parent
  • Add a descendant to a parent that is alphabetically before all other siblings
  • Add a descendant to a parent that is alphabetically between other siblings
  • Add a descendant to a parent that is alphabetically after all other siblings
  • Add a descendant to appear after a niece or nephew
    * Having many expanded sibling nodes above the node to be added seemed to helped reproduce borkage

Environment

  • Open MCT Version: 1.8.1-SNAPSHOT
  • Deployment Type: /testathon
  • OS: Mac
  • Browser: Chrome
@unlikelyzero
Copy link
Contributor

Fixed in testathon 11/18

@unlikelyzero unlikelyzero added the bug:visual Visual problem. Not a functional issue label Nov 18, 2021
@nikhilmandlik
Copy link
Contributor

Verified Fixed.

@charlesh88
Copy link
Contributor Author

Verified fixed Testathon 11-18-21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:visual Visual problem. Not a functional issue severity:critical type:bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants