internlm/SWE-Fixer-Train-110K huggingface dataset:
Repository: nvaccess/nvda

Issue:
NVDA does not report that text is "hidden" when show formatting is enabled in Word (365 at least)
<!--
Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
-->

### Steps to reproduce:

Open Word, type some text, including hidden text.  To hide text, press CONTROL+D to open the font formatting dialog, then press alt+h to toggle the "hidden" effect.  Press ENTER to close.

Press CONTROL+SHIFT+8 to toggle show formatting.

Ensure font attributes is checked in NVDA's document formatting settings.

### Actual behavior:

With Show formatting enabled the hidden text is visible.  NVDA reads it as any other text, but does not report that the text is set to hidden (as it would for bold or underlined text, for instance).

With Show formatting disabled, the text is hidden, there is no visual cue and NVDA reads the document as if the hidden text did not exist (the correct behaviour).

### Expected behavior:

With show formatting enabled, NVDA should report that the text is "hidden" just as it would for other font attributes like italic.

With Show formatting disabled, the text is hidden, there is no visual cue and NVDA reads the document as if the hidden text did not exist (the correct behaviour).

### System configuration:

Windows 10 Version: 
Version 1809 Fast insider 17751.1 
 
Office 365 Version: 
16.0.10325.20118 

#### NVDA version:

alpha-15933,b3aff97c Installed
2018.3beta3 portable

#### Does the issue still occur after restarting your PC?

Yes



Discussion:

Resolving patch:
diff --git a/source/speech/__init__.py b/source/speech/__init__.py
--- a/source/speech/__init__.py
+++ b/source/speech/__init__.py
@@ -1571,6 +1571,16 @@ def getFormatFieldSpeech(attrs,attrsCache=None,formatConfig=None,reason=None,uni
 				# Translators: Reported when text is not underlined.
 				else _("not underlined"))
 			textList.append(text)
+		hidden = attrs.get("hidden")
+		oldHidden = attrsCache.get("hidden") if attrsCache is not None else None
+		if (hidden or oldHidden is not None) and hidden != oldHidden:
+			text = (
+				# Translators: Reported when text is hidden.
+				_("hidden")if hidden
+				# Translators: Reported when text is not hidden.
+				else _("not hidden")
+			)
+			textList.append(text)
 		textPosition=attrs.get("text-position")
 		oldTextPosition=attrsCache.get("text-position") if attrsCache is not None else None
 		if (textPosition or oldTextPosition is not None) and textPosition!=oldTextPosition:


Test patch:
Repository: nvaccess/nvda

Issue:
redundant speech when navigating trees in eclipse
<!--
Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
-->

### Steps to reproduce:
1. open eclipse and press alt+shift+q p to go to package explorer
2. use arrows to navigate the tree
### Actual behavior:
nvda reads the item it is leaving and the item that got focus 
### Expected behavior:
read only the item that got focus
### System configuration
#### NVDA installed/portable/running from source:
nvda installed
#### NVDA version:
nvda 2019.2.rc1
#### Windows version:
windows10
#### Name and version of other software in use when reproducing the issue:
spring tool 4
#### Other information about your system:

### Other questions
#### Does the issue still occur after restarting your PC?
yes
#### Have you tried any other versions of NVDA? If so, please report their behaviors.
it also happens in version 2019.1 
I guess some thing changed in windows 


Discussion:

Resolving patch:
diff --git a/source/appModules/springtoolsuite4.py b/source/appModules/springtoolsuite4.py
new file mode 100644
--- /dev/null
+++ b/source/appModules/springtoolsuite4.py
@@ -0,0 +1,13 @@
+# -*- coding: UTF-8 -*-
+# A part of NonVisual Desktop Access (NVDA)
+# Copyright (C) 2019 NV Access Limited, Łukasz Golonka
+# This file may be used under the terms of the GNU General Public License, version 2 or later.
+# For more details see: https://www.gnu.org/licenses/gpl-2.0.html
+
+""" App module for Spring Tool Suite version 4
+This simply uses the app module for Eclipse.
+"""
+
+# Normally these Flake8 errors shouldn't be ignored but here we are simply reusing existing ap module.
+
+from .eclipse import *  # noqa: F401, F403


Test patch:
Repository: nvaccess/nvda

Issue:
Windows 10 20H1/Windows Search: add SearchApp as an alias for SearchUI
Hi,

This issue should have been brought up in the first place... I was hoping to delay it until February but looks like it must be done now:

