Since chromium loads workers in a separate process from the frame, it needs a loader which doesn't rely on frames in order to do the loading. (This won't allow loaders to be used on other threads and is only needed for the chromium port.)
Created attachment 30718 [details] Proposed fix. Although these is no chromium specific code, it is a chromium specific directory for two reasons: 1. I expect that only chromium will use it. 2. It is so similar to ResourceLoader/SubresourceLoader that to land it in the main directory those classes should be refactored but I haven't been able to figure out how to do that without adding many more virtual function calls and more complexity to those classes (which is badness).
Hmm... duplication of complicated code vs. making complicated code more complex ;-) How bad would the refactoring be? It seems like that is the better long term solution.
Comment on attachment 30718 [details] Proposed fix. Withdrawing for now... Will consider a dummy frame instead.