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

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

GitHub user daserge opened a pull request:

    https://github.com/apache/cordova-browser/pull/23

    CB-10650 Non-index content.src causes Splashscreen to be not displaye…

    …d on browser
    
    [Jira issue](https://issues.apache.org/jira/browse/CB-10650)

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

    $ git pull https://github.com/MSOpenTech/cordova-browser CB-10650

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

    https://github.com/apache/cordova-browser/pull/23.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 #23
    
----
commit b54c7e08a38c08079acbc83f293df1a560f6329c
Author: daserge <[email protected]>
Date:   2016-02-19T10:22:16Z

    CB-10650 Non-index content.src causes Splashscreen to be not displayed on 
browser

----


> Non-index content.src causes Splashscreen to be not displayed on browser
> ------------------------------------------------------------------------
>
>                 Key: CB-10650
>                 URL: https://issues.apache.org/jira/browse/CB-10650
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Browser, Plugin SplashScreen
>            Reporter: Sergey Shakhnazarov
>            Assignee: Sergey Shakhnazarov
>
> {noformat}
> [Browser][cordova.js][xhrStatusChangeHandler] Could not XHR config.xml: Not 
> Found
> Failed to load resource: http://localhost:8000/cdvtests/img/logo.png the 
> server responded with a status of 404 (Not Found)
> {noformat}



--
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