You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NbContextMenustops 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.
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.componentstops 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
The text was updated successfully, but these errors were encountered:
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?
Issue type
I'm submitting a ...
Issue description
Current behavior:
detaching
and thenattaching
the parent element (or component) by customdirective
(you can see that in repro).Expected behavior:
StackBlitz repro:
Steps to reproduce:
div
element inapp.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
The text was updated successfully, but these errors were encountered: