UIAHandler: Do not use UIA for Chrome_RenderWidgetHostHWND windows (#…

…10675)

* UIAHandler: Do not use UIA for Chrome_RenderWidgetHostHWND windows as their UIA implementation is not complete, and our IA2 support for Chrome is much better.

* Address linting issues.

source/_UIAHandler.py

@@ -51,22 +51,25 @@
 badUIAWindowClassNames=[
 	# UIA events of candidate window interfere with MSAA events.
 	"Microsoft.IME.CandidateWindow.View",
-"SysTreeView32",
-"WuDuiListView",
-"ComboBox",
-"msctls_progress32",
-"Edit",
-"CommonPlacesWrapperWndClass",
-"SysMonthCal32",
-"SUPERGRID", #Outlook 2010 message list
-"RichEdit",
-"RichEdit20",
-"RICHEDIT50W",
-"SysListView32",
-"EXCEL7",
-"Button",
-# #8944: The Foxit UIA implementation is incomplete and should not be used for now.
-"FoxitDocWnd",
+	"SysTreeView32",
+	"WuDuiListView",
+	"ComboBox",
+	"msctls_progress32",
+	"Edit",
+	"CommonPlacesWrapperWndClass",
+	"SysMonthCal32",
+	"SUPERGRID",  # Outlook 2010 message list
+	"RichEdit",
+	"RichEdit20",
+	"RICHEDIT50W",
+	"SysListView32",
+	"EXCEL7",
+	"Button",
+	# #8944: The Foxit UIA implementation is incomplete and should not be used for now.
+	"FoxitDocWnd",
+	# All Chromium implementations (including Edge) should not be UIA,
+	# As their IA2 implementation is still better at the moment.
+	"Chrome_RenderWidgetHostHWND",
 ]
 
 # #8405: used to detect UIA dialogs prior to Windows 10 RS5.