Fix braille word wrap

[nvdaes]

• If braille word wrap is enabled, check if the first character of the next braille window is a space
• Update changelog

Link to issue number:

Fixes #18016

Summary of the issue:

When braille Word wrap is enabled, NVDA doesn't check if the first character of the next braille window is a space, causing that in some cases NVDA Splits text between braille Windows instead of using all braille cells.

Description of user facing changes:

When possible, all braille cells Will be used even if word wrap option is enabled.

Description of developer facing changes:

None.

Description of development approach:

In source/braille.py, the _calculateWindowRowBufferOffsets() function has been modified to check if the next character is a space when Word wrap is True, so that all cells can be used in such cases.

Testing strategy:

In Notepad, type:

end end end end end end end end end send

Use a Focus 40 braille display to check that all cells are used, when Word wrap is enabled and disabled.

Known issues with pull request:

None.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary

[seanbudd]

Thanks @nvdaes - do you think you could add some unit tests for _calculateWindowRowBufferOffsets?