Adobe Reader X: In Table, cannot use next row command when header row is identified as row 0 and data/body as row 2 #1731

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

Projects

None yet

2 participants

@nvaccessAuto

Reported by kevinchao89 on 2011-08-25 00:18
Windows 7 x64 and NVDA snapshot 4586.

PDF and tables: issue occurs in all instances, where header row is
recognized as row 0 and data/body row is seen as row 2, but works fine
when navigating to subsequent rows and if first data/body row is
identified as row 1.

Note: CTRL+ALT+DOWN to move to next row will report edge of table, but when at last column of header row, DOWN ARROW, NVDA will report row 2, UP ARROW will report row 0.

@nvaccessAuto

Comment 1 by jteh on 2011-08-25 01:05
Technical: NVDA assumes that the header row and body rows are inside different nodes, which is true for some documents. Therefore, we treat the header row as row 0. However, in some documents, the rows all have the same parent. In this case, the row count gets incremented for the header row as well, but the column headers still get row 0. I need to find a better way to handle row counting.
Changes:
Milestone changed from None to 2011.3

@nvaccessAuto

Comment 2 by jteh on 2011-08-30 02:02
cc8d0fd
Changes:
State: closed

@nvaccessAuto

Comment 4 by kevinchao89 on 2011-08-30 11:55
Thanks! Confirmed fixed in Snapshot 4600. Adobe Reader X PDF table navigation is absolutely solid, could not have asked for better, and I really appreciate it. Incredible fix in less than a week!!!

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2011.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment