Nightly build #55 for cordova has succeeded!
The latest nightly has been published and you can try it out with 'npm i -g
cordova@nightly'
For details check build console at
https://builds.apache.org/job/cordova-nightly/55/consoleFull
-
Jenkins for Apache Cordova
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-cli/pull/257
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-lib/pull/458
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user dpeacock commented on the issue:
https://github.com/apache/cordova-plugin-media/pull/95
The test that failed is an iOS test... this commit is only for
'src/blackberry10/index.js' not sure how the two could be related... thoughts?
---
If your project is set up for it, you
Github user emirdeliz commented on the issue:
https://github.com/apache/cordova-plugin-media/pull/94
Some resolution for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user emirdeliz commented on the issue:
https://github.com/apache/cordova-plugin-media/pull/95
Some resolution for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user HenryPing closed the pull request at:
https://github.com/apache/cordova-android/pull/313
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user HenryPing opened a pull request:
https://github.com/apache/cordova-android/pull/313
Support project template with aar for building app with custom plugins
You can merge this pull request into a Git repository by running:
$ git pull
Github user shazron commented on the issue:
https://github.com/apache/cordova-plugin-wkwebview-engine/pull/7
I'm creating failing unit tests for this first, I think we have passed the
point where we can argue about the implementation, but we need objective
verification:
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/178
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user shazron commented on the issue:
https://github.com/apache/cordova-plugin-wkwebview-engine/pull/8
I'm creating failing unit tests for this first, I think we have passed the
point where we can argue about the implementation, but we need objective
verification:
Github user infil00p commented on the issue:
https://github.com/apache/cordova-android/pull/178
BTW: I'm going to close this and recommend that the approach dpogue is
mentioning be taken. We can't guarantee behaviour across multiple webviews.
---
If your project is set up for it,
Github user shazron commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/116
Thanks for this PR. There's 3 issues with this PR:
1. It doesn't merge cleanly anymore - the commits should be rebased
2. An issue should be created for this in
Github user mani95lisa commented on the issue:
https://github.com/apache/cordova-plugin-inappbrowser/pull/116
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
I see. Cordova already uses a `permissionResultCallbacks` that holds the
user provided `requestCode`. It could additionally hold the
`callbackContext`.
And when android calls `CordovaInterfaceImpl.onRequestPermissionResult` it
could call a new plugin function with a new signature that contains the
onRequestPermissionResult is an Android method we have to override, so we
can't choose which params to pass.
https://developer.android.com/reference/android/support/v4/app/ActivityCompat.OnRequestPermissionsResultCallback.html
2016-06-28 10:29 GMT+02:00 Philipp Kursawe :
I wonder about this API design decision.
The current API forces us to save the callback context in some state
variable to have access to it
in the plugins `onRequestPermissionResult` like this:
private void requestPermissionAction(CallbackContext callbackContext,
JSONArray permission) {
17 matches
Mail list logo