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

NbContextMenu stops working after parent element is "reattached" #1273

Closed
1 of 2 tasks
Roman-Simik opened this issue Mar 3, 2019 · 2 comments
Closed
1 of 2 tasks

Comments

@Roman-Simik
Copy link

Roman-Simik commented Mar 3, 2019

Issue type

I'm submitting a ...

  • bug report
  • feature request

Issue description

  • NbContextMenu stops working after parent element/component is "refreshed".

Current behavior:

  • After "refreshing" the element/component, every NbContextMenu inside that element/component stops working.
  • PS: By refreshing I don't mean using "F5", but by detaching and then attaching the parent element (or component) by custom directive (you can see that in repro).

Expected behavior:

  • After "reattaching" the element/component, every NbContextMenu located in that element/component should still be working.

StackBlitz repro:

Steps to reproduce:

  • Open atleast once the NbContextMenu (by clicking on ContextMenu button) and then click "call directive refresh method" button. After that, every NbContextMenu inside the div element in app.component stops working and you aren't able to open it again.

Other information:

OS: propably ALL (tested on Windows 10)
Browser: propably ALL (tested on Chrome, Firefox)
Angular: 7.1
Nebular 3.1
Node: 8.9.4

All versions you can see of course in the StackBlitz repro

@nnixaa
Copy link
Collaborator

nnixaa commented Apr 1, 2019

Fixed in #1316

@nnixaa nnixaa closed this as completed Apr 1, 2019
@Roman-Simik
Copy link
Author

Roman-Simik commented Apr 8, 2019

Hi, so after I tested new version (3.4.2) where this bug is supposed to be fixed, it's not,
Check this Stackblitz with updated version
Can you please reopen this issue?

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

No branches or pull requests

2 participants