>>! In D70607#2160695, @mattwoodrow wrote:
> I think this is fine for the meantime, trying to remove callers using DocumentChannel is probably harder.
>
> I had a look through the callers, it appears that handling fixups on failed loads is a common one. I think that code could live in DocumentChannel (along with error page selection) to avoid needing those fixups in the content process.
>
> We might also want an nsDocShellLoadState with lazily-created nsIURI, so we can wait until DocumentChannel has sent it to the parent before resolving it with fixups.
Bug 1375244 Comment 16 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>! In D70607#2160695, @mattwoodrow wrote:
> I think this is fine for the meantime, trying to remove callers using DocumentChannel is probably harder.
>
> I had a look through the callers, it appears that handling fixups on failed loads is a common one. I think that code could live in DocumentChannel (along with error page selection) to avoid needing those fixups in the content process.
>
> We might also want an nsDocShellLoadState with lazily-created nsIURI, so we can wait until DocumentChannel has sent it to the parent before resolving it with fixups.