filepicker dialog crashes at TestGtkEmbed

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
17 years ago
6 years ago

People

(Reporter: michael_shtein, Assigned: blizzard)

Tracking

({crash})

Trunk
Sun
Solaris
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

17 years ago
The bug is reproducable only at TestGtkEmbed (it works fine at 
Mozilla itself).

To reproduce the crash please make the following:
1. Click at browser on some .pdf file
2. You will get some dialog with options Open using application/
Save this file to disk ...
3. Check "Open using an application" option.
4. Click on Choose button.
5. You will get filepicker that is not functioning,
6. Checking "Show hidden files and directories" button will
cause to crash.

Comment 1

17 years ago
*** Bug 154578 has been marked as a duplicate of this bug. ***

Updated

17 years ago
Severity: normal → critical
Keywords: crash, stackwanted

Comment 2

17 years ago
Probably due to the implementation or lack thereof of a
nsIHelperAppLauncherDialog service in the GTK widget.

-> Chris
Assignee: adamlock → blizzard
(Reporter)

Comment 3

17 years ago
Created attachment 89410 [details]
the stack.

The stack of TestGtkEmbed's crash

Comment 4

17 years ago
Note: The stack is the same as bug 149141, which I marked as fixed because (as
the reporter points out) it works in Mozilla.
Keywords: stackwanted
(Reporter)

Comment 5

17 years ago
The problem is in file xpfe/components/filepicker/res/content/filepicker.js,
since method window.setCursor() is not defined. Adding check if("setCursor" in
window) solves the problem. That seems to be due to the fact that the window
is not chrome one. What I don't understand is why at Mozilla the window is
chrome and at TestGtkEmbed it isn't.

(Reporter)

Comment 6

16 years ago
Created attachment 91481 [details] [diff] [review]
the patch of the file xpfe/components/filepicker/res/content/filepicker.js
The JS thing should not be needed; the embedding stuff should not be crashing
because of a setCursor call from JS!
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 8

16 years ago
Embedded code did not crash at the setCursor call from JS.
The problem is that since Embedding windows don't support 
setCursor method -> JS stopped its work at the setCursor 
line -> it didn't initialize needed FilePicker properties,
that it should have done later -> and this uninitializing 
caused the crash.
QA Contact: dunn5557 → apis

Comment 9

6 years ago
AFAIK, GTK embedding in that way has been discontinued, and future embedding efforts will likely go different ways, so this bug is probably not relevant any more.
That said, there's no info here on any recent software versions and code responsible for that probably has changed a lot. If this is still relevant, please reopen with current info and a crash signature.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.