### Is your feature request related to a problem? Please describe.
In Windows 10 20H1 (particularly after build 18963), Start Menu/Windows Search executable has been renamed form SearchUI to SearchApp. Because of this, pull requests dealing with Windows Search (such as #10329 and #10341) will fail on 20H1 builds.

### Describe the solution you'd like
Add searchapp.py as an alias for searchui app module.

### Describe alternatives you've considered
Leave it as is.

### Additional context
Applicable in 20H1 and later - 1909 still ships with SearchUI.exe. As this affects current and future issues, it should be included as soon as possible.

Thanks.


Discussion:

Resolving patch:
diff --git a/source/appModules/searchapp.py b/source/appModules/searchapp.py
new file mode 100644
--- /dev/null
+++ b/source/appModules/searchapp.py
@@ -0,0 +1,10 @@
+# A part of NonVisual Desktop Access (NVDA)
+# Copyright (C) 2019 NV Access Limited, Joseph Lee
+# This file is covered by the GNU General Public License.
+# See the file COPYING for more details.
+
+"""Windows Search app module for Windows 10 build 18965 and later.
+"""
+
+# Flake8/F403: this is an alias for SearchUI app module.
+from .searchui import * # NOQA


Test patch:
Repository: nvaccess/nvda

Issue:
Modern keyboard: add support for Text Input Host, a renamed form of modern keyboard in 20H1
Hi,

Another foundation for 20H1 feature support and testing:

### Is your feature request related to a problem? Please describe.
In Windows 10 build 18963, modern keyboard executable has been renamed to Text Input Host 9textinputhost.exe). Unlike initial version of modern keyboard, this name does not break Python's naming conventions and better describes what the app actually does.

Adding support for the renamed modern keyboard is needed to test 20H1 modern input features such as modern CJK IME and other possible enhancements.

### Describe the solution you'd like
Add an app module for Text Input Host which is an alias for current modern keyboard app module. Work on modern keyboard will continue from the old module.

### Describe alternatives you've considered
Leave it as is.

### Additional context
This support is needed for 20H1 onwards.

Thanks.


Discussion:

Resolving patch:
diff --git a/source/appModules/textinputhost.py b/source/appModules/textinputhost.py
new file mode 100644
--- /dev/null
+++ b/source/appModules/textinputhost.py
@@ -0,0 +1,11 @@
+# App module for Text Inpur Hoar (formerly Composable Shell (CShell) input panel)
+# A part of NonVisual Desktop Access (NVDA)
+# Copyright (C) 2019 NV Access Limited, Joseph Lee
+# This file is covered by the GNU General Public License.
+# See the file COPYING for more details.
+
+"""App module for Windows 10 Modern Keyboard aka new touch keyboard panel.
+This is for 20H1 text input host window."""
+
+# Flake8/F403: alias of Composable Shell modern keyboard app module.
+from .windowsinternal_composableshell_experiences_textinput_inputapp import * # NOQA


Test patch:
Repository: nvaccess/nvda

Issue:
Some bullets not read correctly on MS Word
<!--
Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
-->

### Steps to reproduce:

First bullet:

* Open a new document MS Word
* Type "`* Item 1`" to start a bullet list
* Press Enter
* Press 2 times Tab

Second bullet:

* Open a new document MS Word
* Type "`-> Item 2`" to produce a line with heavy right arrow

### Actual behavior:

Bullet 1: NVDA announce "black club"

Bullet 2: NVDA announces "right double arrow"

### Expected behavior:

Bullet 1: NVDA announces "square bullet"

Bullet 2: NVDA announces "right arrow" or something else not including the word "double"

### System configuration
#### NVDA installed/portable/running from source:

INSTALLED

#### NVDA version:

2019.2.1

#### Windows version:

Windows 10

#### Name and version of other software in use when reproducing the issue:

MS Word 2016

#### Other information about your system:

### Other questions
#### Does the issue still occur after restarting your PC?

Yes

#### Have you tried any other versions of NVDA? If so, please report their behaviors.

No but remember that this issue was already present at least in 2019.1



Discussion:

Resolving patch:
diff --git a/source/NVDAObjects/window/winword.py b/source/NVDAObjects/window/winword.py
--- a/source/NVDAObjects/window/winword.py
+++ b/source/NVDAObjects/window/winword.py
@@ -328,19 +328,19 @@
 }
 formatConfigFlag_includeLayoutTables=0x20000
 
