@ionic/angular 8.8.12-dev.11781793379.156d3260 → 8.8.12-dev.11781813448.16e7a064

package/fesm2022/ionic-angular-common.mjs

@@ -893,6 +893,13 @@ const attachView = (zone, environmentInjector, injector, applicationRef, elRefMa
     const unbindEvents = bindLifecycleEvents(zone, instance, hostElement);
     container.appendChild(hostElement);
     applicationRef.attachView(componentRef.hostView);
+    /**
+     * Run change detection so template bindings (e.g. `<ion-nav [root]="rootPage">`)
+     * apply during this synchronous pass, before the web component runs its load
+     * lifecycle. `createComponent` only runs the creation pass, so without this the
+     * binding lands after the element has loaded, too late for `ion-nav` to read it.
+     */
+    componentRef.changeDetectorRef.detectChanges();
     elRefMap.set(hostElement, componentRef);
     elEventsMap.set(hostElement, unbindEvents);
     return hostElement;
@@ -2258,10 +2265,44 @@ class RouterLinkDelegateDirective {
     ngOnInit() {
         this.updateTargetUrlAndHref();
         this.updateTabindex();
+        /**
+         * Ionic components like `ion-item` render a native anchor in their shadow DOM,
+         * so a modifier click (ctrl/meta/shift/alt) or a non-`_self` target should let
+         * the browser handle the navigation natively (new tab, new window, download)
+         * instead of navigating in-app.
+         *
+         * We listen in the capture phase so this runs before Angular's `RouterLink`
+         * handler and our own bubble-phase `onClick`. On a native-navigation intent it
+         * stops propagation to cancel the in-app navigation, but leaves `preventDefault`
+         * alone so the native anchor can still act.
+         */
+        this.elementRef.nativeElement.addEventListener('click', this.onCaptureClick, { capture: true });
     }
     ngOnChanges() {
         this.updateTargetUrlAndHref();
     }
+    ngOnDestroy() {
+        this.elementRef.nativeElement.removeEventListener('click', this.onCaptureClick, { capture: true });
+    }
+    onCaptureClick = (ev) => {
+        if (this.opensNatively(ev)) {
+            ev.stopImmediatePropagation();
+        }
+    };
+    /**
+     * True when the browser should handle the click natively instead of routing
+     * in-app: a modifier was held (ctrl/meta/shift/alt), or the host targets
+     * something other than `_self`. This mirrors the modifier set Angular's own
+     * `RouterLink` guards on, so an Ionic `routerLink` behaves like a plain anchor
+     * for new-tab, new-window, and download intents.
+     */
+    opensNatively(ev) {
+        if (ev instanceof MouseEvent && (ev.ctrlKey || ev.metaKey || ev.shiftKey || ev.altKey)) {
+            return true;
+        }
+        const target = this.elementRef.nativeElement.target;
+        return target != null && target !== '' && target !== '_self';
+    }
     /**
      * The `tabindex` is set to `0` by default on the host element when
      * the `routerLink` directive is used. This causes issues with Ionic