Closed Bug 60156 Opened 24 years ago Closed 24 years ago

filepicker does not appear [non-installer?]

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: pat, Assigned: bryner)

References

Details

(Keywords: dataloss, regression)

Attachments

(1 file)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.13 i686; en-US; m18) Gecko/20001114
BuildID:    2000111421


Reproducible: Always
Steps to Reproduce:

a. select "save links as..." from the context menu when over a link
-or-
b. select "save image as..." from the context menu when over an image
-or-
c. select "open file..." from the file menu

Actual Results:  nothing happens, nothing on the console indicates an error

Expected Results:  the filepicker appears

Dunno if this is related: instead of Document:Done (nn secs) I get
"An unknown error has occured (804b0005)" on the status line. (The actual error
number varies, though ;e.g. 804b0008). After mousing over a link, this is
replaced with the "Document: Done" message
WFM on win2k build 2000111404 trunk
I see this on linux trunk 2000111408 and 2000111421 as well.  "Save As" (for the
whole page) also does not work.

Not sure where to assign this too, but ccing blake, since last night on irc he
said that he probably broke it....
bryner or pavlov?
Assignee: asa → don
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Ever confirmed: true
QA Contact: doronr → sairuh
weird, this WFM --using 2000.11.15.08 opt comm trunk bits. have you tried
today's spins?

i get the filepicker when following your steps --then cancel it. i didn't get
the same console output as you, but after i cancelled the dialog, i got the
following [might be expected since i didn't actually save anything]:

SelectFileAndTransferLocationSpec failed, rv=[Exception... "Component returned
failure code: 0x80004004 (NS_ERROR_ABORT)
[nsIStreamTransfer.SelectFileAndTransferLocationSpec]"  nsresult: "0x80004004
(NS_ERROR_ABORT)"  location: "JS frame ::
chrome://navigator/content/nsContextMenu.js :: anonymous :: line 795"  data: no

marking WFM. pls reopen if it happens with a recent build...perhaps
'mysteriously' fixed last night. :)
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Bug is still there in linux 2000-11-15-08 trunk build from the ftp site.

sairuh, what you are seeing is what should normally happen, but it's not
happening...
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
lessee if we can narrow this down... what theme are you using? [i'm using
modern. --just tried it w/classic and it also works fine.]

does this occur with a particular page? d'you remember what you were doing
before you tried bringing up the filepicker [eg, reading mail, using editor,
etc.]

i'll grab a mozilla trunk build and see if i can repro...
This bug happens with all the themes I have (modern, classic, blue, modern
mozillium).  I tried wiping out .mozilla and package/ and reinstalling and I see
the bug with classi, modern, blue.

Happens on every single page I have tried.

Happens no matter what I am doing beforehand.  I can see it right after I start
up, I can see it after sending some mail, after browsing bugzilla and confirming
some bugs, with and without the java and flash applets.

Does _not_ happen with an optimized debug build from sources dated 11/14/2000
11:50 PST (I pulled by date for that time).

Could this be a build config problem on the automated build machines?
On builds that I have done on my local machines I see this bug as well so it's
probably not build machine related.
*** Bug 60144 has been marked as a duplicate of this bug. ***
Pavlov? ...
Assignee: don → pavlov
Status: REOPENED → NEW
mid-air collision... methinks this might be a config issue, since i *was* able
to repro this using the non-installer tarball (finally :). couldn't repro using
the .sea installer blob...
Keywords: regression
Summary: filepicker does not appear → filepicker does not appear [non-installer?]
*** Bug 60247 has been marked as a duplicate of this bug. ***
I was able to reproduce the problem using the stub installer today.
*** Bug 60253 has been marked as a duplicate of this bug. ***
*** Bug 60258 has been marked as a duplicate of this bug. ***
also, as seen in bug 60258, if a user clicks a link that brings up the helper
app-download dialog, then clicks Save to Disk, s/he won't be able to save the
file at all. eg,

1. go to http://www.mozilla.org/ and scroll to Nightly Builds section
2. click on any of the links
3. when the helper app-download dialog appears, select Save to Disk, then OK

result: nuthin' happens. no filepicker appears, no file is saved.
Keywords: dataloss, dogfood
Earliest recent version on ftp.mozilla.org that seems to exhibit this bug is
2000-11-13-21-Mtrunk/mozilla-i686-pc-linux-gnu.tar.gz.  I'm posting this with
2000-11-13-08-Mtrunk/mozilla-i686-pc-linux-gnu.tar.gz, which works.
I'm also unable to reproduce this on my tip build.  I'll try the nightly builds
referenced and see if I can get it.

cc'ing alecf, because his stringbundle checkin is the least unlikely suspect
during this time period (among a whole bunch of unlikely suspects)
I have a fix for this, I think.
Assignee: pavlov → bryner
Attached patch patchSplinter Review
Ok, it looks like the filepicker component wasn't even getting registered.  This
should fix it.
Status: NEW → ASSIGNED
Can someone on the CC list please review?
Two nits discussed in irc which bryner fixed.

r=jag
just for clarification, what my fix did was to avoid caching the stringbundle 
when you create one with a bad URL.

Are you giving it a bad .properties file?
a=ben@netscape.com

Discussed this with bryner on IRC and this prevents:
a) calling methods on a component which may not yet have been registered (string 
bundle service may have been registered after file picker)
b) assigning the result of a function into a constant before the function has 
been defined. 
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
*** Bug 60339 has been marked as a duplicate of this bug. ***
Verified.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: