Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MS Word: press home, braille cursor could not move to the first cell #3168

Closed
nvaccessAuto opened this issue Apr 18, 2013 · 6 comments
Closed

Comments

@nvaccessAuto
Copy link

Reported by surfer0627 on 2013-04-18 01:59
Braille Settings
Braille Tethered to review.

Please use the attached file to test the case.

In some cases, when user press home to move the cursor to the first cell, and the braille cursor stay at the different cell.

line no. cell no.
third 7
fourth 5
eighth 2
eleventh 20
twelveth 9
fourteenth 16
fifteenth 19
eighteenth 6

If Braille Tethered to focus, braille cursor will correctly move to the first cell.
But it will have one-second delay, after press arrow down or up.

@nvaccessAuto
Copy link
Author

nvaccessAuto commented Apr 18, 2013

Attachment test braille cursor 20130417.doc added by surfer0627 on 2013-04-18 02:01
Description:
Update:
File added from Trac
test braille cursor 20130417.doc.zip

@Adriani90
Copy link
Collaborator

@surfer0627 is this still an issue for you? Does this occur also when tetering the braille display to automatic?

@Adriani90
Copy link
Collaborator

@bdorer can you reproduce this maybe?

@bdorer
Copy link
Sponsor

bdorer commented Dec 15, 2018

hmm, I don't understand the issue. The user tethers braille to review but mooves system cursor. If review follows system cursor is on, review should follow system cursor and that's the case for me. If review follows system cursor is off review cursor doesn't follow system cursor and that's expected. @surfer0627 should provide exact steps to reproduce and what hapens and what is expected.

@bdorer
Copy link
Sponsor

bdorer commented Jan 12, 2019 via email

@Adriani90
Copy link
Collaborator

As we didn't hear from the author since 5 years and @bdorer confirmed that it works as expected, I'll close this as works for me. We can reopen it if the issue comes up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants