From c453f5dc2ffbd7d9c24576ea07a6eaa764b6baca Mon Sep 17 00:00:00 2001 From: Timon Date: Sun, 1 Dec 2024 15:12:45 +0000 Subject: [PATCH] docs(core): fix eventCoalescing comment (#57097) PR Close #57097 --- .../change_detection/scheduling/ng_zone_scheduling.ts | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/packages/core/src/change_detection/scheduling/ng_zone_scheduling.ts b/packages/core/src/change_detection/scheduling/ng_zone_scheduling.ts index 805e8824b1a..da5b7378526 100644 --- a/packages/core/src/change_detection/scheduling/ng_zone_scheduling.ts +++ b/packages/core/src/change_detection/scheduling/ng_zone_scheduling.ts @@ -189,14 +189,13 @@ export interface NgZoneOptions { * * When button is clicked, because of the event bubbling, both * event handlers will be called and 2 change detections will be - * triggered. We can coalesce such kind of events to only trigger + * triggered. We can coalesce such kind of events to trigger * change detection only once. * - * By default, this option will be false. So the events will not be - * coalesced and the change detection will be triggered multiple times. - * And if this option be set to true, the change detection will be - * triggered async by scheduling a animation frame. So in the case above, - * the change detection will only be triggered once. + * By default, this option is set to false, meaning events will + * not be coalesced, and change detection will be triggered multiple times. + * If this option is set to true, change detection will be triggered + * once in the scenario described above. */ eventCoalescing?: boolean;