Closed
Bug 353560
Opened 18 years ago
Closed 18 years ago
Unknown Content dialog not dismissed when filepicker opens
Categories
(Firefox :: General, defect, P2)
Tracking
()
RESOLVED
FIXED
Firefox 3 alpha1
People
(Reporter: bent.mozilla, Assigned: asaf)
References
Details
Attachments
(3 files, 1 obsolete file)
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060920 BonEcho/2.0
When clicking "Save" on the unknown content dialog the filepicker displays to let me choose a save location. The unknown content dialog's Save button becomes disabled but the dialog remains visible. It is possible to click the cancel button on the dialog before dismissing the file picker, although nothing seems to happen.
Reporter | ||
Comment 1•18 years ago
|
||
Reporter | ||
Updated•18 years ago
|
Flags: blocking-firefox2?
Version: unspecified → 2.0 Branch
Reporter | ||
Comment 2•18 years ago
|
||
See bug 249143 for context. This is not a regression (exists in the 1.5.0.x branch).
Reporter | ||
Comment 3•18 years ago
|
||
Also happens in the "normal" case where open and save are radio options.
Assignee | ||
Comment 4•18 years ago
|
||
Something really bad happens here, the "parent" window in promptForSaveToFile is the content window from which the download has been fired. It's expected to be the Unknown Content dialog...
Updated•18 years ago
|
Flags: blocking1.8.0.8?
Assignee | ||
Comment 5•18 years ago
|
||
So, here's what happens here:
1. saveToDisk calls promptForSaveToFile which opens a file picker attached to the content window from which the download has been fired.
2. the file picker blocks the onOK routine (which is fired on-dialog-accpet).
3. the dialog loses focus, and therefore the button is disabled.
The fix is to call saveToDisk only once the dialog is closed.
Assignee | ||
Comment 6•18 years ago
|
||
FWIW, I don't think should block either 2.0 or 1.5.0.8.
Priority: -- → P2
Target Milestone: --- → Firefox 3 alpha1
Comment 7•18 years ago
|
||
I tend to agree; minor issue, not going to block the release at this point, and not sure we want to mess with this code at this point in the cycle. Sorry, Ben.
Flags: blocking-firefox2? → blocking-firefox2-
Reporter | ||
Comment 8•18 years ago
|
||
(In reply to comment #7)
> I tend to agree; minor issue, not going to block the release at this point, and
> not sure we want to mess with this code at this point in the cycle. Sorry, Ben.
>
Hah, no tears here, I promise :)
Reporter | ||
Comment 9•18 years ago
|
||
Wow, look what else can happen. The fact that the UC dialog is not modal to the window means that you can switch back to the original link and re-open the UC dialog as many times as you want. It appears in the exact same place as the most recent UC dialog, so you have to move the window around to realize you've got more than one.
Asaf, your patch won't fix this additional complication, will it?
Comment 10•18 years ago
|
||
Not making 1.8.0.x without a landed, reviewed, tested patch.
Flags: blocking1.8.0.8? → blocking1.8.0.8-
Assignee | ||
Updated•18 years ago
|
Attachment #239449 -
Flags: review?(mconnor) → review?(gavin.sharp)
Comment 11•18 years ago
|
||
Comment on attachment 239449 [details] [diff] [review]
patch
The only thing I'm concerned about here is that this makes us call updateHelperAppPref() before saveToDisk() - are you sure that that's OK? It looks to me like it should be, since nsExternalAppHandler::SaveToDisk doesn't depend on any of the stuff updateHelperAppPref() does (and vice-versa) but I'm not that familiar with this code so I'd like to make sure.
Updated•18 years ago
|
Attachment #239449 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 12•18 years ago
|
||
(In reply to comment #9)
> Asaf, your patch won't fix this additional complication, will it?
>
Please test in the next nightly build.
mozilla/toolkit/mozapps/downloads/src/nsHelperAppDlg.js.in 1.40
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•18 years ago
|
Flags: blocking1.8.1.1?
Assignee | ||
Comment 13•18 years ago
|
||
backed out due to bug 356178.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•18 years ago
|
Attachment #239449 -
Attachment is obsolete: true
Assignee | ||
Comment 14•18 years ago
|
||
Attachment #244684 -
Flags: review?(gavin.sharp)
Assignee | ||
Updated•18 years ago
|
Status: REOPENED → ASSIGNED
Comment 15•18 years ago
|
||
Comment on attachment 244684 [details] [diff] [review]
Use the opener
r=me assuming this doesn't regress bug 356178.
Attachment #244684 -
Flags: review?(gavin.sharp) → review+
Comment 16•18 years ago
|
||
(though I'm a little wary about relying on the fact that the .opener property can point to a closed window in the target="_blank" case, given bug 241972 and bug 353851. should be fine for now, I guess)
Assignee | ||
Comment 17•18 years ago
|
||
mozilla/toolkit/mozapps/downloads/src/nsHelperAppDlg.js 1.42
Status: ASSIGNED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
Comment 18•18 years ago
|
||
Is this patch safe for the 1.8 branch? Did we get answers about the regression questions?
Assignee | ||
Comment 19•18 years ago
|
||
I don't think it's worth the risk (when I nominated this bug i thought it was a regression).
Flags: blocking1.8.1.1?
Reporter | ||
Comment 20•18 years ago
|
||
(In reply to comment #18)
> Did we get answers about the regression questions?
Sorry, I dropped the ball. Not a regression.
Comment 21•18 years ago
|
||
This bug did cause a regression. See bug 383812.
You need to log in
before you can comment on or make changes to this bug.
Description
•