search

nihad640 / smartgwt

Automatically exported from code.google.com/p/smartgwt
0 stars 0 forks source link

ComboBoxItem issue #623

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Before your post : If you are not 100% sure that you've found an issue,
please post on the SmartGWT forums first. Upon confirmation you'll be
advised to create an issue.

All issues require a minimal standalone test case with
an onModuleLoad() to be attached. You can modify an existing showcase
example if desired. Issues created without a standalone test case are
subject to being rejected after 7 days if no test case is present.

Please test any issue against the latest available code (from
smartclient.com/builds) before filing, and indicate any release versions
that you know are also affected.

What steps will reproduce the problem?
1. Click on a menu item which displays a sectionstack which contains a grid
2. When we click on add button on the section stack, a popup form appears
3. The form contains a combobox with some text fields, combobox should contain 
a default value set and should be disabled.

What is the expected output? What do you see instead?

Combobox is disabled, but the default value which is set in the code using the 
method comboBoxItem.setValue("contact-type").

What version of the product are you using? On what operating system?

GWT 2.3.0, Smartgwt 2.5
Windows 7 32-bit OS

What browser(s) does this happen in?  Are there any browsers where the
issue does not occur?

Any browser, tested in IE9, Firefox 3.6.20 and Chrome.

Please provide any additional information below.

The setValue method is working fine, which I have checked using 
sysout(comboBoxItem.getValue())

Note: The same method and the code is working fine in GWT 1.6.4, Smatgwt 2.4. 
But it is very important and urgent that our project should be migrated to 
Smartgwt 2.5.

Original issue reported on code.google.com by spandana...@gmail.com on 25 Aug 2011 at 5:40

GoogleCodeExporter commented 9 years ago 
Marking invalid, no test case, not a plausible framework bug.

Make sure you have run a GWT compile and cleared browser cache before running 
this test.  

If you still think this is a framework bug, submit a runnable, minimal 
standalone test case that clearly demonstrates a problem in the framework and 
the issue will be marked valid again.

Original comment by smartgwt...@gmail.com on 25 Aug 2011 at 4:56