Skip to content

Incorrect assumptions in Gecko VBuf break table navigation in some tables in Chromium #12359

@LeonarddeR

Description

@LeonarddeR

Related to #8462, #9760

Steps to reproduce:

  1. Download BrokenTableTest.html.txt
  2. Remove the extension and open the file in Chrome/Edge Chromium
  3. Try table navigation.

Actual behavior:

Table navigation doesn't work. NVDA does not announce table row/column count for the table. If reporting of layout tables is enabled, table navigation results in an error.

Expected behavior:

Row/Column count is announced for the table and navigation works as expected.

Note that this is what happens when using UIA for Edge is enabled.

Possible cause

There's some logic in gecko_ia2.cpp around Line 794 that makes me think there's an incorrect assumption made about the table information for the actual table can be ignored.

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

NVDA alpha-22571

Windows version:

Windows 10 21h1

Name and version of other software in use when reproducing the issue:

Chrome/Edge 91Edge 91

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions