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
When I use SwiperComponent for Angular with virtual slides module enabled [virtual]="true", all events trigered inside <ng-template swiperSlide></ng-template> does not run in NgZone. Since SwiperModule is officially and specifically supported for Angular framework, I think it should make sure all interfaces publicly exported should be handled in NgZone by default.
The demo contains the expected behavior. The navigation with routerLink inside ng-template should run in NgZone to refresh DOM accordingly.
Actual Behavior
The navigation with routerLink inside ng-template does not run in NgZone, which causes the DOM does not refresh correctly. You can see there are warnings regarding the navigation not running in NgZone.
The text was updated successfully, but these errors were encountered:
What You Did
When I use
SwiperComponent
for Angular with virtual slides module enabled[virtual]="true"
, all events trigered inside<ng-template swiperSlide></ng-template>
does not run in NgZone. SinceSwiperModule
is officially and specifically supported for Angular framework, I think it should make sure all interfaces publicly exported should be handled in NgZone by default.Here is a minimal sample project to demonstrate the problem. If the Stackblitz live demo does not work, see this GitHub repo directly.
Expected Behavior
The demo contains the expected behavior. The navigation with
routerLink
insideng-template
should run in NgZone to refresh DOM accordingly.Actual Behavior
The navigation with
routerLink
insideng-template
does not run in NgZone, which causes the DOM does not refresh correctly. You can see there are warnings regarding the navigation not running in NgZone.The text was updated successfully, but these errors were encountered: