Community
Participate
Working Groups
Build Identifier: Build id: M20090211-1700 When the size of contents of the Combo is bigger than its size and Combo is selected the drop down of contents goes beyond the width of the combobox. I am attaching screenshot for reference. Reproducible: Always
Created attachment 174096 [details] combo with content wider than its size
Correct behaviour in my opnion, the Combo was made smaller than its content (combo#computeSize() was not used to allocate size for the combo). What do you think the right behaviour should be in this case ?
I was thinking there could be a way to force all contents of the combo to be within the boundaries of the combo's size. May be I have to rethink how combo is used in my case.
(In reply to comment #3) > I was thinking there could be a way to force all contents of the combo to be > within the boundaries of the combo's size. How would you present that in the UI, clip the content and nothing, or clip the content and add an horizontal scrollbar (which I don't think is possible). The right thing to do, if possible, is set the size of combo large enough to show all the content (combo.pack()).
It makes sense what you are saying. I am trying to use combo in a way that is not intended to be used. However, as you mentioned clipping the content and adding an horizontal scrollbar would probably a nice feature if at all possible.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
