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
Current behavior:
After updating @nebular/theme from 3.0.0 to 3.0.1 in my electron app I noticed that nb-select is now buggy and doesn't allow you to select any options (the list doesn't even come up) while it resides inside a nb-tabset (dynamically generated with a ngFor). The selects are also dynamically generated by a ng-template ngFor inside a nb-tab.
All the nb-selects that reside in the first tab that I click on do work. All the nb-selects in all the other tabs no longer show options when clicked. The nb-selects in the first tab that was clicked still work. This behaviour can be observed with any tab, as long as it is the first tab you click on after the app starts.
Expected behavior:
That you can always select your options in nb-select in any tab.
Steps to reproduce:
See current behaviour.
Related code:
As far as I can tell this bug was introduced by PR #1007. Reverting the associated commits while in version 3.0.1 fixes the issue again.
Other information:
npm, node, OS, Browser
node v10.15.1, Windows 7 x64, Electron running Chromium
Same Issue Noted above..I am using Nebular 3.4.0 and angular 7 from Nebular 2.0.1 and angular 6,After upgrading the both, I am getting the issues in nb-select template which is used inside nb-stepper in three forms, first form nb-select is working ,other form's nb-select are not working. Please tell me when this bug will be resolved and I am in mid way of completion of my project. Do I need to revert back the version?
Issue type
I'm submitting a ... (check one with "x")
Issue description
Current behavior:
After updating @nebular/theme from 3.0.0 to 3.0.1 in my electron app I noticed that nb-select is now buggy and doesn't allow you to select any options (the list doesn't even come up) while it resides inside a nb-tabset (dynamically generated with a ngFor). The selects are also dynamically generated by a ng-template ngFor inside a nb-tab.
All the nb-selects that reside in the first tab that I click on do work. All the nb-selects in all the other tabs no longer show options when clicked. The nb-selects in the first tab that was clicked still work. This behaviour can be observed with any tab, as long as it is the first tab you click on after the app starts.
Expected behavior:
That you can always select your options in nb-select in any tab.
Steps to reproduce:
See current behaviour.
Related code:
As far as I can tell this bug was introduced by PR #1007. Reverting the associated commits while in version 3.0.1 fixes the issue again.
Other information:
npm, node, OS, Browser
node v10.15.1, Windows 7 x64, Electron running Chromium
Angular, Nebular
Angular 7+, Nebular 3.0.1 (still occurs in Nebular 3.4.0)
The text was updated successfully, but these errors were encountered: