Closed
Bug 294759
Opened 20 years ago
Closed 19 years ago
Sync contentAreaUtils with the xpfe version
Categories
(Firefox :: File Handling, defect, P2)
Firefox
File Handling
Tracking
()
RESOLVED
FIXED
Firefox1.5
People
(Reporter: asaf, Assigned: asaf)
References
()
Details
Attachments
(1 file, 2 obsolete files)
45.81 KB,
patch
|
asaf
:
review+
benjamin
:
approval-aviary1.1a2+
|
Details | Diff | Splinter Review |
My target here is to fix various "Save As *" xpfe bugs which were not ported to
the toolkit version, not a zero k diff.
Assignee | ||
Updated•20 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Updated•20 years ago
|
Target Milestone: --- → Firefox1.1
Assignee | ||
Updated•20 years ago
|
Comment 1•20 years ago
|
||
I think Mike Connor had started working on this, maybe ask him about it?
Updated•19 years ago
|
Flags: blocking1.8b3+
Assignee | ||
Comment 2•19 years ago
|
||
Assignee | ||
Comment 3•19 years ago
|
||
Comment on attachment 186463 [details] [diff] [review]
work in progress
known regressuib w/ this one:
- save as text saves as html.
- the web page title isn't used in some cases (e.g.
http://www.planet.mozilla.org)
Assignee | ||
Updated•19 years ago
|
Attachment #186468 -
Flags: review?(mconnor)
Comment 5•19 years ago
|
||
Comment on attachment 186468 [details] [diff] [review]
patch
const kSaveAsType_Complete = 0; // Save document with attached objects
-const kSaveAsType_URL = 1; // Save document or URL by itself
do we need to remove this? I know its implicit, but future changes might want
this.
At least leave it in, but commented out so its obvious what's between 0 and 2.
+ // We want to use cached data because the document is currently visible.
+ var dispHeader = null;
this should be contentDisposition here too for consistency with the previous
usage.
r=me with the various single line bracket style bits fixed, I didn't bother to
nit them all.
Attachment #186468 -
Flags: review?(mconnor) → review+
Assignee | ||
Comment 6•19 years ago
|
||
Attachment #186468 -
Attachment is obsolete: true
Attachment #187420 -
Flags: review+
Attachment #187420 -
Flags: approval-aviary1.1a2?
Comment 7•19 years ago
|
||
Comment on attachment 187420 [details] [diff] [review]
patch
Please land this quickly.
Attachment #187420 -
Flags: approval-aviary1.1a2? → approval-aviary1.1a2+
Updated•19 years ago
|
Whiteboard: [cb] ready to land for 1.8b3?
Assignee | ||
Comment 8•19 years ago
|
||
Checking in toolkit/content/contentAreaUtils.js;
/cvsroot/mozilla/toolkit/content/contentAreaUtils.js,v <-- contentAreaUtils.js
new revision: 1.71; previous revision: 1.70
done
Checking in toolkit/mozapps/downloads/content/downloads.js;
/cvsroot/mozilla/toolkit/mozapps/downloads/content/downloads.js,v <-- downloads.js
new revision: 1.46; previous revision: 1.45
done
Checking in browser/base/content/browser.js;
/cvsroot/mozilla/browser/base/content/browser.js,v <-- browser.js
new revision: 1.444; previous revision: 1.443
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: [cb] ready to land for 1.8b3?
I think this changed Firefox's behavior. When doing "Save Link As", it used to kick off the download and wait for the content-disposition header to arrive before showing the dialog, so it could present the filename suggested by the server. Now it shows the dialog immediately and guesses a filename based on the URL. This could be considered a regression, although I know there's some benefit in showing the dialog immediately. Was this an intended behaviour change?
Comment 10•19 years ago
|
||
(In reply to comment #9)
> I think this changed Firefox's behavior. When doing "Save Link As", it used to
> kick off the download and wait for the content-disposition header to arrive
> before showing the dialog, so it could present the filename suggested by the
> server. Now it shows the dialog immediately and guesses a filename based on the
> URL.
That's bug 299372. This was a result of bug 160454.
You need to log in
before you can comment on or make changes to this bug.
Description
•