Skip to content

bug(mdc-dialog): afterClosed observable no longer in the NgZone #21696

@mmalerba

Description

@mmalerba

We got an internal bug report about this:

Observed behavior

Prior the MDC migration the following router navigation was happening inside of the NgZone.
After migration to MDC, this navigation is no longer happening in the NgZone.

Expected behavior

Callbacks for the afterClosed Observable should be in the NgZone

Steps to reproduce

  1. Open a dialog
  2. Subscribe to afterClosed()
  3. Navigate within the callback, the Route complains that it is not in the NgZone

Metadata

Metadata

Assignees

Labels

GThis is is related to a Google internal issueP2The issue is important to a large percentage of users, with a workaroundarea: material/dialog

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions