Navigator object updates braille while navigating between FakeTableCell objects#15825
Conversation
Co-authored-by: Leonard de Ruijter <leonardder@users.noreply.github.com>
|
Thanks @Emil-18 for this fix. Could you update the initial description with the description of the new equality test? And could you merge the latest master. For now your PR is not able to build on CI system (appVeyor) due to merge conflict. |
|
@CyrilleB79 I have changed the changes.t2t file, but it still says I have merge conflicts. Aren't I supposed to edit it directly? |
|
@Emil-18, you should merge the latest master branch in your branch. |
|
Poor man's solution could be:
|
See test results for failed build of commit b377afd3d1 |
See test results for failed build of commit b4ca2fc37a |
|
@Emil-18, there is a linting issue; for the rest, the tests are OK. Linting issues can be found following the link "details" of appVeyor status: in the "Artifacts" page, you will find the file "Flake8.txt". |
|
@CyrilleB79 Ok. Should I update changes.t2t as well? |
|
Yes, update the change log please. |
|
@Emil-18, there are merging conflicts again, due to nvaccess/master branch going forward. Could you merge again nvaccess/master into Emil-18/master and push it? Once you have done this, do not keep your PR in "Draft" state: please switch your PR to "Ready" state so that NV Access know that your PR is ready to review. Thanks. Also, a tip for your future contributions and Git usage in general: |
| - In Word, the landing cell will now be correctly reported when using the native Word commands for table navigation ``alt+home``, ``alt+end``, ``alt+pageUp`` and ``alt+pageDown``. (#15805, @CyrilleB79) | ||
| - NVDA now resumes audio if the configuration of the output device changes or another application releases exclusive control of the device. (#15758, #15775, @jcsteh) | ||
| - Contracted braille input works properly again. (#15773, @aaclause) | ||
| - Braille is now updated when moving the navigator object between table cells in more situations (#15755) |
There was a problem hiding this comment.
You may want to add your GitHub's name in the change log as a credit to recognize your work and in case people (e.g. devs) have questions on this topic.
Adding your GitHub in the change log is optional. Feel free to accept the suggestion or not:
| - Braille is now updated when moving the navigator object between table cells in more situations (#15755) | |
| - Braille is now updated when moving the navigator object between table cells in more situations (#15755, @Emil-18) |
Link to issue number:
fixes #15755
Summary of the issue:
When navigating between FakeTableCell objects, braille doesn't show the new object, but instead continues to show the previous object. This is because NVDA thinks the two objects are the same (oldObj == newObj returns True)
Description of user facing changes
The user will be able to navigate FakeTableCell objects with braille
Description of development approach
Added an _isEqual method to the FakeTableCell class, that checks if the two objects has the same row number, column number, and parent, if not, it returns False
Testing strategy:
tested with the sys list view 32 control in the SAM.exe application. Braille followed the navigator object as expected
Known issues with pull request:
None so far
Code Review Checklist: