Bug 98360 - [GTK] accessibility/aria-used-on-image-maps.html is failing
Summary: [GTK] accessibility/aria-used-on-image-maps.html is failing
Status: RESOLVED DUPLICATE of bug 121558
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk, LayoutTestFailure
Depends on:
Blocks: 98347
  Show dependency tree / graph
 
Reported: 2012-10-04 00:36 PDT by Zan Dobersek
Modified: 2013-09-25 06:24 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zan Dobersek 2012-10-04 00:36:19 PDT 
accessibility/aria-used-on-image-maps.html is failing on all GTK platforms.
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=accessibility%2Faria-used-on-image-maps.html
Comment 1 Joanmarie Diggs 2012-10-17 06:00:21 PDT 
Looking at Accerciser, I see the push buttons as expected. But when running the test, I get role unknown. This seems to occur when the test asks for a child at a given index and that child does not exist due to platform-specific expectations in the accessible hierarchy. Once that is addressed in the test, the accessible role will still be reported differently.
Comment 2 Mario Sanchez Prada 2013-09-25 06:24:20 PDT 
I just found that this problem is related to the fact that we are making use sometimes of the WebCore's accessibility layer when the render tree is not stable (e.g. in need of updating the layout), since this tests is now passing for me with the patch I have locally applied to fix the issue found with bug 121558.

Thus, I'm marking this one as duplicate of bug 121588 and will unskip this test along with the patch I'm preparing for that one (which will most likely be renamed, since it's not longer just about "crashing after hiding a heading").

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