[Webkit-unassigned] [Bug 55505] ApplicationCache - doesn't pick the "most appropriate" cache when there are multiple candidates

[bugzilla-daemon at webkit.org]

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





--- Comment #12 from Michael Nordman <michaeln at google.com>  2011-03-22 18:55:46 PST ---
My plan for this in chrome is to modify the storage.FindResponseForMainRequest method to accept an additional input about which manifest_url the caller would like a bias towards, and to provide that input based on the manifest used by the opener|parent. Ties would go to the resource from the preferred manifest_url.

I've got a start at this here...
http://codereview.chromium.org/6727006/

A further refinement could be to have a bias towards the manifest used by the document currently residing in the frame into which a new document is being loaded, but for now i'm just starting with what the opener|parent has to say.

I have not looked at webcore's impl in any detail, but breaking ties in the same way should be possible there too.

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