…onEventNoWindowHandle method to determine if notifications should be received from elements without hwnd set. Re nvaccess#18220.

Similar to UIA propewrty change event handler: add a method in the base app module to say yes or no if asked to process UIA notification events for elements (senders) without window handle defined. Method signature is same as UIA notification event except arguments other than sender (element) are keyword arguments - not all app modules may wish to work with all UIA notification event arguments. By default, this method will return False for compatibility with previous NVDA behavior of dropping notification events without window handle set.

…as 'widow handle' if native window handle is not set for an element. Re nvaccess#18220.

UIA NVDA objects need window handle as part of its construction, including while processing events. However, some elements with important notifications (notably window visual state notifications) do not set native window handle property. Therefore, set foreground window handle as the element's 'window handle' to allow notification event to propagate across handlers (global plugins, app modules, NVDA object).

…from everywhere. Re nvaccess#17841, nvaccess#18175.

The element that reports window visual state changes (restore/masimize/minimize/snap) does not define a native window handle property. Therefore, let File Explorer app module say 'yes' when asked to process UIA notification event from this element. Note that this is not the only time a 'no window handle notification' is used - the other case is input layout switch notifications (say, changing between input languages), thus limit processing to snap anouncements.

…ncement (Windows 11 24H2 and Server 2025 and later). Re nvaccess#17841, nvaccess#18175, nvaccess#18220

…ess#18220.

Nearest window handle getter from UIA handler can say 'None' if window is not found, and calling bool(None) gives False. Therefore, use the boolean transformation of the nearest window handle call as base implementation for 'shouldProcessUIANotificationEvent' method.

…fic cases when asked to process UIA notification event. Re nvaccess#17841, nvaccess#18220

…dow handle can report notifications only if app modules say so). Re nvaccess#17841, nvaccess#18220

…call. Re nvaccess#18220

…ment in notification event handler. Re nvaccess#18220.

Note from Sascha Cowley (NV ACcess): add type hints please (do this in app modules by importing UIA client from COM interfaces).

… to UIA elements without window handles. Re nvaccess#18220.

NOte from reviewers: would it be better to use desktop window handle rather than foreground handle? The issue: some UIA elements do not connect back to the desktop through UIA tree traversal. The foreground window handle makes sense when handling the primary case of window visual state announcement, but there are other places where UIA notification events without window handles (at least from NVDA's perspective) will be seen such as Voice Access (Windows 11). Therefore, switch to using desktop window handle to communicate the need to handle notification events more generically.

# Conflicts:
#	user_docs/en/changes.md