[Webkit-unassigned] [Bug 35883] Buggy caching of .js/.css resources

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Kyle Simpson <getify at gmail.com>  2010-03-09 15:26:11 PST ---
It might very well be a duplicate of 30862 in terms of the actual underlying
functionality issues, but I can say specifically that my bug has some different
symptoms than 30862 is listing. 

Mine is related to behavior of resources that load AFTER the regular page is
finished loading (on-demand resources).30862 seems to be referring to resources
that are loaded during page load. 

In my test, you can actually see that resources loaded at page load time
("script1.js" and "css1.css") behave just fine with respect to the cache. It's
only the "script2.js" and "css2.css" that behave incorrectly, and it appears
it's because they are loaded later, on-demand, after a 3 second delay.

Also, as my bug demonstrates, this incorrect (too aggressive) caching actually
causes the resources to be kept around in some sort of in-memory cache EVEN
after the actual cache is manually cleared. 30862 seems to suggest the
opposite, that clearing the cache fixes their problem.

I should also point out that this DOES in fact also affect both Firefox and
Chrome. My original supposition was that it was only webkit related, but it
appears to be more widespread than that.

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