Closed Bug 242261 Opened 20 years ago Closed 20 years ago

Save Page As... works only if Web Page, Complete is selected

Categories

(Core Graveyard :: File Handling, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.7final

People

(Reporter: bcwright, Assigned: sgautherie)

References

()

Details

(Keywords: regression, verified1.7)

Attachments

(2 files, 2 obsolete files)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011022 Netscape6/6.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040430

In some earlier versions of Mozilla (eg, 1.4, NS 7.1) if you select search
criteria on this page and generate a report, then do a File->Save Page As...
then the page can be saved as either Web Page, Complete or Web Page, HTML only.
 In both cases the textual content of the report is saved.

In Mozilla 1.7rc1, if you generate the report and do a File->Save Page As...
then the textual content of the report is saved only if you select "Web Page,
Complete" in the File Save dialog.  If you select "Web Page, HTML only", then
the page that is saved does not have the report but instead says "Please select
at least one region or country."  However if you select "Web Page, Complete"
then the page that is saved has the complete report.

Reproducible: Always
Steps to Reproduce:
1. From the query page http://www.who.int/vaccines/casecount/case_count.cfm,
select "World" region in the left-hand listbox, "All" countries in the middle
listbox, and the year 2004 in the right-hand listbox.
2. Press "Submit Request."
3. When the report displays, select File, and then select Save Page As...
4. In the file select dialog, select "Web Page, HTML only"
5. Click OK
6. Open the saved file in Mozilla or another browser.

Actual Results:  
The saved file displays "Please select at least one region or country."  If you
save the page as "Web Page, Complete" then the entire report is displayed.

Expected Results:  
The saved file displays the generated report in either case.
Attached file LiveHTTPHeader for Save, Complete (obsolete) —
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a) Gecko/20040429

Save Page, Complete sends HEAD and GET command, 
Save Page, HTML only, sends HEAD only.

The encoding is differently specified:
the server specifies:	 Content-Type: text/html; charset=UTF-8
the saved file specifies: <meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">

so UTF-8 § is displayed as Windows-1252  §, when looking at the saved page.
Sorry, 1st attachment isn´t what I wrote.
previous attachment was a HEAD only, and another request, 
so it was from Save Page as: Web Page, HTML only.
Attachment #147451 - Attachment is obsolete: true
Mozilla 1.4.1 sends a GET when I submit the form, 
and sends a HEAD and a POST when I do  Save Page As: Web Page, HTML only.

Mozilla 1.7b sends a GET when I submit the form,
and sends a HEAD and a GET when I do  Save Page As: Web Page, HTML only.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040316
Regressed in Mozilla 1.7a, is working in Mozilla 1.6
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
regressed between working BuildID 2003123008 and not-working BuildID 2003123008 

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7a) Gecko/20031230
Hermann, are those two build ids supposed to be identical?
(In reply to comment #6)
> Hermann, are those two build ids supposed to be identical?

2003-12-23-08 was tested working, from the 2003-12-23-09 directory.
2003-12-30-08 was tested not-working.
The bonsai URL in comment 9 is wrong -- it ends at 2am instead of the 10am it
wanted.

The right URL is
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2003-12-24+07%3A00%3A00&maxdate=2003-12-25+10%3A00%3A00&cvsroot=%2Fcvsroot

This was broken by the second patch in bug 228619 -- sessionHistory.index throws
after that patch and so the postdata is always null, breaking POST result pages.
 Should have caught that when reviewing...  :(

In any case, this absolutely needs to be fixed for 1.7.  Serge?
Assignee: download-manager → file-handling
Severity: normal → major
Component: Download Manager → File Handling
Flags: blocking1.7?
OS: Windows 2000 → All
QA Contact: ian
Hardware: PC → All
also not working, but not regressed: edit.

If I want to edit the page, using Ctrl+E, the errormessage comes up.

Please select at least one region and or country!
Return to selection form

tested in 1.4.1, and 1.7a BuildID 2003122409 and 2003122509.
First two are saving the page, none of them can edit the page, so it is not a
regression.

The page is served, viewed and saved as UTF-8, but when loading the saved copy,
it is displayed as Windows-1252 according to it the metatag, so I must manually
set the character encoding to UTF-8 to get it right.
Is this TechEvangelism, as it is a server bug?
Can Mozilla know if the Server-Setting of UTF-8 or the file Metatag of
Windows-1252 is the correct one?  Wouldn´t it be nice to ask the User which
setting he prefers?
One bug per issue, please.
Assignee: file-handling → gautheri
Depends on: 228619
Target Milestone: --- → mozilla1.7final
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040421] (<-- 1.7rc1 !)
(W98SE)

(In reply to comment #10)
> This was broken by the second patch in bug 228619 -- sessionHistory.index throws
> after that patch

Obviously, as |sessionHistory| was the |var| which was removed :-(
The exception is |ReferenceError: sessionHistory is not defined|.

(Av1) Best action seems to be:
cvs update -j1.102 -j1.101
mozilla/xpfe/communicator/resources/content/contentAreaUtils.js

Neil, can you do it !? (assuming test=me, rs=bzbarsky)
Yeah, just backing out that patch looks fine to me.  I just did so on the trunk,
in fact.
Comment on attachment 147506 [details] [diff] [review]
What I just landed on trunk
[Checked in: Comment 14 & 17]

Could this please be approved for 1.7? This just backs out an erroneous
patch...
Attachment #147506 - Flags: approval1.7?
Checked in on the branch.
Status: NEW → RESOLVED
Closed: 20 years ago
Keywords: fixed1.7
Resolution: --- → FIXED
Attachment #147506 - Attachment description: What I just landed on trunk → What I just landed on trunk [Checked in: Comment 14 & 17]
Attachment #147506 - Attachment is obsolete: true
Flags: blocking1.7?
verified, save web page as HTML works as expected on 1.7
Status: RESOLVED → VERIFIED
Keywords: fixed1.7verified1.7
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: