--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
First off, a provisional load happens when a Frame (DOM Window) is asked to navigate, but theHTTP response has not yet been received. We haven't yet disturbed the existing Document inthe Frame.
Once the HTTP response headers are available, we can inspect the MIME type, and decide howto render it. If we determine that the response can be rendered by WebKit or a plugin, then weset about replacing the Document with a new one in which we will render the HTTP response.This causes the corresponding provisional load to transition to a normal load. (See RenderView::didCommitProvisionalLoad.)Now, answering your question... if the HTTP response is interrupted while the corresponding loadis still provisional, then RenderView::didFailProvisionalLoad will be called. Otherwise, if the loadhad already been committed, but failed to be downloaded fully, then RenderView::didFailLoadwill be called.
The error code net::ERR_ABORTED is intended to only be generated when a user action causesa load to be interrupted. This can happen when a new navigation interrupts an existing one, orwhen the user clicks the STOP button.
Thanks Darin, this is very helpful.On Fri, Apr 15, 2011 at 9:07 AM, Darin Fisher <da...@chromium.org> wrote:
First off, a provisional load happens when a Frame (DOM Window) is asked to navigate, but theHTTP response has not yet been received. We haven't yet disturbed the existing Document inthe Frame.Once the HTTP response headers are available, we can inspect the MIME type, and decide howto render it. If we determine that the response can be rendered by WebKit or a plugin, then weset about replacing the Document with a new one in which we will render the HTTP response.This causes the corresponding provisional load to transition to a normal load. (See RenderView::didCommitProvisionalLoad.)Now, answering your question... if the HTTP response is interrupted while the corresponding loadis still provisional, then RenderView::didFailProvisionalLoad will be called. Otherwise, if the loadhad already been committed, but failed to be downloaded fully, then RenderView::didFailLoadwill be called.The error code net::ERR_ABORTED is intended to only be generated when a user action causesa load to be interrupted. This can happen when a new navigation interrupts an existing one, orwhen the user clicks the STOP button.From your description, chrome seems to be believing that an existing navigation is interrupted by a new navigation(as this happen w/o STOP button) when InterstitialPage::Procced is called under certain condition.Can you point me the code that handles this new navigation scenario?
On Fri, Apr 15, 2011 at 11:18 AM, oshima <osh...@chromium.org> wrote:Thanks Darin, this is very helpful.On Fri, Apr 15, 2011 at 9:07 AM, Darin Fisher <da...@chromium.org> wrote:
First off, a provisional load happens when a Frame (DOM Window) is asked to navigate, but theHTTP response has not yet been received. We haven't yet disturbed the existing Document inthe Frame.Once the HTTP response headers are available, we can inspect the MIME type, and decide howto render it. If we determine that the response can be rendered by WebKit or a plugin, then weset about replacing the Document with a new one in which we will render the HTTP response.This causes the corresponding provisional load to transition to a normal load. (See RenderView::didCommitProvisionalLoad.)Now, answering your question... if the HTTP response is interrupted while the corresponding loadis still provisional, then RenderView::didFailProvisionalLoad will be called. Otherwise, if the loadhad already been committed, but failed to be downloaded fully, then RenderView::didFailLoadwill be called.The error code net::ERR_ABORTED is intended to only be generated when a user action causesa load to be interrupted. This can happen when a new navigation interrupts an existing one, orwhen the user clicks the STOP button.From your description, chrome seems to be believing that an existing navigation is interrupted by a new navigation(as this happen w/o STOP button) when InterstitialPage::Procced is called under certain condition.Can you point me the code that handles this new navigation scenario?I'm sorry, but I don't really understand what you are looking for.
, but I never had time to work on this change so far. (I made one change to handle installed apps)Chrome currently wait 500ms before "proceeding". For m12, I was looking for an easy fixthat allow me to remove this 500ms hack, but If you think we should spend time on replacing itinstead, I'm happy to punt it to m13.
One difference in chromeos is that we shows 'sign up for broadband' message in the offline pageusing extension. I assume the error page is just an html page, so this shouldn't be an issue?