Open Bug 75359 Opened 23 years ago Updated 13 years ago

Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc)

Categories

(SeaMonkey :: Sidebar, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: Peter, Unassigned)

References

Details

Mozilla/5.0 (Windows; U; WinNT4.0; en-US; 0.8.1) Gecko/20010323

Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc)

This is part of the meta bug to track all *Download Manager* requests (bug 25995)
Blocks: 75364
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Hardware: PC → All
Summary: Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc) → [RFE] Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc)
Target Milestone: --- → Future
reassigning matt's old bugs.
Assignee: matt → sgehani
With the new download manager window, this may not be so hard to implement I'd
think. Is there any chance this will happen? It is much cleaner than opening
another window in my opinion.
*** Bug 138683 has been marked as a duplicate of this bug. ***
*** Bug 148145 has been marked as a duplicate of this bug. ***
Summary: [RFE] Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc) → Show Downloads in a Sidebar tab (filename, progress, pause/cancel, etc)
*** Bug 187328 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: samir_bugzilla → nobody
QA Contact: sujay → sidebar
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: UNCONFIRMED → NEW
Ever confirmed: true
I've added chrome://mozapps/content/downloads/downloads.xul as a sidebar using the following defaults/profile/panels.rdf:
                        
----------------------- defaults/profile/panels.rdf ----------------------------
<?xml version="1.0"?> <!-- -*- Mode: SGML -*- -->

<RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:NC="http://home.netscape.com/NC-rdf#">

  <RDF:Description about="urn:sidebar:current-panel-list">
    <NC:panel-list>
      <RDF:Seq>
        <RDF:li resource="urn:sidebar:3rdparty-panel:Downloads"/>
      </RDF:Seq>
    </NC:panel-list>
    <NC:version>0.1</NC:version>
  </RDF:Description>
  <RDF:Description about="urn:sidebar:3rdparty-panel:Downloads">
    <NC:title>Downloads</NC:title>
    <NC:content>chrome://mozapps/content/downloads/downloads.xul</NC:content>
  </RDF:Description>
</RDF:RDF>
--------------------------------------------------------------------------------

To use it, the panels.rdf in the profile must be deleted/moved.

I think it's what Firefox uses as a dialog, but it looks very good as a sidebar to me. Maybe making that one of the default sidebars would be enough.
You need to log in before you can comment on or make changes to this bug.