Closed GoogleCodeExporter closed 8 years ago
This code does not reproduce a problem. Most likely your actualy code involves
invalid mixing of GWT and SmartGWT widgets.
If you disagree, add a test case that actually reproduces the problem against
the latest patch build from smartclient.com/builds.
Marking Invalid until reproducible.
Original comment by smartgwt...@gmail.com
on 27 Apr 2012 at 4:46
You are right. I created a new empty GWT Project and there is no error.
I checked what is causing the Problem and found that part of it is this line:
SC.setScreenReaderMode(true);
So if you add this the checkbox in the header disappears. This already appears
as a bug to me.
However, this is still not causing the same problem I described. In my project
we are also using gwt-platform so I suppose there is some problem as you
suggested by "mixing GWT and SmartGWT".
However, this is why I used "list.show()" instead of adding it properly to the
view.
I removed the SC.setScreenReaderMode(true); line from my app and now it works.
However we have to check the impact on accessibility as we need to support
screen readers.
Thanks a lot so far.
Original comment by joerg.ho...@googlemail.com
on 27 Apr 2012 at 7:46
public class Smartgwt_test implements EntryPoint {
/**
* This is the entry point method.
*/
public void onModuleLoad() {
SC.setScreenReaderMode(true);
ListGrid list = new ListGrid();
ListGridField field = new ListGridField("Operation");
list.setFields(field);
list.setSelectionAppearance(SelectionAppearance.CHECKBOX);
list.setSelectionType(SelectionStyle.SIMPLE);
list.show();
}
}
Original comment by joerg.ho...@googlemail.com
on 27 Apr 2012 at 7:47
Just to clarify, this code still does not reproduce the problem *until you add
gwt-platform*, right?
Original comment by smartgwt...@gmail.com
on 28 Apr 2012 at 6:54
A follow up: We were able to reproduce this issue and have made a change to
resolve it. Should no longer be occurring in nightly builds cut from the 3.0p
or 3.1d branch (as of May 17 or greater).
Changing status from invalid to fix.
Original comment by smartgwt...@gmail.com
on 17 May 2012 at 12:53
Feedback:
We have upgraded to SmartGWT 3.1 and can confirm that this issue is resolved
even with our entire technology stack (GWTP, OpenLayers, etc.).
Accessibility and keyboard control of Menü, etc. is now a lot better.
Thanks for your great support!
Original comment by joerg.ho...@googlemail.com
on 29 Nov 2012 at 12:03
Original issue reported on code.google.com by
joerg.ho...@googlemail.com
on 26 Apr 2012 at 4:44Attachments: