Re-use nsIWebBrowserPersist from within nsExternalHelperAppService

RESOLVED WONTFIX

Status

()

P3
normal
RESOLVED WONTFIX
18 years ago
3 years ago

People

(Reporter: mscott, Unassigned)

Tracking

Trunk
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
This is a reminder bug. Bill and I were talking about this after our meeting on
Thursday. We should move the code I have to stream data to a temp file while we
determine if we want to open or save the file to disk (including prompting for
the file name) into the xfer component that Bill has. Basically this code
implements a stream listener interface so data can be streamed directly to it
while we bring up the UI.

In order to consolidate things like error checking, it makes sense to move this
out where it can leverage error checking and other things that Bill already has
working in the xfer component.

Comment 1

18 years ago
mass move, v2.
qa to me.
QA Contact: tever → benc

Comment 2

17 years ago
"xfer" is kaput.  Nowadays, the code we'd like to reuse is the
nsIWebBrowserPersist interface implemented in nsWebBrowserPersist over in embedding.

I looked into doing that in the course of fixing bug 27609 but it wasn't
feasible at the time, mostly due to resource constraints.  It might be
theoretically possible, with some tweaking of nsWebBrowserPersist so it wasn't
so persnickity about owning the output file stream.
Summary: Move helper app code for streaming to a temp file into xpfe/xfer → Re-use nsIWebBrowserPersist from within nsExternalHelperAppService
Assignee: mscott → nobody
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.