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

Same issue happening when add nb-select inside Feature module. Not working even with nb-layout wrapping all app. Any help? #2180

Open
AlaaEl-DinAhmed opened this issue Jan 20, 2020 · 7 comments

Comments

@AlaaEl-DinAhmed
Copy link

Same issue happening when add nb-select inside Feature module. Not working even with nb-layout wrapping all app. Any help?

Originally posted by @Mayocampo in #943 (comment)

@Destreyf
Copy link

I'm not sure if it's applicable, but make sure that you do not have more than one nb-layout, once you add a second layout the "overlay" used to reference the list of items can't render correctly, this drove me insane trying to figure out and is incredibly un-intuitive.

@unrealisted
Copy link

unrealisted commented Jan 30, 2020

Same issue with datepicker. I have structure like a ngx-admin(with one ngx-one-column-layout preset and no more), but inside feature modules:
Cannot read property 'appendChild' of undefined at NbOverlayContainerAdapter._createContainer
Wrapping it in layouts => breaking default styles/scrolls and etc.

@Destreyf
Copy link

@unrealisted Are you creating the elements inside of the nb-layout and nb-layout-column?

Would it be possible for you to share your general layout?

@unrealisted
Copy link

unrealisted commented Feb 4, 2020

@unrealisted Are you creating the elements inside of the nb-layout and nb-layout-column?

Would it be possible for you to share your general layout?

@Destreyf Sorry, i can attach only screens:

Screenshot_1
Screenshot_2

@kakid
Copy link

kakid commented Feb 13, 2020

Hello,

Here you will found a working sample with lazy loaded module : Nebular Stackblitz with lazy loading

I had the same issue, I fixed it with loading the nbSelect directly in my child module, in my first approach, I loaded all my nubelar dependancy throw a custom nebular module.
my nebular module looked like :

import { NgModule } from '@angular/core';
import {
        NbThemeModule,
        NbSidebarModule,
        NbToastrModule,
        NbLayoutModule,
        NbSelectModule    
} from '@nebular/theme';
import { NbEvaIconsModule } from '@nebular/eva-icons';
import { DirectionService } from './services/direction.service';
@NgModule({
    imports: [
        NbThemeModule.forRoot(,
        NbSidebarModule.forRoot(),
        NbToastrModule.forRoot(),
        NbLayoutModule,
        NbSelectModule
    ],
    exports: [
        NbThemeModule,
        NbSidebarModule,
        NbToastrModule,
        NbLayoutModule,
        NbSelectModule    
    ],
    providers: [DirectionService]
})
export class NebularModule {}

@snakone
Copy link

snakone commented Mar 5, 2020

i know people says only use one <nb-layout> for your entire app, i had the same issue, quite desperate, i tried to wrap the child <router-outlet> where you have the pop-up with this

<nb-layout>
      <nb-layout-column>
        <router-outlet></router-outlet>
      </nb-layout-column>
</nb-layout>

woala!! problem solved, working on a thrid child of the main router-outlet

@tegola
Copy link

tegola commented Jun 8, 2021

I have managed to solve this. See here.

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

7 participants