Status: Assigned Owner: [email protected] CC: [email protected], [email protected], tony.chromium, [email protected], [email protected] Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium
New issue 18292 by [email protected]: Consider moving alt error page support to the ResourceDispatcherHost layer http://code.google.com/p/chromium/issues/detail?id=18292 Consider moving error page support to the ResourceDispatcherHost layer There are loads of problems with the way error pages / alternate 404 pages load today. It might just make a lot more sense for them to be loaded as alternate data provided at the ResourceDispatcherHost layer (in the form of a custom ResourceHandler) before we even send any data to WebKit. Some bugs this would resolve: 1- We'd no longer have to implement subtle behavior to get the page_id advancement correct. See all the delicate code related to setting the 'replace' flag correctly in render_view.cc. 2- We'd no longer get multiple start/stop loading notifications for page transitions involving error pages. 3- We'd avoid subtle buffering of response data for alternate 404 pages. 4- Alternate error pages for post responses would work properly. Concerns: 1- This would mean that alternate error pages load with the security origin of the failed page. This may actually be a good thing. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
