[Webkit-unassigned] [Bug 49838] Image Subresource Loads Should Not Prevent Page Cache Entry

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=49838


Joseph Pecoraro <joepeck at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joepeck at webkit.org




--- Comment #2 from Joseph Pecoraro <joepeck at webkit.org>  2010-11-19 15:31:19 PST ---
• New PageCache logging output for the manual test would look like:

> --------
>  Determining if page can be cached:
>     +---
>      Determining if frame can be cached navigating from (.../main-document-error-subresource-image-loading.html) to (.../resources/main-document-error-subresource-image-loading-next.html):
>        -Main document has an error
>         -BUT it was a cancellation and all loaders during the cancel were page cache acceptable (loading images).
>      Frame CAN be cached
>     +---
>  Page CAN be cached
> --------
> Finished creating CachedFrame for main frame url '.../main-document-error-subresource-image-loading.html' and DocumentLoader 0x107a98c00

• One concern with this patch. When returning back to page now in the page cache, the <img>
will still look like the 1st image, but the DOM element's src attribute will have the value of the
2nd image. The DOM is out of sync. It might be more appropriate to refetch the image after
returning to the page, but this behavior seems the same as an image taking a long time to timeout.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.