You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current dev version, 23.04.02-0808f7b-dev, spelling errors aren't indicated onthe braille display when the method for spelling errors is set to dot 7, dot 8, or dots 7 and 8. When using tags as the method, they are indicated in braille. To reproduce, simply go to NVDA -> Braille Extender -> Settings -> Document formatting, click the methods button, and change the method for spelling errors from tags to any of the dot options, then click OK twice. Then, misspell a word in any text entry field in Windows. The screen reader indicates the spelling error, but the braille display does not. Repeating the above instructions but selecting tags instead of a dot option, the braille display properly uses tags to indicate the spelling error.
The text was updated successfully, but these errors were encountered:
now when those advanced document formating options are became a part of the stable version to correct this issue became very important. there was a very active discussion in the german NVDA comunity mailing list regarding this bug.
In the current dev version, 23.04.02-0808f7b-dev, spelling errors aren't indicated onthe braille display when the method for spelling errors is set to dot 7, dot 8, or dots 7 and 8. When using tags as the method, they are indicated in braille. To reproduce, simply go to NVDA -> Braille Extender -> Settings -> Document formatting, click the methods button, and change the method for spelling errors from tags to any of the dot options, then click OK twice. Then, misspell a word in any text entry field in Windows. The screen reader indicates the spelling error, but the braille display does not. Repeating the above instructions but selecting tags instead of a dot option, the braille display properly uses tags to indicate the spelling error.
The text was updated successfully, but these errors were encountered: