Link to issue number:

Fixes #10864

Summary of the issue:

In NVDA 2019.2.1 it was possible to define behaviors.RowWithoutCellObjects without defining column location. In NVDA 2019.3.1, the code documentation still states that RowWithoutCellObjects._getColumnLocation method is optional, but not implementing it breaks fake table navigation.

Description of how this pull request fixes the issue:

Restore fake table navigation when RowWithoutCellObjects._getColumnLocation is not implemented (overridden)

Alternative

An alternative could have been to document _get_columnLocation as required instead of optional. However, since RowWithoutCellObjects and inherits from NVDAObject which can have location set to None, it seemed important to me that _get_columnLocation remain optional, even if I do not know any case where this method is not implemented.

Testing performed:

• Tested with Outlook Extended 1.4 that column navigation works in Outlook's address book results. No navigation object highlighter shows up during fake cell navigation since these fake cells don't have a defined location.
• Checked in task manager "Details" processus list that table navigation still works.
• In the same list, reduced a column width to 0 and checked that this column was skipped as expected
• In the same list with this 0-width column, activated nav obj highlighter and went from one fake cell to another with object navigation (not in simple mode). Checked that the 0-width fake cell still shows up the highlighter rectangle (narrow vertical) when selecting it by object navigation.

Known issues with pull request:

None

Change log entry:

Section: Changes for developers or bugfixes

Allow again behaviors._FakeTableCell to have no location defined (#10864)