Skip to content

Commit 71f8508

Browse files
[Word] Remove content related to rolled-back feature (#5312)
1 parent 3adb6e1 commit 71f8508

File tree

3 files changed

+1
-17
lines changed

3 files changed

+1
-17
lines changed
-11.3 KB
Binary file not shown.
-12.1 KB
Binary file not shown.

docs/word/word-add-ins-troubleshooting.md

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Word add-ins
33
description: Learn how to troubleshoot development errors in Word add-ins.
4-
ms.date: 03/26/2025
4+
ms.date: 08/05/2025
55
ms.topic: troubleshooting
66
ms.localizationpriority: medium
77
---
@@ -86,22 +86,6 @@ Formatting properties such as [color](/javascript/api/word/word.font#word-word-f
8686
- If all text in the range has the same font color, `range.font.color` specifies that color.
8787
- If multiple font colors are present within the range, `range.font.color` is `null`.
8888

89-
## My add-in can no longer find the correct Word window
90-
91-
Microsoft Word, like other Windows applications, uses a hierarchy of windows to display documents and UI to users. These windows can be identified by window handles or class names. As of Office Version 2502 (Build 18526.20118), one of the windows in Word's hierarchy was removed.
92-
93-
It's possible that your Word add-in has a rigid dependency on Word's previous window hierarchy and so crashes or no longer works correctly. For an example issue, see [Possibly Microsoft 365 Office Apps updates crashing my Word Addin](https://aka.ms/word-wwf-crash-issue). We recommend that developers not rely on a particular window hierarchical structure. Instead, the current guidance is to search for a window's class name. To find the top-level Word window, search for the "OpusApp" class name. To find the window displaying an open Word document, search for the "_WwG" class name.
94-
95-
The following shows an example of the previous Word window hierarchy.
96-
97-
:::image type="content" source="../images/word-window-hierarchy-before.png" alt-text="Previous Word window hierarchy.":::
98-
99-
The following shows an example of the new window hierarchy. Note that the intermediate window with the "_WwF" class name is no longer present.
100-
101-
:::image type="content" source="../images/word-window-hierarchy-after.png" alt-text="New Word window hierarchy.":::
102-
103-
You can use a debugging tool like [Spy++](/visualstudio/debugger/using-spy-increment) to inspect an application's window hierarchy. However, keep in mind that the hierarchy could further change in the future.
104-
10589
## Native JavaScript APIs don't work with Word.Table
10690

10791
The [Word.Table](/javascript/api/word/word.table) object is different from an [HTML table object](https://developer.mozilla.org/docs/Learn_web_development/Core/Structuring_content/HTML_table_basics). The native JavaScript APIs used to interact with an HTML table can't be used to manage a Word.Table object. Instead, you must use the [Table APIs](/javascript/api/word/word.table) available in the Word Object Model to interact with Word.Table and related objects.

0 commit comments

Comments
 (0)