Skip to content

Error in MS Word when pressing nvda+shift+h #11465

@Adriani90

Description

@Adriani90

Steps to reproduce:

  1. Open NVDA
  2. Open a Word document
  3. Press nvda+shift+h

Actual behavior:

NVDA plays an error sound and following error is written to the log:

IO - inputCore.InputManager.executeGesture (20:49:12.247) - winInputHook (11156):
Input: kb(laptop):shift+NVDA+h
ERROR - scriptHandler.executeScript (20:49:12.262) - MainThread (14468):
error executing script: <bound method WordDocument.script_reportCurrentHeaders of <NVDAObjects.IAccessible.winword.WordDocument object at 0x026340F0>> with gesture 'Umschalt+NVDA+h'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 208, in executeScript
  File "NVDAObjects\IAccessible\winword.pyc", line 260, in script_reportCurrentHeaders
  File "comtypesMonkeyPatches.pyc", line 82, in new__getattr__
  File "comtypes\client\lazybind.pyc", line 168, in __getattr__
  File "comtypes\automation.pyc", line 729, in _invoke
  File "comtypesMonkeyPatches.pyc", line 26, in __call__
_ctypes.COMError: (-2146822347, None, ('Das angeforderte Element ist nicht in der Sammlung vorhanden.', 'Microsoft Word', 'wdmain11.chm', 25421, None))

Expected behavior:

The script sugerates that NVDA should report current heading. However, I don't remember such feature being implemented in NVDA ever. Expected is either reporting of current heading if any, or "no headings" in case there are no headings in the document.
Otherwise report "not supported".

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

NVDA Version: alpha-20677,8f1d6c88

Windows version:

Windows 10 2004 update

Name and version of other software in use when reproducing the issue:

MÎcrosoft Word 365

Other information about your system:

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.

no

If addons are disabled, is your problem still occuring?

yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

n/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/microsoft-officep4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions