You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2013/02/19 19:01:16 UTC

[jira] [Comment Edited] (CB-2389) UIWebViewDelegate methods do not correctly take into account iframes

    [ https://issues.apache.org/jira/browse/CB-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581482#comment-13581482 ] 

Andrew Grieve edited comment on CB-2389 at 2/19/13 6:01 PM:
------------------------------------------------------------

Some research to report:

In all cases, webView.request.URL is the previous page's URL (or empty) during the didStartLoad callback.

When loading a page with a redirect:
1. shouldStartLoading (requestURL is target page)
2. didStartLoading
3. shouldStartLoading (requestURL is redirect target)
4. didFinishLoad (request.URL is redirect target)

** Note the lack of a second didStartLoading **


When loading a page with iframes:
1. shouldStartLoading (requestURL is main page)
2. didStartLoading
3. shouldStartLoading (requestURL is one of the iframes)
4. didStartLoading
5. didFinishLoad
6. didFinishLoad

** Note there is no way to distinguish which didFinishLoad maps to which didStartLoad **


Loading a page by calling window.history.go(-1):
1. didStartLoading
2. didFinishLoad

** Note the lack of a shouldStartLoading call **


Loading a page by calling location.reload()
1. shouldStartLoading
2. didStartLoading
3. didFinishLoad

                
      was (Author: agrieve):
    Some research to report:

In all cases, webView.request.URL is the previous page's URL (or empty) during the didStartLoad callback.

When loading a page with a redirect:
1. shouldStartLoading (requestURL is target page)
2. didStartLoading
3. shouldStartLoading (requestURL is redirect target)
4. didFinishLoad (request.URL is redirect target)

** Note the lack of a second didStartLoading **


When loading a page with iframes:
1. shouldStartLoading (requestURL is main page)
2. didStartLoading
3. shouldStartLoading (requestURL is one of the iframes)
4. didStartLoading
5. didFinishLoad
6. didFinishLoad

** Note there is no way to distinguish which didFinishLoad maps to which didStartLoad **


Loading a page by calling window.history.go(-1):
1. didStartLoading
2. didFinishLoad

** Note the lack of a shouldStartLoading call **


                  
> UIWebViewDelegate methods do not correctly take into account iframes
> --------------------------------------------------------------------
>
>                 Key: CB-2389
>                 URL: https://issues.apache.org/jira/browse/CB-2389
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.3.0
>            Reporter: Justin Bradford
>            Assignee: Andrew Grieve
>             Fix For: 2.5.0
>
>
> I'm seeing an intermittent issue where a FileTransfer download appears to do nothing at all. The file never downloads, the call returns without error, and neither the success or error callbacks are ever invoked. Additionally, the onprogress function on the FileTransfer instance is never called.
> I've seen this problem on iOS (simulator and device), but I have not tried other devices yet.
> I haven't been able to reduce it a clean testcase, but so far, the only pattern I've seen is that it only occurs when I request the download very shortly after creating a directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira