After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 127602 - entry completion window should have a minimum size for odd ball cases
entry completion window should have a minimum size for odd ball cases
Status: RESOLVED DUPLICATE of bug 131916
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2003-11-21 11:39 UTC by Dave Bordoley [Not Reading Bug Mail]
Modified: 2011-02-04 16:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Dave Bordoley [Not Reading Bug Mail] 2003-11-21 11:39:22 UTC 
Ok, so in general the completion window size is pretty sane, but there are
some issues. For instance open applet (my pet project) is normally 1/8 of
the width of the monitor. So if i have an action item like "Search the web
for this url", a substantial amount of text gets cut off the screen. 

So the potential solutions i see are api, that allows me to set  the width
of the completion window (not really optimal imo really), or to be sane and
set a more reasonable minimum width for these situations.

note: 1/8th of the screen is still a rather large entry on a 1024x768
screen so i imagine other apps could have similar issues.
Comment 1 Dave Bordoley [Not Reading Bug Mail] 2003-11-21 12:01:46 UTC 
I'm wondering if this might be an a11y issue as well, mainly because
when using large fonts, the action items aren't correctly shown at
all. They are cut off both horizontally and vertically. I tested this
with epiphany.
Comment 2 Matthias Clasen 2004-02-27 11:14:07 UTC 
decided to lump entry completion bugs together with combobox bugs.
Comment 3 Matthias Clasen 2004-03-09 08:46:47 UTC 
The duplicate proposes a more general resizing policy property which 
would cover this


*** This bug has been marked as a duplicate of 131916 ***