Closed
Bug 83662
Opened 23 years ago
Closed 23 years ago
Can't select first item in any folder in FilePicker
Categories
(Core :: XUL, defect)
Tracking
()
VERIFIED
FIXED
mozilla0.9.2
People
(Reporter: gillesd, Assigned: bryner)
References
Details
(Whiteboard: vrfy on next branch build)
Attachments
(1 file)
691 bytes,
patch
|
Details | Diff | Splinter Review |
Create New Message. Select the Attach button. Select a folder (preferrably with no subfolders) and pick the first file in the list. On my version (linux, mozilla build 20001060106), the Open button is greyed out. Furthermore, the name of the file is not updated FOR THE FIRST FILE in the list, ONLY. This is a pretty weird bug, but I've been able to reproduce it on another machine as well with a build from 4 days ago.
Comment 1•23 years ago
|
||
Does this happen only for attachments? What about using the "Open" menuitem? Could this be a filepicker bug?
Reporter | ||
Comment 2•23 years ago
|
||
Yup Boris, didn't think of that. You were right: From the browser, we cannot open the first file in a list.
Comment 3•23 years ago
|
||
update summary and ressign to right component
Assignee: ducarroz → pchen
Component: Composition → XP Apps
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: sheelar → sairuh
Summary: Can't use first item in any folder as an attachment → Can't select first item in any folder in FilePicker
Comment 4•23 years ago
|
||
Reassigning to bryner
Assignee: pchen → bryner
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 5•23 years ago
|
||
accepting for 0.9.3.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
Updated•23 years ago
|
Component: XP Apps → XP Toolkit/Widgets
QA Contact: sairuh → aegis
Comment 6•23 years ago
|
||
i see this too [2001.05.31.08 comm]. workaround: click on another file in the file picker, then click the 1st file --you can then open the 1st file [the Open button becomes enabled, too].
QA Contact: aegis → sairuh
Reporter | ||
Comment 7•23 years ago
|
||
Sairuh(se), your workaround doesn't work on our machines: if you watch closely for the name of the file, it remains whatever was the latest you clicked on, EXCEPT the first one. The only real workaround I found was to actually TYPE in the filename. Gilles
Reporter | ||
Comment 8•23 years ago
|
||
Oh, BTW, Brian, 0.9.3? Can't it be done for 0.9.2? This seems rather important (as I said previously, the only workaround is to type in the name of the file). Here at OEone, this is quite important...
Comment 9•23 years ago
|
||
gilles, thx for the clarification! i doublechecked, and you're right: even though it seems that the 1st file is selected [after clicking another one], it won't load [unless you explicitly type in its name].
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.2
Assignee | ||
Comment 10•23 years ago
|
||
Is the first file in the directory you're using a symlink? That's the only case where I'm seeing what you describe.
Comment 11•23 years ago
|
||
no, when i saw this it was with a text file.
Reporter | ||
Comment 12•23 years ago
|
||
What's a "symlink"? I see this problem with all types of file (images, text, html, etc.) Hope I answered correctly?
Comment 13•23 years ago
|
||
('symlink' == Unix symbolic link [see ln(1)].)
Assignee | ||
Comment 14•23 years ago
|
||
Comment 15•23 years ago
|
||
r=jag
Comment 16•23 years ago
|
||
sr=blizzard
Comment 17•23 years ago
|
||
a= asa@mozilla.org for checkin to the trunk. (on behalf of drivers)
Assignee | ||
Comment 18•23 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 20•23 years ago
|
||
a=blizzard on behalf of drivers for 0.9.1
Assignee | ||
Comment 21•23 years ago
|
||
checked into 0.9.1 branch.
Comment 22•23 years ago
|
||
chad, i take it you verified this using a trunk build? since bryner only recently checked it into the branch, i'm adding note to vrfy this when the next branch build comes out... /me wishes there was some way to set this back to resolved without having to reopen, ah well...
Whiteboard: vrfy on next branch build
Comment 23•23 years ago
|
||
Verified on the branch. 2001060606
You need to log in
before you can comment on or make changes to this bug.
Description
•