[vorobey]

PR applies changes for supporting Angular zoneless mode (default for new Angular 21+ apps). Zone-based apps keep working as before; no breaking changes.

• component.ts: injects ChangeDetectorRef and passes it to NgEventsStrategy and EmitterHelper
• events-strategy.ts: fireEvent and fireNgEvent call markForCheck after emitting, so code subscriptions (.subscribe(), instance.on()) re-render the view in zoneless apps
• calling public options triggers markForCheck in component.ts. Form editing a one-way [formData] in place; internal state (hoveredElement, focusedElement) doesn't trigger change detection on hover
• zone.run() / runOutsideAngular() are kept: no-op in zoneless apps, unchanged behavior in zone apps
• tests: new zone and zoneless karma environments (nx-infra-plugin executor, shims) running tests/src/zone-modes, included in test:all; zone.js moved out of the common shim

[Copilot]

🟡 Changes recommended

The new suites are omitted from standard CI execution, and the drag test can mask a missing change-detection trigger.

2 open issues

• Include zone and zoneless environments in wrapper CI tests · New
• Assert mousemove view update before dispatching mouseup · New

What changed in this PR

Adds zone-based and zoneless change-detection tests for the Angular wrappers, supported by new Karma environments.

Changes:

• Adds shared regression tests for both change-detection modes.
• Separates Zone.js polyfills from common test setup.
• Adds Nx test/debug targets and core-file lint directives.

File	Description
packages/​nx-infra-plugin/​src/​executors/​karma-multi-env/​schema.json	Allows both new environments.
packages/​nx-infra-plugin/​src/​executors/​karma-multi-env/​schema.d.ts	Extends environment types.
packages/​nx-infra-plugin/​src/​executors/​karma-multi-env/​karma.types.ts	Maps new environments to shims.
packages/​nx-infra-plugin/​src/​executors/​karma-multi-env/​karma-multi-env.impl.ts	Includes new environments in execution order.
packages/​devextreme-angular/​tests/​src/​zone-modes/​change-detection.spec.ts	Adds change-detection regression tests.
packages/​devextreme-angular/​src/​core/​events-strategy.ts	Adds a lint suppression only.
packages/​devextreme-angular/​src/​core/​component.ts	Adds a lint suppression only.
packages/​devextreme-angular/​project.json	Adds test/debug targets and cache inputs.
packages/​devextreme-angular/​karma.zoneless.test.shim.js	Initializes tests without Zone.js.
packages/​devextreme-angular/​karma.zoneless-testing.module.js	Provides zoneless change detection.
packages/​devextreme-angular/​karma.zone.test.shim.js	Initializes zone-based regression tests.
packages/​devextreme-angular/​karma.zone-polyfills.test.shim.js	Centralizes Zone.js loading.
packages/​devextreme-angular/​karma.test.shim.js	Uses zone polyfills and excludes dedicated suites.
packages/​devextreme-angular/​karma.server.test.shim.js	Uses zone polyfills.
packages/​devextreme-angular/​karma.hydration.test.shim.js	Uses zone polyfills.
packages/​devextreme-angular/​karma.common.test.shim.js	Removes shared Zone.js loading.
packages/​devextreme-angular/​.gitignore	Ignores Chrome Headless artifacts.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Programmatic option-change subscriptions can still leave zoneless views stale.

3 open issues

• Mark for check for direct optionChanged subscribers in zoneless mode · New
• Assert mousemove view update before dispatching mouseup
• Include zone and zoneless environments in wrapper CI tests

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Public instance.on('optionChanged') handlers can still leave zoneless views stale.

3 open issues

• Zoneless public optionChanged listeners fail to trigger view updates · New
• Assert mousemove view update before dispatching mouseup
• Include zone and zoneless environments in wrapper CI tests

1 resolved since last review

• Mark for check for direct optionChanged subscribers in zoneless mode

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Callback-only nested widget events can still leave plain-field updates unrendered in zoneless applications.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Notify Angular for callback-only nested widget actions

packages/​devextreme-angular/​src/​core/​events-strategy.ts:34

The notification is still inside if (emitter.observers.length), so callback-only nested widgets are missed. For example, a toolbar button configured through items[].options.onClick can have no click emitter subscribers. Core _createActionByOption invokes fireEvent before executing the option callback separately (core/widget/component.ts:466–470); updating a plain host field in that callback does not notify Angular, leaving a zoneless view stale unless another change-detection trigger occurs. Cover user-configured option callbacks in the notification path and add a zoneless regression test, while preserving suppression for widget-internal callbacks.

3 resolved since last review

• Zoneless public optionChanged listeners fail to trigger view updates
• Assert mousemove view update before dispatching mouseup
• Include zone and zoneless environments in wrapper CI tests

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The invalid ESLint severity allow blocks the Angular package’s lint checks.

1 open issue

• Use a valid ESLint severity instead of allow · New

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Shared scheduling changes retain correctness and performance concerns and need runtime validation across both Angular modes.

2 open issues

• Schedule checks after imperative form-control writes in zoneless apps · New
• Avoid scheduling checks for nested strategies’ internal events · New

1 resolved since last review

• Use a valid ESLint severity instead of allow

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The listener wrapper breaks supported object callbacks, and the shared scheduling changes still need browser regression validation in both Angular modes.

1 open issue

• Preserve EventListenerObject callbacks in domAdapter.listen · New

2 resolved since last review

• Avoid scheduling checks for nested strategies’ internal events
• Schedule checks after imperative form-control writes in zoneless apps

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Shared lifecycle and event-dispatch changes require runtime validation and human review, with a callback-contract regression still unresolved.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Handle EventListenerObject callbacks in DOM event overrides

packages/​devextreme-angular/​src/​core/​integration.ts:54

The DOM adapter explicitly accepts EventListenerObject callbacks (ListenCallback in packages/devextreme/js/__internal/core/dom_adapter.ts), not just functions. After this override is installed, registering a supported { handleEvent(...) { ... } } listener for mousemove, mouseover, or mouseout now throws TypeError: callback.call is not a function when the event fires. Preserve that callback contract by invoking handleEvent for object listeners.

1 resolved since last review

• Preserve EventListenerObject callbacks in domAdapter.listen

_{Review effort: Balanced}