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

NVDA behaves strange when hitting uparrow at the top of a multiline edit box in Firefox/Chrome while "Automatic focus mode for caret movement" is checked #1733

Closed
nvaccessAuto opened this Issue Aug 27, 2011 · 3 comments

Comments

Projects
None yet
2 participants
@nvaccessAuto
Copy link

nvaccessAuto commented Aug 27, 2011

Reported by Ahiiron on 2011-08-27 00:45
Testing with latest NVDA snap and 2011.2, firefox6, 7, 8, and 9, (32 and 64 bit), Chrome 15, IE8. This happens in all machines I've tested (xp, Vista, 7).

This is only a problem when "Automatic focus mode for caret movement" is checked in the Browse Mode dialog. With this disabled, all works as expected, NVDA will read the top line of the edit field and all is well.

After typing a few lines in a multiline edit box, then hitting up arrow several times to go to the top and eventually pop out of Focus Mode, NVDA just repeats a line two or three down from the top of the edit box, or it will say "edit multiline, blank".
Example:
Go to any multiline edit field and paste the following text

this is the first line
Here's the second line,
And now the third.

Expected: when you start arrowing up (or pressing ctrl-home and then up arrowing), NVDA should pop you out of Focus mode and let you review the page above the edit box.
Instead, NVDA will just say, "Here's the second line" or "blank"

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Nov 3, 2011

Comment 1 by jteh on 2011-11-03 09:02
Changes:
Milestone changed from None to 2012.1

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Nov 3, 2011

Comment 2 by jteh on 2011-11-03 14:49
This worked correctly in NVDA 2010.2. I broke it when introducing the new input framework in 2011.1.

Fixed in 60a1f3b.
Changes:
Milestone changed from 2012.1 to 2011.3

@nvaccessAuto

This comment has been minimized.

Copy link
Author

nvaccessAuto commented Nov 7, 2011

Comment 3 by Ahiiron on 2011-11-07 02:12
Nice! Confirmed fixed in latest 2011.3 snapshot.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.