You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "jcesarmobile (JIRA)" <ji...@apache.org> on 2016/11/24 18:16:58 UTC

[jira] [Commented] (CB-9208) InAppBrowser.executeScript interacts strangely with location.hash

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

jcesarmobile commented on CB-9208:
----------------------------------

It's not documented, but you should use executeScript on loadstop event instead of doing it on loadstart.

Depending on the code you wan't to execute, it might not work on loadstart

> InAppBrowser.executeScript interacts strangely with location.hash
> -----------------------------------------------------------------
>
>                 Key: CB-9208
>                 URL: https://issues.apache.org/jira/browse/CB-9208
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin InAppBrowser
>    Affects Versions: 5.0.0
>         Environment: iOS
>            Reporter: Grant Patterson
>            Priority: Minor
>              Labels: Triaged
>
> In my "loadstart" event handler I call executeScript() with a callback. Here is what I see:
> actual page change: script runs, callback runs
> window.location.assign(same page, new hash): nothing runs
> click anchor link e.g. href=#newsection: nothing runs
> set location.hash = newhash: script runs; callback does not
> The last case is the strangest to me. The script runs just fine in this case but the callback with the result never happens.
> I'm not sure under what conditions a URL fragment change should trigger the "loadstart" event; I would say it should be always, and that does not appear to be the case. That is probably a bug.
> Worse, though, is running the script but not triggering its callback. This could leave some task half-done: the in-app-browser window has had a state change, but the code outside the in-app-browser never hears back about it. That is almost certainly a bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org