Bug 7267

Summary: REGRESSION: Web Archive format not saving JavaScript/CSS files to .webarchive file
Product: WebKit Reporter: David Kilzer (:ddkilzer) <ddkilzer>
Component: WebKit Misc.Assignee: Nobody <webkit-unassigned>
Status: CLOSED WORKSFORME    
Severity: Normal Keywords: Regression
Priority: P1    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   

David Kilzer (:ddkilzer)
Reported 2006-02-14 23:41:01 PST
Summary: Saving a .webarchive file from Safari+WebKit ToT does not save JavaScript and CSS files referenced by the web page. Steps to reproduce: 1. Open Safari+WebKit. (I used a locally-built r12813 from anonsvn.opensource.apple.com.) 2. Open a web page with JavaScript and/or CSS resources. I use: http://tv.yahoo.com/grid/ (You may need to enter a zip code and a cable/satellite provider.) 3. Save the web page as a "Web Archive" named tot.webarchive. 4. Open the same page in Step 2 in a production release of Safari (v2.0.3 (417.8) on 10.4.5 tested). 5. Save the web page as a "Web Archive" again with a different name like prod.webarchive. 6. Open the prod.webarchive and tot.webarchive in the Property List Editor. 7. Open Root->WebSubresources from each file. 8. Compare them with the JS and CSS files referenced at the top of the file in Step 4. Expected results: The two web archives should have the same resources. (Exclude resources saved from banner ads!) Actual results: The tot.webarchive will be missing some JS and CSS files that the prod.webarchive file has. (Exclude resources saved from banner ads!) Notes: This bug was originally described in Bug 7266, but was broken out into its own bug since it was a regression.
Attachments
David Kilzer (:ddkilzer)
Comment 1 2006-02-18 20:10:26 PST
I can't reproduce this now using nightlies cvs-2005-10-01-03-27-01-GMT, r12142, r12751, or r12884. Closing and marking as RESOLVED/WORKSFORME.
Note You need to log in before you can comment on or make changes to this bug.