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

Sometimes difficult to add new entries to notebooks in layouts #4748

Closed
3 of 5 tasks
akhenry opened this issue Jan 20, 2022 · 4 comments
Closed
3 of 5 tasks

Sometimes difficult to add new entries to notebooks in layouts #4748

akhenry opened this issue Jan 20, 2022 · 4 comments
Labels
bug:regression It used to work. Now it doesn't :( needs:e2e Needs an e2e test severity:medium type:bug
Milestone

Comments

@akhenry
Copy link
Contributor

akhenry commented Jan 20, 2022

Summary

When attempting to add a new entry to a notebook that is contained in a layout using the + button in the notebook, the new entry input will sometimes briefly appear and then disappear. Pressing the button again will work.

This only occurs in layouts (display and flex), and only occurs when the notebook is not selected, so it's some interaction between notebooks, the selection API, and layouts.

Expected vs Current Behavior

Clicking on the + button should allow me to immediately add an entry to a notebook, even inside of a layout.

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?

Steps to Reproduce

  1. Place a notebook inside a layout and save the layout.
  2. Navigate away from the layout, and then back again
  3. Click on the + button at the top of the notebook to add a new entry
  4. Observe that the new entry input briefly appears before immediately disappearing

Environment

  • Open MCT Version: 384af89
  • Deployment Type: Dev with couch DB enabled
  • OS: MacOS
  • Browser: 97.0.4692.71
@akhenry akhenry added type:bug bug:regression It used to work. Now it doesn't :( severity:medium labels Jan 20, 2022
@jvigliotta jvigliotta self-assigned this Apr 7, 2022
@jvigliotta
Copy link
Contributor

Closing as I was unable to replicate, let's test it in testathon

Testing

  • reproduction steps in issue

@unlikelyzero unlikelyzero added the needs:e2e Needs an e2e test label Apr 7, 2022
@unlikelyzero unlikelyzero added this to To triage in Improve Test Coverage via automation Apr 7, 2022
@unlikelyzero unlikelyzero added the bug:retest Retest without a specific milestone label Apr 7, 2022
@unlikelyzero
Copy link
Collaborator

Could not reproduce. Please reopen if found

@unlikelyzero unlikelyzero added this to the Target:2.0.2 milestone Mar 20, 2023
@rukmini-bose
Copy link
Contributor

Can't reproduce this Testathon 3/20/2024

@charlesh88 charlesh88 removed the bug:retest Retest without a specific milestone label Mar 20, 2024
@charlesh88
Copy link
Contributor

Testathon 2024-03-20 cannot repro, fixed.

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 :( needs:e2e Needs an e2e test severity:medium type:bug
Projects
Development

No branches or pull requests

5 participants