[Webkit-unassigned] [Bug 118577] [GTK] platform/gtk/accessibility/replaced-objects-in-anonymous-blocks.html is failing

Tue Oct 22 06:22:43 PDT 2013

https://bugs.webkit.org/show_bug.cgi?id=118577

Mario Sanchez Prada <mario at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #3 from Mario Sanchez Prada <mario at webkit.org>  2013-10-22 06:21:28 PST ---
(In reply to comment #2)
> It seems that the problem is that in the following code from the test...
> 
>    <body> 
>    <p>Paragraph</p>
>    <button>button</button>
>    <p></p>
>    [...]
> 
> The button is placed inside of a render object without an associated DOM node (wrapped by an AccessibilityObject of role GroupRole), which avoids AccessibilityRenderObject::textUnderElement() from using the TextIterator to extract the text under that GroupRole object.
> 
> In that scenario, as a consequence of this->node() returning NULL, AccessibilityRenderObject::textUnderElement() ends up calling AccessibilityNodeObject::textUnderElement(), which iterates over every children and finally return the text corresponding to the button but not the object replacement character since it's already asking for the text under that button, not from the point of view of its parent container.
> 
> In the same way, if we changed the test to this...
> 
>    <body> 
>    <p>Paragraph</p>
>    lorem ipsum <button>button</button> foo bar baz
>    <p></p>
>    [...]
> 
> ... we would still obtain "lorem ipsum button foo bar baz" (no OR character) when exposing the anonymous block containing that test, which is bad for ATK based ATs (Joanie, correct me if I'm wrong).
> 
> I'll try to investigate this issue and see if I can find a reasonable solution for this that does not disturb other ports (emitting object replacement characters in these cases is only used in GTK, AFAIK).
> 
> Any hint or tip is welcome anyway of course.

I found that the root issue behind this was actually not that simple and that it all boils down to a wrong way of doing things in the AtkText implementation.

I'm working on fixing the whole problem in bug 123153, so I'm resolving this one as a duplicate of that one.

*** This bug has been marked as a duplicate of bug 123153 ***

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.