Comparing changes

…server (#178) Angular's dev-mode ImagePerformanceWarning only bails out early when PerformanceObserver is missing or both image warnings are disabled. NativeScript runtimes that ship a Web Performance API now define that global, so the service proceeds to getDocument() and throws NG0210, failing every debug boot. Default IMAGE_CONFIG to disabled for both warnings — NativeScript has no <img> elements for them to scan. Apps can still override it, since their own providers are applied after the NativeScript ones. (cherry picked from commit 6daed00)

) * Angular discovers some optional configuration by reading the DOM. The CSP_NONCE default factory, for example, evaluates `DOCUMENT.body.querySelector('[ngCspNonce]')`. `NativeScriptDocument.body` was a hollow object, so the optional chaining in those probes did not help and they failed with `body?.querySelector is not a function`. Signal forms reach this on the first `[formField]` binding, which crashed every signal-form dialog at construction. * `querySelector`, `querySelectorAll`, `getElementById`, `getElementsByTagName` and `getElementsByClassName` now answer "nothing found" on the document and on `body`/`head`. `createElement` still throws, since constructing real nodes is a caller bug rather than a probe. * CSP_NONCE is also provided as `null`, as there is no CSP in a NativeScript runtime. It has to be a root provider: the root injector resolves `providedIn: 'root'` tokens itself before consulting the platform injector, so providing it in COMMON_PROVIDERS would have had no effect. (cherry picked from commit 5a5315d)

…#179) afterClosed was emitted by a hardcoded 100ms fallback timer while the iOS dismissal animation (~400ms) was still running, so opening another dialog from afterClosed failed with "the modal view could not be presented". The 'closed' state is now driven by core's showModal closeCallback, which fires once the native dismissal has completed, plus a one-shot 'unloaded' listener scoped inside it so background-driven unloads can't masquerade as a close. The timer remains only as a 5s safety net. Both portal types now share the same show/dismiss path, which also makes natively-dismissed template dialogs emit afterClosed, and afterOpened is wired to shownModally (it never fired before). (cherry picked from commit 1fcbca7)

(cherry picked from commit d130ff8)

(cherry picked from commit 614d141)

Navigation Menu

Repository navigation

Comparing changes

Open a pull request

Commits on Oct 2, 2026

This comparison is taking too long to generate.

Uh oh!