Google Chrome: navigating in an Input Composition for east-Asian characters no longer...

Fixes #4080

diff --git a/source/NVDAObjects/IAccessible/chromium.py b/source/NVDAObjects/IAccessible/chromium.py
index 0837b47..e03367b 100644 (file)
--- a/source/NVDAObjects/IAccessible/chromium.py
+++ b/source/NVDAObjects/IAccessible/chromium.py
@@ -20,6 +20,9 @@ class ChromeVBuf(GeckoVBuf):
        def __contains__(self, obj):\r
                if obj.windowHandle != self.rootNVDAObject.windowHandle:\r
                        return False\r
+               if not isinstance(obj,ia2Web.Ia2Web):\r
+                       # #4080: Input composition NVDAObjects are the same window but not IAccessible2!\r
+                       return False\r
                accId = obj.IA2UniqueID\r
                if accId == self.rootID:\r
                        return True\r

diff --git a/user_docs/en/changes.t2t b/user_docs/en/changes.t2t
index 7dea263..cc023e2 100644 (file)
--- a/user_docs/en/changes.t2t
+++ b/user_docs/en/changes.t2t
@@ -45,6 +45,7 @@
 - Touch screen hovers are no longer reported in input help. (#5652)\r
 - NVDA no longer fails to list comments in the Elements List for Excel if a comment is  on a merged cell. (#5704)\r
 - In a very rare case, NVDA no longer fails to read sheet content in Excel with report row and column headers enabled (#5705)\r
+- In Google Chrome, navigating within an Input composition for east-asian characters no longer fails with an error. (#4080)\r
 \r
 \r
 == Changes for Developers ==\r