Bug 470468 - firefox and some other gnome program open/save dialogs resize on any activity - VERY ANNOYING
Summary: firefox and some other gnome program open/save dialogs resize on any activity...
Status: RESOLVED DUPLICATE of bug 445923
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Firefox (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-29 02:34 UTC by Jon Nelson
Modified: 2009-01-29 04:03 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Nelson 2009-01-29 02:34:23 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5

Basically, in both firefox and eog (much worse in firefox), if you need to use a file dialog (such as for attaching stuff to emails, opening a file, etc...), the dialog is very badly sized (minimal) at the outset and *every* selection resizes the dialog back. It's extremely annoying.

A google search reveals an Ubuntu user also encountered the problem:

https://bugs.launchpad.net/ubuntu/+bug/319267/+viewstatus

and I reproduce part of their pretty good text below:




The issue occurs when you open the 'file open' dialog and resize it (for example to make it larger, because you are browsing a large directory). It resizes automatically when:

 * bookmarks (left side) are clicked
 * any files/folders are clicked (right side)
 * breadcrumbs are clicked (top)

applications which seem affected: eye of gnome, firefox
applications which don't seem affected: openoffice, gimp




Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Hubert Figuiere 2009-01-29 04:03:54 UTC
this is bug 445923.
Thanks for taking the time to report it.

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