fix(core): Drop special-case disables automatic change detection sche… #63846
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…duling This commit drops special-case handling for old-style "zoneless" that would disable the internal scheduler when zoneless was not explicitly enabled but Zone was not defined. This scheduler is now enabled in _all_ applications, providing consistent expectations for developers. BREAKING CHANGE: Using a combination of `provideZoneChangeDetection` while also removing ZoneJS polyfills will no longer result in the internal scheduler being disabled. All Angular applications now consistenly use the same scheduler, and those with the Zone change detection provider include additional automatic scheduling behaviors based on NgZone stabilization.
angular-robot
bot
added
detected: breaking change
thePunderWoman
approved these changes
Sep 16, 2025
thePunderWoman
added
the
action: merge
|
This PR was merged into the repository. The changes were merged into the following branches:
|
wildcardalice
pushed a commit
to wildcardalice/angular
that referenced
this pull request
Sep 18, 2025
…duling (angular#63846) This commit drops special-case handling for old-style "zoneless" that would disable the internal scheduler when zoneless was not explicitly enabled but Zone was not defined. This scheduler is now enabled in _all_ applications, providing consistent expectations for developers. BREAKING CHANGE: Using a combination of `provideZoneChangeDetection` while also removing ZoneJS polyfills will no longer result in the internal scheduler being disabled. All Angular applications now consistenly use the same scheduler, and those with the Zone change detection provider include additional automatic scheduling behaviors based on NgZone stabilization. PR Close angular#63846
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…duling
This commit drops special-case handling for old-style "zoneless" that would disable the internal scheduler when zoneless was not explicitly enabled but Zone was not defined. This scheduler is now enabled in all applications, providing consistent expectations for developers.
BREAKING CHANGE: Using a combination of
provideZoneChangeDetectionwhile also removing ZoneJS polyfills will no longer result in the internal scheduler being disabled. All Angular applications now consistenly use the same scheduler, and those with the Zone change detection provider include additional automatic scheduling behaviors based on NgZone stabilization.