-# Map some characters from PUA to Unicode. Meant to be used with bullets only.
+# Map some characters from 0 to Unicode. Meant to be used with bullets only.
 # Doesn't care about the actual font, so can give incorrect Unicode in rare cases.
 mapPUAToUnicode = {
 	# from : to # fontname
-	u'\uF06E' : u'\u25A0', # Wingdings
-	u'\uF076' : u'\u2756', # Wingdings
-	u'\uF0A7' : u'\u2663', # Symbol
-	u'\uF0A8' : u'\u2666', # Symbol
-	u'\uF0B7' : u'\u2022', # Symbol
-	u'\uF0D8' : u'\u27A2', # Wingdings
-	u'\uF0E8' : u'\u21D2', # Wingdings
-	u'\uF0F0' : u'\u21E8', # Wingdings
-	u'\uF0FC' : u'\u2714', # Wingdings
+	u'\uF06E': u'\u25A0',  # Wingdings (black square)
+	u'\uF076': u'\u2756',  # Wingdings (black diamond minus white x
+	u'\uF0A7': u'\u25AA',  # Symbol (black small square)
+	u'\uF0A8': u'\u2666',  # Symbol (black diamond suit)
+	u'\uF0B7': u'\u2022',  # Symbol (bullet)
+	u'\uF0D8': u'\u2B9A',  # Wingdings (three-D top-lighted RIGHTWARDS equilateral arrowhead)
+	u'\uF0E8': u'\U0001f87a',  # Wingdings (wide-headed rightwards heavy barb arrow)
+	u'\uF0F0': u'\u21E8',  # Wingdings (right white arrow)
+	u'\uF0FC': u'\u2714',  # Wingdings (heavy check mark)
 }
 
 class WordDocumentHeadingQuickNavItem(browseMode.TextInfoQuickNavItem):


Test patch:
Repository: nvaccess/nvda

Issue:
Windows 10 Settings: volume progress bar beep is heard in System/Sound
Hi,

Following from #10410 discussion:

### Steps to reproduce:
This requires add-ons to be disabled and one must be running Windows 10 Version 1803 or later:

1. Open Settings (Windows+I).
2. Navigate to System/Sound.

### Actual behavior:
Progress beep for output/input is heard.

### Expected behavior:
No progress beep.

### System configuration
#### NVDA installed/portable/running from source:
Installed

#### NVDA version:
Alpha.18986

#### Windows version:
Windows 10 Version 1909

#### Name and version of other software in use when reproducing the issue:
None

#### Other information about your system:
None

### Other questions
#### Does the issue still occur after restarting your PC?
Yes

#### Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes - 2019.2.1 and 2019.1.

### Technical information:
This is caused by volume meter progress bar, which should not have been a progress bar in the first place. A fix is included in Windows 10 App Essentials add-on.



Discussion:

Resolving patch:
diff --git a/source/appModules/systemsettings.py b/source/appModules/systemsettings.py
new file mode 100644
--- /dev/null
+++ b/source/appModules/systemsettings.py
@@ -0,0 +1,36 @@
+# appModules/systemsettings.py
+# A part of NonVisual Desktop Access (NVDA)
+# Copyright (C) 2019 NV Access Limited, Joseph Lee
+# This file is covered by the GNU General Public License.
+# See the file COPYING for more details.
+
+"""App module for Windows 10 Settings app (aka Immersive Control Panel)."""
+
+import appModuleHandler
+from NVDAObjects.UIA import UIA
+from NVDAObjects.behaviors import ProgressBar
+
+
+class AppModule(appModuleHandler.AppModule):
+
+	def chooseNVDAObjectOverlayClasses(self, obj, clsList):
+		if isinstance(obj, UIA):
+			# #10411: In build 17035, Settings/System/Sound has been added, but has an anoying volume meter.
+			if obj.UIAElement.cachedClassName == "ProgressBar" and isinstance(obj.next, UIA):
+				# Due to Storage Sense UI redesign in build 18277,
+				# the progress bar's sibling might not be a UIA object at all.
+				try:
+					if (
+						obj.next.UIAElement.cachedAutomationID.startswith(
+							"SystemSettings_Audio_Output_VolumeValue_"
+						)
+						or obj.simplePrevious.UIAElement.cachedAutomationID.startswith(
+							"SystemSettings_Audio_Input_VolumeValue_"
+						)
+					):
+						try:
+							clsList.remove(ProgressBar)
+						except ValueError:
+							pass
+				except AttributeError:
+					pass


