Bug 12605 – Reloading a webarchive loses its CSS subresources

• Component: Page Loading
• Status: RESOLVED FIXED

[David Kilzer (:ddkilzer)]

Summary:

The first time a webarchive loads, the CSS subresources it contains are loaded.  However, subsequent reloads cause WebKit to "lose" the CSS subresources.

Steps to reproduce:

1. Open Safari/WebKit.
2. Open test case attachment.
3. Hit Cmd-R or the Reload button.

Expected results:

After Step 3, the text in the test case should still be colored correctly (as it is the first time the webarchive is loaded).

Actual results:

After Step 3, the text in the test case is no longer colored.

Regression:

This is not a regression as loading a webarchive with CSS resources on shipping Safari on Tiger doesn't display the text at all.

Notes:

Test case taken from test for bug 11839.

[David Kilzer (:ddkilzer)]

Created attachment 12924 [details]
Test case

Test case for Comment #0.

[David Kilzer (:ddkilzer)]

BTW, if you try to create this locally, please move/rename the CSS files after the webarchive has been created otherwise you will see false positive results (the colors will still be there after the reload, but only because WebKit is able to read them of disk instead).

[David Kilzer (:ddkilzer)]

Still occurs with a local debug build of WebKit r20699 with Safari 2.0.4 (419.3) on Mac OS X 10.4.9 (8P135).

[David Kilzer (:ddkilzer)]

*** Bug 14625 has been marked as a duplicate of this bug. ***

[David Kilzer (:ddkilzer)]

<rdar://problem/5336501>

[Gennady]

I agree that bug 14625 is a duplicate of this one.
But than this one should be named more generic as not only CSS sub-resources are lost, but also images and possibly javascript.

[Brady Eidson]

Landed a fix in r30632