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 671235 - FileFilter combo does not expand ellipsed file names when dropdown box selected
FileFilter combo does not expand ellipsed file names when dropdown box selected
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-03-02 23:51 UTC by Timothy Arceri
Modified: 2018-02-10 03:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple gtk3 app to show the problem (1.42 KB, text/x-c++src)
2012-03-02 23:53 UTC, Timothy Arceri 		Details

Description Timothy Arceri 2012-03-02 23:51:36 UTC 
bug 527499 fixed a problem with FileChooserDialog being expanded large than the screen. However the ellipsed file extentions should be un-ellispsed once the dropdown box is selected.

Steps to reproduce:
1. Open a FileChooserDialog in a context with a long filter. For example,
uploading images to flickr (http://flickr.com/photos/upload/).


Actual results:
The file types are ellipsed, and remain ellipsed when clicking on the dropdown box.

Expected results:
Full file types are shown when drop down selected.

Does this happen every time?
Yes
Comment 1 Timothy Arceri 2012-03-02 23:53:21 UTC 
Created attachment 208887 [details]
Simple gtk3 app to show the problem

I have attached a simple app to show the problem.

To compile: g++ simple-gtk3.cpp -o simple-gtk `pkg-config g--cflags --libs`
Comment 2 Matthias Clasen 2018-02-10 03:24:03 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.