Ticket #1731 (closed defect: fixed)

Opened 6 months ago

Last modified 6 months ago

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

Reported by: kevinchao89 Owned by: jteh
Priority: minor Milestone: 2011.3
Component: Browse mode Version: development
Keywords: AdobeWorkApr2011 Cc:
Operating system: Blocked by:
Blocking:

Description

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.

Change History

comment:1 Changed 6 months ago by jteh

  • Owner set to jteh
  • Status changed from new to assigned
  • Operating system Windows 7 deleted
  • Milestone set to 2011.3

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.

comment:2 Changed 6 months ago by jteh

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

comment:3 Changed 6 months ago by jteh

  • Keywords AdobeWorkApr2011 added

comment:4 Changed 6 months ago by kevinchao89

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!!!

Note: See TracTickets for help on using tickets.