Closed Bug 1677122 Opened 4 years ago Closed 3 years ago

Outline and Outline row hierarchy still incorrect: Children of row appear as children of table, row is missing.

Categories

(Core :: Disability Access APIs, defect, P1)

Firefox 84
Desktop
macOS
defect

Tracking

()

RESOLVED DUPLICATE of bug 1680589
Tracking Status
firefox84 --- affected

People

(Reporter: MarcoZ, Assigned: morgan)

References

Details

(Whiteboard: [Mac2020_2])

Steps:

  1. Turn on VoiceOver.
  2. Open data:text/html,<button>Before</button><div role="tree" tabindex="0" aria-label="My drive" aria-activedescendant="myfiles"><div id="myfiles" role="treeitem" aria-label="My files" aria-selected="true" aria-expanded="false">My files</div><div role="treeitem" aria-label="Shared items" aria-selected="false" aria-expanded="false">Shared items</div></div>.
  3. Focus the table.
  4. Press Ctrl+Option+Shift+DownArrow to interact.
    • Expected: You should hear the first row, with a "collapsed" state, spoken.
    • Actual: You hear the text leaf. You do not hear any indication of the collapsed state.

The exposed hierarchy is still not correct. When interacting with a tree table with VoiceOver+Shift+Down, one should be able to navigate both rows of the test case.
You can verify that it picks up the children of the div directly by adding another item to the div, for example two inner divs with text.

Assignee: nobody → mreschenberg

:marcoz is this the same issue in bug 1680589 or is there another issue here re: hierarchy ? I wasn't able to confirm that the expanded/collapsed issue was due to parent/child structure, but if you were I'd love to know more. Thanks!

Flags: needinfo?(mzehe)

It is essentially the same issue, but this one dealt with the cut off labels IIRC. The hierarchy was what I thought I saw when interacting with the tree and its items in Firefox and Safari, and compared the two.

Flags: needinfo?(mzehe)

Ah okay, I'm gonna resolve this as a duplicate then, since I've got the other bug for tracking expanded/collapsed, and the label issue was fixed earlier :)

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE

oops wrong bug number 😬

You need to log in before you can comment on or make changes to this bug.