Ticket #1733 (closed defect: fixed)

Opened 6 months ago

Last modified 4 months ago

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

Reported by: Ahiiron Owned by: jteh
Priority: minor Milestone: 2011.3
Component: Browse mode Version: 2011.1
Keywords: regression Cc:
Operating system: Blocked by:
Blocking:

Description

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"

Change History

comment:1 Changed 4 months ago by jteh

  • Status changed from new to assigned
  • Owner set to jteh
  • Priority changed from minor to major
  • Component changed from Core to Browse mode
  • Milestone set to 2012.1

comment:2 Changed 4 months ago by jteh

  • Priority changed from major to minor
  • Keywords regression added
  • Version changed from development to 2011.1
  • Operating system Windows 7 deleted
  • Milestone changed from 2012.1 to 2011.3

This worked correctly in NVDA 2010.2. I broke it when introducing the new input framework in 2011.1.

Fixed in changeset:releases,2011.3,4761.

comment:3 Changed 4 months ago by Ahiiron

  • Status changed from assigned to closed
  • Resolution set to fixed

Nice! Confirmed fixed in latest 2011.3 snapshot.

Note: See TracTickets for help on using tickets.