Which @angular/* package(s) are the source of the bug?
zone.js
Is this a regression?
Yes
Description
Since version 0.14.6 of zone.js, the functionality of the AbortController seems broken.
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-dq9ojm?file=src%2Fmain.ts
Please provide the exception or error you saw
With zone.js 0.14.5 the AbortController was working correctly, but with 0.14.6 it started to be broken.
Reproduction:
1. Open https://stackblitz.com/edit/stackblitz-starters-dq9ojm?file=src%2Fmain.ts
2. Click on "Click" button
3. Alert message is presented
4. Click on "Abort" button
5. Click on "Click" button and the alert message is still presented, although the abort() method of the AbortController was called.
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 18.0.1
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64
Angular: 18.0.0
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1800.1
@angular-devkit/build-angular 18.0.1
@angular-devkit/core 18.0.1
@angular-devkit/schematics 18.0.1
@angular/cli 18.0.1
@schematics/angular 18.0.1
rxjs 7.8.1
typescript 5.4.5
zone.js 0.14.6
Anything else?
Related PR which probably broke the behavior: #55339
Which @angular/* package(s) are the source of the bug?
zone.js
Is this a regression?
Yes
Description
Since version 0.14.6 of zone.js, the functionality of the AbortController seems broken.
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/stackblitz-starters-dq9ojm?file=src%2Fmain.ts
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version)Anything else?
Related PR which probably broke the behavior: #55339