From what you describe, it looks like we can't avoid fixing this bug. But I suspect that the API may look somewhat different to the one that's currently exposed by QtWebkit. I'm going to have a think about that today and try to come up with some ideas.
You're right too that Oxide doesn't make use of QNetworkAccessManager at all - it uses Chromium's networking stack
From what you describe, it looks like we can't avoid fixing this bug. But I suspect that the API may look somewhat different to the one that's currently exposed by QtWebkit. I'm going to have a think about that today and try to come up with some ideas.
You're right too that Oxide doesn't make use of QNetworkAccessM anager at all - it uses Chromium's networking stack