1583653 - Reflowing inserts extra whitespace text leafs that shouldn't be there

Status: RESOLVED DUPLICATE of bug 1581589

(Core :: Disability Access APIs, defect)

Description

[Eitan Isaacson [:eeejay]]

In two cases in which we don't create accessibles for text leafs:

1. If a map element has a single whitespace text node, we don't create an accessible for the map element, and we don't create an accessible text leaf for its child.
2. If a table has whitespace text nodes between its cells we don't create text leafs for them.

If either of those are reflowed, a text node is inserted as a sibling it their container. I was concerned that this was a regression from bug 686400, but I don't believe it is after some bisection and testing.

Comment 1

[Eitan Isaacson [:eeejay]]

Attachment: 0001-Bug-1583653-Test-case.patch

Test case

Comment 2

[Eitan Isaacson [:eeejay]]

Comment on attachment 9095031 [details] [diff] [review]
0001-Bug-1583653-Test-case.patch

OK, the map case is valid. Table case was just a confusion.

Comment 3

[Eitan Isaacson [:eeejay]]

Attachment: Bug 1583653 - Return null in GetAccessibleOrContainer for text leafs of unrendered maps. r?Jamie!

Comment 4

[Eitan Isaacson [:eeejay]]

I'm going to close this bug as a dup of bug 1581589 to simplify things.