Bug 102916

Summary: [GTK] Accessibility test expected results adapt for ATK
Product: WebKit Reporter: Mateusz Leszko <m.leszko>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Normal CC: aboxhall, adele, andresg_22, apinheiro, bugs-noreply, cfleizach, dmazzoni, ews-watchlist, g.czajkowski, jcraig, jdiggs, k.czech, mario, mcatanzaro, samuel_white
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Linux   
Attachments:
Description Flags
patch proposition ews-feeder: commit-queue-

Mateusz Leszko
Reported 2012-11-21 03:05:31 PST
Adapting accessibility tests expected result to ATK approach. Modifying expected role from MAC AXRoles to ATK roles. Some accessiblity layout test in Webkit-gtk(and Webkit-efl soon) has wrong expected result. e.g.: aria-presentational-role-expected.txt has expectation to return MAC role("AXLink") instead ATK role("link"). aria-scrollbar-role-actual.txt has expectation to return MAC role("AXScrollBar") instead ATK role("scroll bar"). canvas-fallback-content-actual.txt has expectation to return MAC role("AXButton") instead ATK role("push button"). canvas-fallback-content-actual.txt has expectation to return MAC role("AXRadioButton") instead ATK role("radio button").
Attachments
patch proposition (20.01 KB, patch)
2012-11-23 08:38 PST, Mateusz Leszko 		ews-feeder: commit-queue-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Mateusz Leszko
Comment 1 2012-11-21 06:57:12 PST
I think we should move this tests from LayoutTests/accessiblity to: LayoutTests/platform/mac and add modified copy to: -LayoutTests/platform/chromium/accessiblity (with MAC roles expected) and: -LayoutTests/platform/efl/accessiblity (with ATK roles expected) -LayoutTests/platform/gtk/accessiblity (with ATK roles expected)
Mateusz Leszko
Comment 2 2012-11-23 08:38:50 PST
Created attachment 175812 [details] patch proposition Not moving files like in first idea, but just creating new test and expectations for EFL and GTK.
Note You need to log in before you can comment on or make changes to this bug.