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

ASF GitHub Bot commented on CB-11012:
-------------------------------------

GitHub user jcesarmobile opened a pull request:

    https://github.com/apache/cordova-plugin-inappbrowser/pull/175

    CB-11012: (docs) added some clarifications about InAppBrowser object and 
window

    ### Platforms affected
    
    Documentation
    
    ### What does this PR do?
    
    Add some clarifications of the InAppBrowser object ref and window to make 
clearer when you can use it's method
    
    ### What testing has been done on this change?
    None
    
    ### Checklist
    - [x] [ICLA](http://www.apache.org/licenses/icla.txt) has been signed and 
submitted to [email protected].
    - [x] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
    - [x] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform 
affected.
    - [ ] Added automated test coverage as appropriate for this change.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jcesarmobile/cordova-plugin-inappbrowser 
CB-11012-document-events

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-plugin-inappbrowser/pull/175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #175
    
----
commit 4d6e18e32355577507b52a5bdd7c4a48552015d3
Author: Julio César <[email protected]>
Date:   2016-07-17T11:13:57Z

    CB-11012 added some clarifications about InAppBrowser object

----


> Loadstart loadstop events do not fire for webview (target = _self)
> ------------------------------------------------------------------
>
>                 Key: CB-11012
>                 URL: https://issues.apache.org/jira/browse/CB-11012
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin InAppBrowser
>         Environment: Cordova 6.1.0
>            Reporter: Rohan
>            Priority: Minor
>              Labels: triaged
>
> Building a cordova app using Ionic.
> Loading a URL in webview using inappbrowser plugin but none of the events 
> like loadstart, loadstop  get fired.
> This is my app.js
> {code}
>  var ref = cordova.InAppBrowser.open('http://www.google.com','_self', 
> 'location=no')
>           ref.addEventListener('loadstart', function (event) {
>             console.log('loadstart fired');
>           }, false);
>           ref.addEventListener('loadstop', function (event) {
>             console.log('loadstop fired');
>           }, false);
>           ref.addEventListener('loaderror', function (event) {
>             console.log('loadstop fired');
>           }, false);
>           ref.addEventListener('exit', function (event) {
>             console.log('exit fired');
>           }, false);
> {code}
> CSP in index.html
> {code}
>  
>    <meta http-equiv="Content-Security-Policy" content="default-src 'self' 
> data: gap: https://ssl.gstatic.com; style-src 'self' 'unsafe-inline'; 
> media-src *">
> {code}
>  Console output is blank when _self is used
> *Note: The events fire when target _blank is used.*
> {code}
> I/chromium( 2222): [INFO:CONSOLE(69)] "loadstart fired", source: 
> file:///android_asset/www/src/app.js (69)
> I/chromium( 2222): [INFO:CONSOLE(73)] "loadstop fired", source: 
> file:///android_asset/www/src/app.js (73) 
> I/chromium( 2222): [INFO:CONSOLE(73)] "loadstop fired", source: 
> file:///android_asset/www/src/app.js (73)
> I/chromium( 2722): [INFO:library_loader_hooks.cc(130)] Chromium logging 
> enabled: level = 0, default verbosity = 0
> I/chromium( 2222): [INFO:CONSOLE(73)] "loadstop fired", source: 
> file:///android_asset/www/src/app.js (73)
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to