Test patch:
Repository: nvaccess/nvda

Issue:
in the Start Menu when focus is on the search box and user presses up arrow to go to All Programs, NVDA says blank All Programs (and all the information with it)
**Reported by blindbhavya on 2014-07-19 08:33**
Steps to reproduce
Press Ctrl + Esc to launch the Start Menu.
Your focus will be on the search box.
Press up arrow to go to All Programs.
NVDA will say blank all programs.
So, NVDA should not say blank.



Discussion:
Comment 1 by jteh on 2014-07-20 22:25
This occurs because the search box is an edit field and blank is reported in an edit field when you press up arrow and the field is blank. We'd probably need to special case this specific box to fix it.

Comment 2 by blindbhavya on 2014-07-21 13:09
Ok.

cc @bhavyashah 
Giving this p4, since although it is annoying, it is not at all live threatening and probably not very trivial to fix.
@bhavyashah can you still reproduce the issue?
Still reproducible on Windows 7.

Resolving patch:
diff --git a/source/editableText.py b/source/editableText.py
--- a/source/editableText.py
+++ b/source/editableText.py
@@ -135,7 +135,7 @@ def _hasCaretMoved(self, bookmark, retryInterval=0.01, timeout=None, origWord=No
 		return (False,newInfo)
 
 	def _caretScriptPostMovedHelper(self, speakUnit, gesture, info=None):
-		if isScriptWaiting():
+		if isScriptWaiting() or eventHandler.isPendingEvents("gainFocus"):
 			return
 		if not info:
 			try:


Test patch:
Repository: nvaccess/nvda

Issue:
repetition when focusing a console window
<!--
Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
Issues may be closed if the required information is not present.
https://github.com/nvaccess/nvda/wiki/Github-issue-template-explanation-and-examples
-->

### Steps to reproduce:
open a console window, in my case I open bash
2. open any other windows such a browser. 
3. tab back to your console window.
### Actual behavior:
I hear root@Computer name, window, terminal, selected, terminal selected
### Expected behavior:
hearing only the window name, + "console" to know the type of focused app
### System configuration
core -i7 24 gb ram, ssd drive
#### NVDA installed/portable/running from source:
installed
#### NVDA version:
alpha-18290,7b5cd2d0
#### Windows version:
windows Version 1903 (OS Build 18950.1000)
#### Name and version of other software in use when reproducing the issue:
none
#### Other information about your system:

### Other questions
#### Does the issue still occur after restarting your PC?
yes
#### Have you tried any other versions of NVDA? If so, please report their behaviors.
console work has just landed, so unrelated.


Discussion:
@codeofdusk 
While spurious selections are no longer reported in Windows Console, the terminal object is reported twice. This is likely due to faulty focus redirection:

* Temporarily removing the `consoleUIAWindow._get_focusRedirect` override introduced in #9674 suppresses the extra announcement.
* The `focusRedirect` and initially focused terminal text area seem to be different Python objects: in a Python console invoked by pressing NVDA+control+z from Command Prompt, `nav.parent.focusRedirect == nav`, but `nav.parent.focusRedirect is not nav`.

Cc @feerrenrut @leonardder @michaelDCurran
could one of the admins re-open this so that someone can look into fixing it? 
This was erroneously closed with #10052.
hi 
Does the current issue have a corresponding pr for testing?
thanks

Resolving patch:
diff --git a/source/NVDAObjects/UIA/winConsoleUIA.py b/source/NVDAObjects/UIA/winConsoleUIA.py
--- a/source/NVDAObjects/UIA/winConsoleUIA.py
+++ b/source/NVDAObjects/UIA/winConsoleUIA.py
@@ -250,17 +250,8 @@ def __ne__(self, other):
 
 
 class consoleUIAWindow(Window):
-	def _get_focusRedirect(self):
-		"""
-		Sometimes, attempting to interact with the console too quickly after
-		focusing the window can make NVDA unable to get any caret or review
-		information or receive new text events.
-		To work around this, we must redirect focus to the console text area.
-		"""
-		for child in self.children:
-			if isinstance(child, WinConsoleUIA):
-				return child
-		return None
+	# This is the parent of the console text area, which sometimes gets focus after the text area.
+	shouldAllowUIAFocusEvent = False
 
 
 class WinConsoleUIA(KeyboardHandlerBasedTypedCharSupport):


Test patch:
Repository: nvaccess/nvda

Issue:
NVDA fails to navigate to landmarks in EdgeHTML-based content
**Note:** The problem occurs not only in the Microsoft Edge browser, but in all places which display content via EdgeHTML (e.g. the Twitter app for Windows 10). I can provide logs for the issue, if necessary.

### Steps to reproduce:
1. Launch NVDA.
2. Open Microsoft Edge (the EdgeHTML-based one).
3. Load a page with some landmarks in it (nvaccess.org should do it).
4. When the page loads, use the "D" key to navigate between landmarks in the loaded document/page.
5. Invoke the elements list (NVDA+F7) and select the "Landmarks" radio-button.

### Actual behavior:
After step 4, NVDA plays an error and no action is taken.
After step 5, NVDA also plays an error and the list of landmarks fails to load in the elements list dialog.

### Expected behavior:
After step 4, NVDA should go to the next available landmark in the document/page.
After step 5, the list of landmarks should be loaded in the elements list dialog.

### System configuration
- Operating system: Windows 10 Pro version 1909 (build 18363.476), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- NVDA version: alpha-19266,67bf1df6, in bulgarian.
- Microsoft Edge version: 44.18362.449.0.
- Microsoft EdgeHTML version: 18.18363.
- Processor: Intel Core i5-9400F at 2.90GHz.
- RAM Memory: 16.00GB.
- Graphics: MSI GeForce GTX-1050TI Gaming X 4G, 4096MB dedicated memory + 4065MB shared system memory, desktop resolution set to 1920x1080.
- Sound Card: Realtek ALC892 at Intel Cannon Point PCH.

### Other questions
#### Does the issue still occur after restarting your PC?
Yes, it does.

#### Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes - v2019.2.1 - it behaves as expected.



Discussion:
Could you please provider a log file?
OK, here is a log attached. Testing done with add-ons disabled and log level set to "Debug".
[NVDA_Log_2019-11-25_#10543.log](https://github.com/nvaccess/nvda/files/3886961/NVDA_Log_2019-11-25_.10543.log)


Resolving patch:
diff --git a/source/UIABrowseMode.py b/source/UIABrowseMode.py
--- a/source/UIABrowseMode.py
+++ b/source/UIABrowseMode.py
@@ -422,7 +422,7 @@ def _iterNodesByType(self,nodeType,direction="next",pos=None):
 		elif nodeType == "landmark":
 			condition = UIAHandler.handler.clientObject.createNotCondition(
 				UIAHandler.handler.clientObject.createPropertyCondition(
-					UIAHandler.uia.UIA_LandmarkTypePropertyId,
+					UIAHandler.UIA.UIA_LandmarkTypePropertyId,
 					0
 				)
 			)


Test patch:
Repository: nvaccess/nvda

Issue:
Add "4.1.2. NVDA Usage Statistics Dialog" in the User Guide
### Steps to reproduce:
Open the NVDA User Guide.
### Actual headlines:
4. Getting started with NVDA
4.1. Launching NVDA
4.1.1. Welcome Dialog
4.2. About NVDA keyboard commands
### Expected behaviour:
Add a new chapter called "4.1.2. NVDA Usage Statistics Dialog" with a little description and a reference to "Allow the NVDA project to gather NVDA usage statistics" in the chapter "11.1.1. General (NVDA+control+g)".
#### Update on 2018-09-04:
And please also write down based on [my comment in PR #8708](https://github.com/nvaccess/nvda/pull/8708#issuecomment-418127349) in the description that the NVDA configuration ("nvda.ini") will be saved automatically by pressing the buttons "Yes" and "No", but not when pressing "Later".
### System configuration:
#### NVDA version:
NVDA 2018.3 Beta 3


Discussion:
This will be also solved by #9730. 

Resolving patch:
diff --git a/source/braille.py b/source/braille.py
--- a/source/braille.py
+++ b/source/braille.py
@@ -76,7 +76,7 @@
 	# Translators: Displayed in braille for an object which is a
 	# graphic.
 	controlTypes.ROLE_GRAPHIC: _("gra"),
-	# Translators: Displayed in braille for an object which is a
+	# Translators: Displayed in braille for toast notifications and for an object which is a
 	# help balloon.
 	controlTypes.ROLE_HELPBALLOON: _("hlp"),
 	# Translators: Displayed in braille for an object which is a


Test patch: