HP Secure Browser support (#16377): Detect brchrome and flag it as no…

…t supporting IAccessible2. (#16392)

Summary of the issue:
Users have to explicitly configure in NVDA advanced options to "use UIA
for Edge and other chromium based browsers", for NVDA to work with HP Secure Browser.

Description of user facing changes:
Users won't have to explicitly configure UIA for all chromium-based browsers when
they want to use HP Secure Browser

Description of development approach:
Detect browser with a process name of "brchrome" which represents HP Secure Browser
and flag it as not supporting IAccecssible2. In this scenario, UIA will be
used by default for HP SB.

Co-authored-by: Tomasz Wroblewski <tomasz.wroblewski@hp.com>

source/UIAHandler/__init__.py

@@ -1204,7 +1204,9 @@ def _isUIAWindowHelper(self, hwnd: int, isDebug=False) -> bool:  # noqa: C901
 				# As their IA2 implementation is still better at the moment.
 				# However, in cases where Chromium is running under another logon session,
 				# the IAccessible2 implementation is unavailable.
-				hasAccessToIA2 = not appModule.isRunningUnderDifferentLogonSession
+				# 'brchrome' is part of HP SureClick, a chromium-based browser which runs webpages to run in separate
+				# virtual machines - it supports UIA remoting but not IAccessible2 remoting.
+				hasAccessToIA2 = not appModule.isRunningUnderDifferentLogonSession and not appModule.appName == "brchrome"
 				if (
 					AllowUiaInChromium.getConfig() == AllowUiaInChromium.NO
 					# Disabling is only useful if we can inject in-process (and use our older code)