-
17 Apr 2012 9:03 AM #1
GXT 3-rc2 ComboBox: setForceSelection(false) does not work
GXT 3-rc2 ComboBox: setForceSelection(false) does not work
If you setForceSelection(false), I would expect the typed text to remain in the combo box when you unfocus. Not the case. Also clears when you hit enter.
-
17 Apr 2012 9:25 AM #2
probably related to the other bug I see with the label provider
-
17 Apr 2012 5:47 PM #3
Thanks for the report. You're right - this doesn't match the description provided. I've filed a bug against the team and will update here with any progress.
-
17 Apr 2012 6:03 PM #4
-
18 Jul 2012 1:00 PM #5
Any update on this. It was reported with a RC2, but I still see this behavior in 3.0.0b.
-
26 Jul 2012 12:20 PM #6
Hi ! Does this bug has been resolved ? I've searched for a workaround, but unfortunately I've found nothing...
-
6 Sep 2012 11:29 PM #7
-
7 Sep 2012 7:40 AM #8
Is EXTGWT-1819 not related? Couldn't find the bug report.
-
4 Oct 2012 1:04 AM #9
ComboBox, ClearValueOnParseError
ComboBox, ClearValueOnParseError
I set to combo box following:
setClearValueOnParseError(false);
I do the same thing with date component.
I start application, enter invalid string to both component, result- first component is cleared, second is not cleared.
Is there any workaround to leave invalid value in combo?
-
11 Oct 2012 2:06 AM #10
Same problem
Same problem
setClearValueOnParseError(false);
setForceSelection(false);
I set those two properties on my combobox because I need to accept arbitrary text but on blur the content text disapears.
Even with some EventHandlers like BlurHandler, onBlur or onBrowserEvent I can't get the typed value.
You found a bug! We've classified it as
EXTGWT-1932
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote