Closed
Bug 175881
Opened 23 years ago
Closed 23 years ago
DL manager's "Launch File" and "Show in Finder" buttons are not functional with previous download entries
Categories
(SeaMonkey :: Download & File Handling, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.4final
People
(Reporter: chrispetersen, Assigned: janv)
References
Details
(Whiteboard: [adt2] [UI])
Attachments
(1 file, 1 obsolete file)
|
3.10 KB,
patch
|
neil
:
review+
jag+mozilla
:
superreview+
asa
:
approval1.4+
|
Details | Diff | Splinter Review |
Build: 2002-10-21-05 branch
Platform: OS X 10.2
Expected Results: "Launch File" and "Show in Finder" buttons should function
What I got: After selecting a previous dl item in the DL window, neither "Launch
File" and "Show in Finder" will function.
Steps to reproduce:
1) Complete a file transfer via the Download manager
2) After this is completed, select the item listed in Download manager
3) Click on "Launch File" or "Show in Finder" button to verify it functions
4) Quit and relaunch application
5) Open DL Manager via Tools menu
6) Select a previous DL item and click on either "Launch File" or "Show in
Finder" button again.
7) Button is no longer functional.
Comment 1•23 years ago
|
||
I think I have a variation on the same problem
(on Windows XP using Mozilla 1.2)
-I cleared my download manager list and closed the window
-Downloaded another file which reopened but did not focuse the
download manager
-When I focused the download manager window, the only entry was
highlighted, but the "action" buttons were not available
-When I downloaded yet another file, all the buttons were now avail
-This was repeatable by always empty and closing the download manager
window
-I also noted that the first file is out of order while the rest of the
files stay in order of download, the first file sorts to the bottom
as if it were the last file downloaded
| Reporter | ||
Comment 2•23 years ago
|
||
This problem is still occuring on the Mach-O (2003-01-23-07) trunk build under
OS X 10.2.3.
Comment 3•23 years ago
|
||
Nav triage team: nsbeta1+/adt2
| Assignee | ||
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → mozilla1.4beta
| Assignee | ||
Updated•23 years ago
|
Whiteboard: [adt2] → [adt2] [UI]
Is this fixed now that patch to bug 132331 has been checked in? BuildID
20030523xx and later have it in. Behaviour now is, if the file doesn't exist,
then those buttons are disabled rather than doing nothing.
| Assignee | ||
Comment 6•23 years ago
|
||
This is still an issue, working on a fix...
Status: NEW → ASSIGNED
| Assignee | ||
Comment 7•23 years ago
|
||
| Assignee | ||
Comment 8•23 years ago
|
||
My patch also fixes a regression introduced by fix for bug 191217.
"Launch file" should be hidden on linux.
| Assignee | ||
Updated•23 years ago
|
OS: MacOS X → All
Target Milestone: mozilla1.4beta → mozilla1.4final
| Assignee | ||
Updated•23 years ago
|
Attachment #124759 -
Flags: review?(jaggernaut)
Comment 9•23 years ago
|
||
Comment on attachment 124759 [details] [diff] [review]
patch
Hrm, I think I just sr'ed a very similar patch in bug 206441.
| Assignee | ||
Comment 10•23 years ago
|
||
I suspect, jag will want to change:
file = fileHandler.getFileFromURLSpec(aFilePath);
file = file.QueryInterface(lfIID);
to:
file = fileHandler.getFileFromURLSpec(aFilePath)
.QueryInterface(lfIID);
the same for handler/fileHandler
I'll do that if needed (no need to attach a new patch)
Comment 11•23 years ago
|
||
Comment on attachment 124759 [details] [diff] [review]
patch
Wouldn't it be better to cache the file protocol handler?
Also, how difficult would it be to fix the // XXXvarga download manager? Or at
least explain why it isn't consistent :-)
| Assignee | ||
Comment 12•23 years ago
|
||
>Wouldn't it be better to cache the file protocol handler?
yes, good idea
>Also, how difficult would it be to fix the // XXXvarga download manager? Or at
>least explain why it isn't consistent :-)
Originally, I wanted to fix the download manager (I mean the nsDownloadManager),
but I found out that it would be quite risky change and I doubt it would be
approved for 1.4.
I filed bug 208113 for a better fix.
working on a new patch
| Assignee | ||
Comment 13•23 years ago
|
||
this patch incorporates gStatusbar change
Attachment #124759 -
Attachment is obsolete: true
| Assignee | ||
Updated•23 years ago
|
Attachment #124826 -
Flags: superreview?(jaggernaut)
Attachment #124826 -
Flags: review?(ian)
Comment 14•23 years ago
|
||
Comment on attachment 124759 [details] [diff] [review]
patch
Cancelling old request
Attachment #124759 -
Flags: review?(jaggernaut)
Comment 15•23 years ago
|
||
*** Bug 206441 has been marked as a duplicate of this bug. ***
Comment 16•23 years ago
|
||
Shouldn't that now be:
+ var ioService = Components.classes[ioSvcContractID].getService(ioSvcIID);
Blocks: 172785
| Assignee | ||
Comment 17•23 years ago
|
||
yes, good catch, I'll change it before landing
Comment 18•23 years ago
|
||
Best to ask Neil for the review as I'm only 80% sure of the code.
| Assignee | ||
Comment 19•23 years ago
|
||
Comment on attachment 124826 [details] [diff] [review]
new patch
if I knew it earlier ...
Attachment #124826 -
Flags: review?(ian) → review?(neil.parkwaycc.co.uk)
Comment 20•23 years ago
|
||
Comment on attachment 124826 [details] [diff] [review]
new patch
Well I'm glad you asked Ian for review because I didn't spot the JS strict
warning.
Attachment #124826 -
Flags: review?(neil.parkwaycc.co.uk) → review+
Comment 21•23 years ago
|
||
Comment on attachment 124826 [details] [diff] [review]
new patch
+ catch(ex) {
+ file = null;
+ }
No need for that, if any of doSomething() fails in |file = doSomething()|, file
won't change.
sr=jag
Attachment #124826 -
Flags: superreview?(jaggernaut)
Attachment #124826 -
Flags: superreview+
Attachment #124826 -
Flags: approval1.4?
| Assignee | ||
Comment 22•23 years ago
|
||
fixed on the trunk
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 23•23 years ago
|
||
Comment on attachment 124826 [details] [diff] [review]
new patch
a=asa (on behalf of drivers) for checkin to the 1.4 branch.
Attachment #124826 -
Flags: approval1.4? → approval1.4+
Comment 24•23 years ago
|
||
a=adt. Please land this fix on the 1.4 Branch and add the 1.4fixed keyword.
| Reporter | ||
Comment 26•23 years ago
|
||
Verified on the Macho trunk build (2003-06-05-08)
Status: RESOLVED → VERIFIED
| Reporter | ||
Comment 27•23 years ago
|
||
Verified on the 2003-06-05-05 Win32 trunk
Comment 28•23 years ago
|
||
> No need for that, if any of doSomething() fails in |file = doSomething()|,
> file won't change.
Although strictly speaking it wouldn't have been initialized...
| Reporter | ||
Comment 29•23 years ago
|
||
Verified on Macho and Win32 branch builds
Keywords: fixed1.4 → verified1.4
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 30•21 years ago
|
||
Build: Mozilla1.7
Platform: linux suse
Expected Results: "Launch File" buttons should function
What I got: After selecting a previous dl item in the DL window, "Launch
File" function.
But, it is no longer functional.
You need to log in
before you can comment on or make changes to this bug.
Description
•