Bug 201727 - Browser's file browser won't show files, only directories
Summary: Browser's file browser won't show files, only directories
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 4
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-08 15:36 UTC by Marcos Marado
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-20 20:54:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marcos Marado 2006-08-08 15:36:33 UTC
Description of problem:
Seamonkey's file browser stopped working (as file browser I mean when you click
in a "Browse..." button): while browsing a directory with files inside, the
files won't show. I think it might have something to do with the extension
filter, since no options are showing there.

If you want a screenshot I can arrange it, I just have to upload it using
another browser :-P

Version-Release number of selected component (if applicable):
seamonkey-1.0.4-0.4.2.fc4


How reproducible: Allways


Steps to Reproduce:
1. Open browser
2. Go to a website with a form with a "browse button"
3. try to get a file to upload
  
Actual results:
No files appear to be selected

Expected results:
The window should show the files in the selected directory

Additional info:
This only happens in this seamonkey version, I did the yum update of it
yesterday and before this version I hadn't this problem.

Comment 1 Kai Engert (:kaie) (inactive account) 2006-09-20 20:54:47 UTC
What you describe works fine for me on seamonkey 1.0.5 on FC5.

Did you verify that you selected "all files" in the "file type" drop down?

I'm sorry but I'm no longer working on FC4, because it has reached the EndOfLive
phase. Could you please consider to upgrade to FC5?



Note You need to log in before you can comment on or make changes to this bug.