Summary: | WorkerScriptLoader always (and unfortunately sometimes) inherits caching policy from the parent context. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Dmitry Titov <dimich> | ||||||
Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | ap, atwilson, fishd, japhet, levin, tonyg | ||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Attachments: |
|
Description
Dmitry Titov
2010-03-19 16:55:05 PDT
See http://code.google.com/p/chromium/issues/detail?id=34092#c10. I don't think this bug is unique to workers, and the fix probably can be made to SubresourceLoader in a manner that would work for all resource loads made after the page has loaded. Created attachment 51470 [details]
HTML file that shows this bug
Created attachment 51471 [details]
Associated JS file (worker script) that shows the bug.
Added worker-latency.html and worker.js files as attachments for this bug. Download both files into a single directory, load worker-latency.html in a browser, then hit reload to reproduce the issue.
This no longer reproduces using atwilson's test case. Worker loaded scripts come from the cache even after a reload. Please reopen with explanation if I'm missing something. Likely it works now due to Nate's changes here http://trac.webkit.org/changeset/98380 and subsequent related changes later. |