Comment 5 for bug 1260016

@chris yes you understand correctly. Basically we use a custom QNetworkAccessManager to access message parts internally and externally to the app [1]. Which we use the UrlSchemeDelegates to bridge the gap between the webview and our custom QNAM.

Now getting the message parts individually isn't really an issue as we can just ask the model for the data for each part and chuck it through loadHtml and be done with it. but when we come to multi-part messages where for instance, an html part might contain a cid url [2] referencing another message part. I can't see how we can load these referenced parts within the message without the aid of the webview supporting our internal schemes.

IIUC and i'm not entirely familiar with the internals of oxide/chromium, but am i right in thinking that it actually doesn't interact with QNetworkAccessManager but has it's own internal http implementation and can't go through a QNetworkAccessManager? If that's correct then even our current method of returning a wrapped qnetworkreply or Mike's idea of overriding the QNAM is actually redundant in this use-case.

I'm not sure what the best approach here is. And all ideas will be greatly appreciated :-)

[1] http://bazaar.launchpad.net/~dpniel/dekko/trunk-1/view/head:/src/Imap/Network/MsgPartNetAccessManager.cpp
[2] https://tools.ietf.org/html/rfc2392