Community
Participate
Working Groups
Build ID: 3.3 Steps To Reproduce: The Name Space-Package table in the Axix2 Web Service Skeleton Java Bean Configuration Page is not accessible. 1- You cannot step on any cell in the second colomn using keyboard only. 2-You cannot edit any cell ( first or second column) untill you click on it by the mouse. Stepping on the cell by means of a keyboard does not enable editing. More information: The same problem in the Client Web Service Configuration page. In The Axis 1 Client Wizard , in the Web Service Client Namespace to Package Mapping page, we have a similar table. The problem is resolved by adding buttons under the table for using in Adding / Editing data inside the table. This solution is acceptable in terms of Accessibility.
I tested this and what I saw was if you are doing it from keyboard only with the tab index then we can not actually get the focus on the table entries to edit it becaue the action event involved in getting the focus inside the raw of a table is actually mouse down (click on any raw). And then as I see it from the tab index its actually set focus to the namespace to package table there after and it can be traverse through the keyboard. So I am actually bit gray on what is the actual requirement on this, is this needed in kind of a UI automation testing. I ll try to fix it as its already fixed in the Axis1 case.
Okey I looked at the how the Axis1 have solved the problem, but I am not impressed with it, mainly because of the fact that is not pre-populated. What I am thinking of is to have some kind of tab index working and get the focus on to the namespace package table and then with again after that with the tab (esc to get out focus), then again go through the main controls in the page with tab navigation. Is this can not be achieved with the SWT controls? I will try look in to this more. thanks Lahiru
Since this involves UI changes, it needs to be done for WTP 3.0 M6.
Hi, I agree that buttons are probably not necessary in axis2 case since the table is already populated with all the namespaces in the WSDL file. There is one thing I want to clarify on however, which is, what's the purpose of allowing the user to edit the namespace column? If the namespaces shown are already those found inside the WSDL, would users ever need to modify them? If the namespace does not need to be editable, it would simplify the fix for this bug since we don't have to handle navigating between columns.
Created attachment 92965 [details] patch Here is a proposed fix for this bug, which assumes that we restrict the namespace column to be read-only.
Patch committed and released to HEAD as v200803261855.
mass change to add 'contributed' keyword based on bugzilla query, please correct if that's not accurate (by marking patches as obsolete and removing the 'contributed' keyword.
Fix verified. Thanks.
