Hi,
Regression caused by #14838
Steps to reproduce:
After installing alpha-30080,dd8a44cf, open emoji panel (Windows+Period) on Windows 11 and use arrow keys to navigate the emoji panel.
Actual behavior:
NVDA does not announce emoji panel entries when arrow keys are pressed.
Expected behavior:
NVDA announces emoji panel entries when arrow keys are pressed.
NVDA logs, crash dumps and other attachments:
Developer info for emoji panel text field:
name: 'Search recently used emojis, gifs and more'
role: EDITABLETEXT
processID: 25048
roleText: None
states: FOCUSABLE, FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.UIA.XamlEditableText object at 0x08981F10>
Python class mro: (<class 'NVDAObjects.UIA.XamlEditableText'>, <class 'NVDAObjects.behaviors.EditableTextBase'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)
description: ''
location: RectLTWH(left=267, top=681, width=417, height=29)
value: ''
TextInfo: <class 'NVDAObjects.UIA.UIATextInfo'>
appModule: AppModule(windowsinternal_composableshell_experiences_textinput_inputapp, appName='textinputhost', processID=25048)
appModule.productName: 'MicrosoftWindows.Client.CBS'
appModule.productVersion: '1000.22679.1000.0'
appModule.helperLocalBindingHandle: c_long(72297384)
windowHandle: 132700
windowClassName: 'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
extendedWindowStyle: 136839176
windowThreadID: 21144
windowText: 'Windows Input Experience'
displayText: ''
UIAElement: <POINTER(IUIAutomationElement) ptr=0x692af58 at 11ef4e0>
UIA automationID: Windows.Shell.InputApp.FloatingSuggestionUI.DelegationTextBox
UIA frameworkID: XAML
UIA runtimeID: (42, 132700, 4, 15)
UIA providerDescription: [pid:25048,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: TextBox
UIA patterns available: TextPattern, ScrollItemPattern, TextEditPattern, LegacyIAccessiblePattern, ValuePattern
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-30080,dd8a44cf
Windows version:
Windows 11 23H2 beta (build 22635)
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Used as a development workstation
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Emoji panel can be navigated correctly in older alpha releases and on 2023.3
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Cause and solution:
Windows 11 emoji panel text fields are seen as XAML edit fields. Resolving this wil require editing modern keyboard app module to remove the updated class when choosing overlay classes.
Thanks.
Hi,
Regression caused by #14838
Steps to reproduce:
After installing alpha-30080,dd8a44cf, open emoji panel (Windows+Period) on Windows 11 and use arrow keys to navigate the emoji panel.
Actual behavior:
NVDA does not announce emoji panel entries when arrow keys are pressed.
Expected behavior:
NVDA announces emoji panel entries when arrow keys are pressed.
NVDA logs, crash dumps and other attachments:
Developer info for emoji panel text field:
name: 'Search recently used emojis, gifs and more'
role: EDITABLETEXT
processID: 25048
roleText: None
states: FOCUSABLE, FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.UIA.XamlEditableText object at 0x08981F10>
Python class mro: (<class 'NVDAObjects.UIA.XamlEditableText'>, <class 'NVDAObjects.behaviors.EditableTextBase'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)
description: ''
location: RectLTWH(left=267, top=681, width=417, height=29)
value: ''
TextInfo: <class 'NVDAObjects.UIA.UIATextInfo'>
appModule: AppModule(windowsinternal_composableshell_experiences_textinput_inputapp, appName='textinputhost', processID=25048)
appModule.productName: 'MicrosoftWindows.Client.CBS'
appModule.productVersion: '1000.22679.1000.0'
appModule.helperLocalBindingHandle: c_long(72297384)
windowHandle: 132700
windowClassName: 'Windows.UI.Core.CoreWindow'
windowControlID: 0
windowStyle: 1409286144
extendedWindowStyle: 136839176
windowThreadID: 21144
windowText: 'Windows Input Experience'
displayText: ''
UIAElement: <POINTER(IUIAutomationElement) ptr=0x692af58 at 11ef4e0>
UIA automationID: Windows.Shell.InputApp.FloatingSuggestionUI.DelegationTextBox
UIA frameworkID: XAML
UIA runtimeID: (42, 132700, 4, 15)
UIA providerDescription: [pid:25048,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:Windows.UI.Xaml.dll)]
UIA className: TextBox
UIA patterns available: TextPattern, ScrollItemPattern, TextEditPattern, LegacyIAccessiblePattern, ValuePattern
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-30080,dd8a44cf
Windows version:
Windows 11 23H2 beta (build 22635)
Name and version of other software in use when reproducing the issue:
None
Other information about your system:
Used as a development workstation
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Emoji panel can be navigated correctly in older alpha releases and on 2023.3
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
Cause and solution:
Windows 11 emoji panel text fields are seen as XAML edit fields. Resolving this wil require editing modern keyboard app module to remove the updated class when choosing overlay classes.
Thanks.