Closed
Bug 48311
Opened 25 years ago
Closed 25 years ago
Filepicker does not display proper file list
Categories
(SeaMonkey :: UI Design, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
M18
People
(Reporter: dr, Assigned: bryner)
References
Details
(Keywords: regression, Whiteboard: [nsbeta3+])
Spun off of 46658 [nsbeta3+], the XUL filepicker does not display the right
files according to the selected filter. See gabriel's comments in 46658. bryner,
you seem to be handling a lot of filepicker stuff, is this up your alley?
nominating nsbeta3, adding gabriel to cc.
Keywords: nsbeta3
Comment 3•25 years ago
|
||
nsbeta3+
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [nsbeta3+]
Target Milestone: --- → M18
| Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
And also sections of editor/base/nsEditorShell.cpp.
(I did a search for *.html; )
And also, in xpfe/components/filepicker/res/locale/en-US/filepicker.properties
all files should only be (*) for unix systems; for windows it should still be
(*.*)
Comment 7•25 years ago
|
||
over to me...
Component: XP Miscellany → XP Apps: GUI Features
QA Contact: brendan → sairuh
Updated•25 years ago
|
Keywords: regression
gabriel: my initial confusion regarding the * vs. *.* issue was that
filepicker.properties is retarded, in that it seems to localize but not xp-ize.
the reason that * simply works is because on windows and mac, the native
filepicker is used and the xp code (including filepicker.properties) is not.
also: ouch! nsFileSpecWithUIImpl.cpp looks painfully obsolete (i'm almost
certain that this is/should be taken care of in xul/xbl), and i fear it might be
still used. hyatt would know for sure whether that file could be gutted or
tossed...
| Assignee | ||
Comment 11•25 years ago
|
||
Checked in fix.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 12•25 years ago
|
||
cool, works now. vrfy'd using linux comm 2000.08.22.08.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•