components: ngZone: 'noop' option doesn't work with Angular Material components

ngrx and rx-angular give us a way to create application without zonejs. I wish that material remove zonejs so I can get rid of this library in my application. this is only thing is missing.

@jelbourn its 2022, any news? it’s in the plan of the team?

I’m going to close this as complete now thanks to the work done by @mmalerba to remove ngZone.onStable and ngZone.onMicrotaskEmpty. Note that if you are using ngZone: 'noop', you do need to run change detection through ApplicationRef.tick.

News here?

Any update on this?

Angular material and cdk will both adopt signals when support is further along. It’s a long-term goal for the team to ensure that all of Angular’s first-party offerings are signal-based with no zonejs dependency. It’s a long road, though, as it involves many breaking changes that need gradual rollouts, backwards compatibility, and migration tooling.

I’d also love to get an update on this one. I really like using materials but now it seems that it’s a no-go when high performance is a must and noop is used 😕

Any Update?

The lack of transparency about whether Material will go Signals in the foreseeable future makes me believe that we get stuck with it as it is and zone.js will still be needed in the coming years. My context is that I want Angular to transpile to native async/await - which is seemingly not possible if zone.js is still in the game.

Any news on this matter? “In Angular 17, signals were released as stable (except for the effect() function)”. Can we at least expect material to move forward in the foreseeable future (months not years)? Would be great to have some updated info in order to make decisions on our side.

I wrote this library to help with angular zoneless apps.
The library will also make material work in zoneless mode (and will also make every 3rd party that does not support zoneless work) link to the library: az-zoneless. The library also expose events that will trigger ChangeDetectorRef.detectChanges.
For example:

<button (azClick)="doSomething()">this click works in zoneless since it calls ChangeDetectorRef.detectChanges()</button>

Any updates on this?

Another note. if you happen to use angular lifecycle hooks. Make sure you manually call ngOninit… Just spent ages with a dev fixing his code to finally notice he used lifecycle

So then it will be a part of the v18 release? Will it be considered as ‘stable’ or ‘development’ at that point?

For this repository, the compatibility is just there. There’s nothing to enable or disable so there’s not really a “status” so to speak.

@chrisguttandin to use positionStrategy without zone if you call “updatePosition” after attaching it works fine

    const config = new OverlayConfig({
      positionStrategy: this.overlay
        .position()
        .flexibleConnectedTo(this.dropdown)
        .withPositions([
          {
            originX: 'start',
            originY: 'bottom',
            overlayX: 'start',
            overlayY: 'top',
          },
        ]).withPush(true),
    });

    this.fusilliOverlayRef = this.overlay.create(config);
    this.fusilliOverlayRef.backdropClick().subscribe(() => {
      this.fusilliOverlayRef.dispose();
    });

    this.fusilliOverlayRef.attach(
      new ComponentPortal(TravellersComponent, this.viewContainerRef)
    );

    this.fusilliOverlayRef.updatePosition();
  }```

Hello?