[jira] [Commented] (CB-5109) Windows 8.1 - InAppBrowser
[ https://issues.apache.org/jira/browse/CB-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140096#comment-14140096 ] ASF GitHub Bot commented on CB-5109: Github user sgrebnov closed the pull request at: https://github.com/apache/cordova-plugin-inappbrowser/pull/53 > Windows 8.1 - InAppBrowser > -- > > Key: CB-5109 > URL: https://issues.apache.org/jira/browse/CB-5109 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin InAppBrowser, Windows 8 >Reporter: Maxime LUCE >Assignee: Sergey Grebnov > > In Windows 8.1, there is a new WebView control. > It can be used to create an InAppBrowser implementation. > http://msdn.microsoft.com/en-us/library/windows/apps/dn301831.aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7599) Audio exception in iOS8
Dooms created CB-7599: - Summary: Audio exception in iOS8 Key: CB-7599 URL: https://issues.apache.org/jira/browse/CB-7599 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: Dooms Priority: Minor In iOS8, exceptions are generated when pausing one audio and playing another. Sorry I haven't been able to debug the issue further at this time. The exception: AVAudioSession.mm:646: -[AVAudioSession setActive:withOptions:error:]: Deactivating an audio session that has running I/O. All I/O should be stopped or paused prior to deactivating the audio session. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140072#comment-14140072 ] ASF GitHub Bot commented on CB-7493: Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-windows/pull/43#issuecomment-56139471 Rebased. @purplecabbage, pls. review. > Add e2e test for 'space-in-path' and 'unicode in path/name' for core > platforms. > --- > > Key: CB-7493 > URL: https://issues.apache.org/jira/browse/CB-7493 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Since we have several issues with unicode in paths and app names it will be > great to have automated testing of these cases. > Best place to keep these tests is platform repo, so these tests can be ran > via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and > iOS) > For WP8 and windows platforms we already have such tests, so we need just to > improve them to test new cases. > For Android and iOS it will be necessary to implement tests. Implementation > will be very similar to windows/wp8 implementation. > Note that android currently doesn't have support for unicode symbols in app > name (due to android tools restrictions). So test for android should contain > only 'space' case test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7453) Cordova-media-capture fails to record an mp3 file on WP8.1 device/emulator
[ https://issues.apache.org/jira/browse/CB-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140070#comment-14140070 ] ASF GitHub Bot commented on CB-7453: Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-plugin-media-capture/pull/26#issuecomment-56139405 Rebased. @purplecabbage, pls. review. > Cordova-media-capture fails to record an mp3 file on WP8.1 device/emulator > -- > > Key: CB-7453 > URL: https://issues.apache.org/jira/browse/CB-7453 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: media-capture, mp3, wp8.1 > > When trying to record audio file using media-capture plugin on WP8.1 device, > i gettting error with code 3, which is equal to {{CAPTURE_NO_MEDIA_FILES}}. > It seems that WP8.1 by some reasons can't encode audio stream to mp3 format. > Possible solution is to add a fallback to another format (m4a looks good) > when mp3 recording fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-5942) targetWidth and targetHeight are not being interpreted consistently across platforms
[ https://issues.apache.org/jira/browse/CB-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14140059#comment-14140059 ] Shazron Abdullah commented on CB-5942: -- I would suggest using the table notation here: https://issues.apache.org/jira/secure/WikiRendererHelpAction.jspa?section=tables for your table so it's easy to refer to in this bug without having to open the Excel file from your repo. Here's the plan (We should break this up into two sub-tasks, one for iOS and one for WP8): 1. We should support both properties 2. The API should never grow the image 3. The API should shrink the image while maintaining aspect ratio, such that both dimensions of the resized image fit within targetWidth and targetHeight. 4. Use the Android output as the expected output > targetWidth and targetHeight are not being interpreted consistently across > platforms > > > Key: CB-5942 > URL: https://issues.apache.org/jira/browse/CB-5942 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 3.0.0, 3.1.0, 3.2.0 > Environment: iOS, WP8 >Reporter: John M. Wargo > > A while back I posted a question regarding Camera targetWidth & targetHeight > properties and how they worked. After some discussion, the conclusion I > reached was that the documentation couldn't be correct about how it worked > since there was no way to determine the camera's resolution with the current > API but the docs said I had to provide both parameters. I said I'd do some > testing and I have finally gotten around to completing it. Here's what I > discovered: > I created an application that allowed me to pass in different values for > targetWidth & targetHeight when taking a picture. I tested at the following > image sizes: 640x480, 800x600, 1024x768 as well as setting only the > targetWidth to 1024 or only the targetHeight to 768. > Here's the results: > Android > PortraitLandscape > 480x640 640x480 > 600x800 800x600 > 768x10241024x768 > 768x10241024x768 > 768x10241024x768 > iOS > PortraitLandscape > 360x480 640x480 > 450x600 800x600 > 576x768 1024x768 > 2448x3264 3264x2448 > 2448x3264 3264x2448 > Windows Phone 8 > PortraitLandscape > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > As you can see, Android properly implements the targetWidth & targetHeight > properties. On iOS, it supports setting both properties, but not instances > where only one is specified. Windows Phone 8 ignores the parameters > completely. On iOS, when you turn the device on its side, the Camera API > applies the target width or height to the wrong axis (Android does this well > however). > I'm trying to test this on a BlackBerry device, but my development > environment is giving me fits right now. I'll work on it in the morning and > publish my results when I get them. > I would suggest that the android implementation is as expected and that the > other platforms need their implementations of targetWidth & targetHeight > adjusted so it works correctly. The documentation should be updated as well > as it's incorrect today specifying that both properties must be provided. > If the group doesn't want to support only providing one of the properties, > then I would expect that the onError callback is called when only one is > provided rather than simply ignoring them as is the case with iOS and Windows > Phone. > I posted my sample application and a spreadsheet with my results to > https://github.com/johnwargo/camera_res_test > The concensus on the dev list is the following: > The API should never grow the image > The API should shrink the image while maintaining aspect ratio, such that > both dimensions of the resized image fit within targetWidth and targetHeight. > I would propose as well that the API support only one of the parameters or > both - the API should understand enough about the image file to maintain > aspect ratio, the developer shouldn't have to tell it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-5942) targetWidth and targetHeight are not being interpreted consistently across platforms
[ https://issues.apache.org/jira/browse/CB-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5942: - Environment: iOS, WP8 > targetWidth and targetHeight are not being interpreted consistently across > platforms > > > Key: CB-5942 > URL: https://issues.apache.org/jira/browse/CB-5942 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 3.0.0, 3.1.0, 3.2.0 > Environment: iOS, WP8 >Reporter: John M. Wargo > > A while back I posted a question regarding Camera targetWidth & targetHeight > properties and how they worked. After some discussion, the conclusion I > reached was that the documentation couldn't be correct about how it worked > since there was no way to determine the camera's resolution with the current > API but the docs said I had to provide both parameters. I said I'd do some > testing and I have finally gotten around to completing it. Here's what I > discovered: > I created an application that allowed me to pass in different values for > targetWidth & targetHeight when taking a picture. I tested at the following > image sizes: 640x480, 800x600, 1024x768 as well as setting only the > targetWidth to 1024 or only the targetHeight to 768. > Here's the results: > Android > PortraitLandscape > 480x640 640x480 > 600x800 800x600 > 768x10241024x768 > 768x10241024x768 > 768x10241024x768 > iOS > PortraitLandscape > 360x480 640x480 > 450x600 800x600 > 576x768 1024x768 > 2448x3264 3264x2448 > 2448x3264 3264x2448 > Windows Phone 8 > PortraitLandscape > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > 1836x3264 3264x1836 > As you can see, Android properly implements the targetWidth & targetHeight > properties. On iOS, it supports setting both properties, but not instances > where only one is specified. Windows Phone 8 ignores the parameters > completely. On iOS, when you turn the device on its side, the Camera API > applies the target width or height to the wrong axis (Android does this well > however). > I'm trying to test this on a BlackBerry device, but my development > environment is giving me fits right now. I'll work on it in the morning and > publish my results when I get them. > I would suggest that the android implementation is as expected and that the > other platforms need their implementations of targetWidth & targetHeight > adjusted so it works correctly. The documentation should be updated as well > as it's incorrect today specifying that both properties must be provided. > If the group doesn't want to support only providing one of the properties, > then I would expect that the onError callback is called when only one is > provided rather than simply ignoring them as is the case with iOS and Windows > Phone. > I posted my sample application and a spreadsheet with my results to > https://github.com/johnwargo/camera_res_test > The concensus on the dev list is the following: > The API should never grow the image > The API should shrink the image while maintaining aspect ratio, such that > both dimensions of the resized image fit within targetWidth and targetHeight. > I would propose as well that the API support only one of the parameters or > both - the API should understand enough about the image file to maintain > aspect ratio, the developer shouldn't have to tell it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7598) Support 9-patch splashscreen images for Android
[ https://issues.apache.org/jira/browse/CB-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue updated CB-7598: - Description: If a splashscreen image for Android is specified in config.xml and ends with {{.9.png}}, it is a 9-patch image and should retain that extension when copied into the platforms/android directory. Currently the file will be renamed to {{screen.png}} when it should be {{screen.9.png}}. was: If a splashscreen image for Android is specified in config.xml and ends with `.9.png`, it is a 9-patch image and should retain that extension when copied into the platforms/android directory. Currently the file will be renamed to `screen.png` when it should be `screen.9.png`. > Support 9-patch splashscreen images for Android > --- > > Key: CB-7598 > URL: https://issues.apache.org/jira/browse/CB-7598 > Project: Apache Cordova > Issue Type: Bug > Components: Android, CLI, CordovaLib >Affects Versions: 3.5.0 >Reporter: Darryl Pogue >Priority: Minor > > If a splashscreen image for Android is specified in config.xml and ends with > {{.9.png}}, it is a 9-patch image and should retain that extension when > copied into the platforms/android directory. > Currently the file will be renamed to {{screen.png}} when it should be > {{screen.9.png}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7598) Support 9-patch splashscreen images for Android
[ https://issues.apache.org/jira/browse/CB-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1414#comment-1414 ] ASF GitHub Bot commented on CB-7598: GitHub user dpogue opened a pull request: https://github.com/apache/cordova-lib/pull/87 CB-7598 Android: Support for 9-patch splash images If a splashscreen image for Android is specified in config.xml and ends with `.9.png`, it is a 9-patch image and should retain that extension when copied into the platforms/android directory. Currently the file will be renamed to `screen.png` when it should be `screen.9.png`. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dpogue/cordova-lib nine-patch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/87.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 #87 commit 01ef7393dcbf4860a6aa27a40f68c3c4fb81dd9d Author: Darryl Pogue Date: 2014-09-19T04:49:23Z CB-7598 Android. Support for 9-patch splash images > Support 9-patch splashscreen images for Android > --- > > Key: CB-7598 > URL: https://issues.apache.org/jira/browse/CB-7598 > Project: Apache Cordova > Issue Type: Bug > Components: Android, CLI, CordovaLib >Affects Versions: 3.5.0 >Reporter: Darryl Pogue >Priority: Minor > > If a splashscreen image for Android is specified in config.xml and ends with > `.9.png`, it is a 9-patch image and should retain that extension when copied > into the platforms/android directory. > Currently the file will be renamed to `screen.png` when it should be > `screen.9.png`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7598) Support 9-patch splashscreen images for Android
Darryl Pogue created CB-7598: Summary: Support 9-patch splashscreen images for Android Key: CB-7598 URL: https://issues.apache.org/jira/browse/CB-7598 Project: Apache Cordova Issue Type: Bug Components: Android, CLI, CordovaLib Affects Versions: 3.5.0 Reporter: Darryl Pogue Priority: Minor If a splashscreen image for Android is specified in config.xml and ends with `.9.png`, it is a 9-patch image and should retain that extension when copied into the platforms/android directory. Currently the file will be renamed to `screen.png` when it should be `screen.9.png`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[ https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139966#comment-14139966 ] Ralph S Theart commented on CB-6617: any news just wanted to know ...I've been trying to use the File API to get the full resolved url but its not workingcould you let me know how you tested this..thanks. > inAppBrowser does not contain the localStorage of the parent window > --- > > Key: CB-6617 > URL: https://issues.apache.org/jira/browse/CB-6617 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Plugin InAppBrowser >Affects Versions: 3.4.0 >Reporter: Ralph S Theart >Assignee: Joe Bowser > Labels: android, localstorage > > Why is it that I can share localStorage information between wbeviews(I refer > to my app and a inappbrowser instance) in iOS but not in Android. > If I do... > {code} > //location: index.html (in my app) > localStorage.setItem('Cheese':'Brie'); > {code} > Then if I try to retrieve this data from locally served html file via > inappbroweser in android > {code} > var item = localStorage.getItem('Cheese'); > item = null > {code} > It never get set... BUT if I recompile my app and locally served html file > via inAppBroweser then it's there. > I feel like i'm missing something.. > How in the world are people passing data back and forth between the app view > and the iab view?? I need to pass deep objects back and forth ...so using url > parameters is unacceptable. Neither is using inject js...as it is not > consistent in android the data does not always make it to the iab > instance and sometimes becomes undefined...I have tested this with LoadStart, > LoadStop...it's just not consistent. > iOS just works...could you help me thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139884#comment-14139884 ] Liming Xie commented on CB-7539: I am for the proposal to embed a local web server into cordova. it will benefit a lot to HTML5 games. With the WebGL and WKWebView introduced in iOS8, and the Android L, HTML5 game performance is largely improved. The era for HTML5 on mobile phone is coming. The only bottleneck is the AJAX and domain issue. As resources are loaded via AJAX, canvas domain is also restricted for security reason. For example, the most popular phaser.js game engine, a httpd is always required. If this issue can be solved, it will largely change the HTML5 mobile game ecosystem. I've implemented a plugin to embed a tiny webserver into Cordova, CocoaHTTPServer (iOS) and NanoHTTPD (java) are used in the plugin. It's being used by Meteor. https://github.com/floatinghotpot/cordova-httpd There are quite a few app to have local httpd embeded. I guess the app review is not a blocking issue. On the other hand, the security control on remote access need be carefully designed of course. If needed, maybe I can contribute some effort to this feature. > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139812#comment-14139812 ] Carlos Santana commented on CB-7539: SGTM [~shazron] > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7597) Localizable.strings for Media Capture are in the default template, it should be in the plugin
Shazron Abdullah created CB-7597: Summary: Localizable.strings for Media Capture are in the default template, it should be in the plugin Key: CB-7597 URL: https://issues.apache.org/jira/browse/CB-7597 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Media Capture Reporter: Shazron Abdullah Create a new iOS project. See Resources -> de.lproj, Resources -> en.lproj, etc. These resources should be in the Media Capture plugin instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-5109) Windows 8.1 - InAppBrowser
[ https://issues.apache.org/jira/browse/CB-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139761#comment-14139761 ] ASF GitHub Bot commented on CB-5109: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-inappbrowser/pull/52 > Windows 8.1 - InAppBrowser > -- > > Key: CB-5109 > URL: https://issues.apache.org/jira/browse/CB-5109 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin InAppBrowser, Windows 8 >Reporter: Maxime LUCE >Assignee: Sergey Grebnov > > In Windows 8.1, there is a new WebView control. > It can be used to create an InAppBrowser implementation. > http://msdn.microsoft.com/en-us/library/windows/apps/dn301831.aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-5109) Windows 8.1 - InAppBrowser
[ https://issues.apache.org/jira/browse/CB-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139757#comment-14139757 ] ASF subversion and git services commented on CB-5109: - Commit 22b3f0ccd469b690e1f6db015cafe085e80ecea0 in cordova-plugin-inappbrowser's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;h=22b3f0c ] Merge branch 'CB-5109' of https://github.com/Touchit/cordova-plugin-inappbrowser > Windows 8.1 - InAppBrowser > -- > > Key: CB-5109 > URL: https://issues.apache.org/jira/browse/CB-5109 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin InAppBrowser, Windows 8 >Reporter: Maxime LUCE >Assignee: Sergey Grebnov > > In Windows 8.1, there is a new WebView control. > It can be used to create an InAppBrowser implementation. > http://msdn.microsoft.com/en-us/library/windows/apps/dn301831.aspx -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6911) [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139749#comment-14139749 ] Shazron Abdullah commented on CB-6911: -- Cordova 3.6.x release process was started on August 26th, and this commit occurred after that, thus it will be in 3.7.0. I'll get back to you on "Is there any word on how we can add this to cordova.js without having it re-write itself every-time you do a cordova build ios?" > [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when > accessing anything off window.navigator > > > Key: CB-6911 > URL: https://issues.apache.org/jira/browse/CB-6911 > Project: Apache Cordova > Issue Type: Sub-task > Components: CordovaJS > Environment: iOS 8 beta 5 (device) >Reporter: Jeff Schilling >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot > 2014-09-04 at 9.30.58 pm.png > > > references to window.navigator.* (platform, geolocation) etc fail with > Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7453) Cordova-media-capture fails to record an mp3 file on WP8.1 device/emulator
[ https://issues.apache.org/jira/browse/CB-7453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139737#comment-14139737 ] ASF GitHub Bot commented on CB-7453: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-plugin-media-capture/pull/26#issuecomment-56118695 Merge issues. > Cordova-media-capture fails to record an mp3 file on WP8.1 device/emulator > -- > > Key: CB-7453 > URL: https://issues.apache.org/jira/browse/CB-7453 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: media-capture, mp3, wp8.1 > > When trying to record audio file using media-capture plugin on WP8.1 device, > i gettting error with code 3, which is equal to {{CAPTURE_NO_MEDIA_FILES}}. > It seems that WP8.1 by some reasons can't encode audio stream to mp3 format. > Possible solution is to add a fallback to another format (m4a looks good) > when mp3 recording fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6911) [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139727#comment-14139727 ] Angus Bremner commented on CB-6911: --- "Is there any word on how we can add this to cordova.js without having it re-write itself every-time you do a cordova build ios?" If this is not going to be in the next update, I'd like to know this also. > [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when > accessing anything off window.navigator > > > Key: CB-6911 > URL: https://issues.apache.org/jira/browse/CB-6911 > Project: Apache Cordova > Issue Type: Sub-task > Components: CordovaJS > Environment: iOS 8 beta 5 (device) >Reporter: Jeff Schilling >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot > 2014-09-04 at 9.30.58 pm.png > > > references to window.navigator.* (platform, geolocation) etc fail with > Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7429) Media-capture plugin is not working on WP8.1 since native API change
[ https://issues.apache.org/jira/browse/CB-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139726#comment-14139726 ] ASF GitHub Bot commented on CB-7429: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media-capture/pull/25 > Media-capture plugin is not working on WP8.1 since native API change > > > Key: CB-7429 > URL: https://issues.apache.org/jira/browse/CB-7429 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > > {{captureImage()}} and {{captureVideo()}} methods won't work on WP8.1 since > API change. > these methods use Windows.Media.Capture.CameraCaptureUI() class for acquiring > camera picture, which is unavailable on WP8.1. Possible solution is to use > MediaCapture class. Also it will require to implement custom camera interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7429) Media-capture plugin is not working on WP8.1 since native API change
[ https://issues.apache.org/jira/browse/CB-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139721#comment-14139721 ] ASF subversion and git services commented on CB-7429: - Commit 3539bc20db30fc710a3f76b0c732b1fd50df0e56 in cordova-plugin-media-capture's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=3539bc2 ] CB-7429 Adds media capture support for windows * Custom UI for WP8.1 * capture* methods now resolved with proper MediaFile object * files are captured to Appdata/local folder > Media-capture plugin is not working on WP8.1 since native API change > > > Key: CB-7429 > URL: https://issues.apache.org/jira/browse/CB-7429 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > > {{captureImage()}} and {{captureVideo()}} methods won't work on WP8.1 since > API change. > these methods use Windows.Media.Capture.CameraCaptureUI() class for acquiring > camera picture, which is unavailable on WP8.1. Possible solution is to use > MediaCapture class. Also it will require to implement custom camera interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7429) Media-capture plugin is not working on WP8.1 since native API change
[ https://issues.apache.org/jira/browse/CB-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139723#comment-14139723 ] ASF subversion and git services commented on CB-7429: - Commit 8f05569dfed1bafa380b93567830f7cfc36678ed in cordova-plugin-media-capture's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=8f05569 ] CB-7429 Fixes image capture manual tests on windows > Media-capture plugin is not working on WP8.1 since native API change > > > Key: CB-7429 > URL: https://issues.apache.org/jira/browse/CB-7429 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > > {{captureImage()}} and {{captureVideo()}} methods won't work on WP8.1 since > API change. > these methods use Windows.Media.Capture.CameraCaptureUI() class for acquiring > camera picture, which is unavailable on WP8.1. Possible solution is to use > MediaCapture class. Also it will require to implement custom camera interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7429) Media-capture plugin is not working on WP8.1 since native API change
[ https://issues.apache.org/jira/browse/CB-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139722#comment-14139722 ] ASF subversion and git services commented on CB-7429: - Commit 5dce4c14b68a29632bc19875820ad55acef5a327 in cordova-plugin-media-capture's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=5dce4c1 ] CB-7429 Move windows8 and windows Proxies into one file * Adds missing capabilities to windows8 > Media-capture plugin is not working on WP8.1 since native API change > > > Key: CB-7429 > URL: https://issues.apache.org/jira/browse/CB-7429 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > > {{captureImage()}} and {{captureVideo()}} methods won't work on WP8.1 since > API change. > these methods use Windows.Media.Capture.CameraCaptureUI() class for acquiring > camera picture, which is unavailable on WP8.1. Possible solution is to use > MediaCapture class. Also it will require to implement custom camera interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7429) Media-capture plugin is not working on WP8.1 since native API change
[ https://issues.apache.org/jira/browse/CB-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139724#comment-14139724 ] ASF subversion and git services commented on CB-7429: - Commit c4c7093550922fef967353141a5e8080767b4bcd in cordova-plugin-media-capture's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=c4c7093 ] Merge branch 'CB-7429' of https://github.com/MSOpenTech/cordova-plugin-media-capture > Media-capture plugin is not working on WP8.1 since native API change > > > Key: CB-7429 > URL: https://issues.apache.org/jira/browse/CB-7429 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media Capture > Environment: WP8.1 device/emulator >Reporter: Vladimir Kotikov > > {{captureImage()}} and {{captureVideo()}} methods won't work on WP8.1 since > API change. > these methods use Windows.Media.Capture.CameraCaptureUI() class for acquiring > camera picture, which is unavailable on WP8.1. Possible solution is to use > MediaCapture class. Also it will require to implement custom camera interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7454) Add support for m4a audio format to Media plugin
[ https://issues.apache.org/jira/browse/CB-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139717#comment-14139717 ] ASF GitHub Bot commented on CB-7454: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media/pull/26 > Add support for m4a audio format to Media plugin > > > Key: CB-7454 > URL: https://issues.apache.org/jira/browse/CB-7454 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Vladimir Kotikov > Labels: m4a, media, wp8.1 > > Current version doesn't support m4a audio even if platform, we're running on > does. > For example CB-7453 describes that media-capture for WP8.1 can record an m4a > file when mp3 recording fails, and the recorded file format which is fully > supported by Windows platform and IE11, can't be used with Media plugin due > to current plugin limitations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7454) Add support for m4a audio format to Media plugin
[ https://issues.apache.org/jira/browse/CB-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139715#comment-14139715 ] ASF subversion and git services commented on CB-7454: - Commit 33acd6fd0c4130fe6ea77b9438f99f31792a7b81 in cordova-plugin-media's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=33acd6f ] CB-7454 Adds support for m4a audio format for Windows > Add support for m4a audio format to Media plugin > > > Key: CB-7454 > URL: https://issues.apache.org/jira/browse/CB-7454 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Vladimir Kotikov > Labels: m4a, media, wp8.1 > > Current version doesn't support m4a audio even if platform, we're running on > does. > For example CB-7453 describes that media-capture for WP8.1 can record an m4a > file when mp3 recording fails, and the recorded file format which is fully > supported by Windows platform and IE11, can't be used with Media plugin due > to current plugin limitations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7454) Add support for m4a audio format to Media plugin
[ https://issues.apache.org/jira/browse/CB-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139716#comment-14139716 ] ASF subversion and git services commented on CB-7454: - Commit 526a738533fe39e8a19ac06086545b58af5e773a in cordova-plugin-media's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;h=526a738 ] Merge branch 'CB-7454' of https://github.com/MSOpenTech/cordova-plugin-media > Add support for m4a audio format to Media plugin > > > Key: CB-7454 > URL: https://issues.apache.org/jira/browse/CB-7454 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Media >Reporter: Vladimir Kotikov > Labels: m4a, media, wp8.1 > > Current version doesn't support m4a audio even if platform, we're running on > does. > For example CB-7453 describes that media-capture for WP8.1 can record an m4a > file when mp3 recording fails, and the recorded file format which is fully > supported by Windows platform and IE11, can't be used with Media plugin due > to current plugin limitations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7373) Mobilespec manual contacts test provide no output for errors.
[ https://issues.apache.org/jira/browse/CB-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139711#comment-14139711 ] ASF GitHub Bot commented on CB-7373: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-contacts/pull/44 > Mobilespec manual contacts test provide no output for errors. > - > > Key: CB-7373 > URL: https://issues.apache.org/jira/browse/CB-7373 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Reporter: Vladimir Kotikov >Priority: Minor > Labels: contacts, mobilespec, windows8, windows81 > > Mobilespec's manual test for contact->save method provdies no output if any > errors happens during test. > E.g. saving contacts is not supported on windows8/8.1, and save method always > resolves with NOT_SUPPORTED_ERR, but user can't see this in test results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7357) Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR
[ https://issues.apache.org/jira/browse/CB-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139705#comment-14139705 ] ASF subversion and git services commented on CB-7357: - Commit 42cd509a6c5d8a68ea4151ca23073a710609a8b8 in cordova-plugin-contacts's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=42cd509 ] CB-7357 Adds missing 'capability' element to phone's appxmanifest. > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > > > Key: CB-7357 > URL: https://issues.apache.org/jira/browse/CB-7357 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: Windows 8.1, Windows Phone 8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: contacts, windows-phone-81, wp8.1 > > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > Repro steps: > 1. Create mobilespec app with latest contacts plugin included > 2. Run mobilespec app on wp8.1 device/emulator and navigate to New-style > tests -> Manual tests -> contact tests. > 3. Click on Get phone's contacts > Expected: > Contacts data shown in status box. or 'No contacts found' if no contacts > exists on device > Actual: > 'Error 3' message shown in status box. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7373) Mobilespec manual contacts test provide no output for errors.
[ https://issues.apache.org/jira/browse/CB-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139709#comment-14139709 ] ASF subversion and git services commented on CB-7373: - Commit 162f657e74504e6f555416807374ebe23a2e5ea9 in cordova-plugin-contacts's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=162f657 ] Merge branch 'CB-7373' of https://github.com/MSOpenTech/cordova-plugin-contacts > Mobilespec manual contacts test provide no output for errors. > - > > Key: CB-7373 > URL: https://issues.apache.org/jira/browse/CB-7373 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Reporter: Vladimir Kotikov >Priority: Minor > Labels: contacts, mobilespec, windows8, windows81 > > Mobilespec's manual test for contact->save method provdies no output if any > errors happens during test. > E.g. saving contacts is not supported on windows8/8.1, and save method always > resolves with NOT_SUPPORTED_ERR, but user can't see this in test results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7373) Mobilespec manual contacts test provide no output for errors.
[ https://issues.apache.org/jira/browse/CB-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139707#comment-14139707 ] ASF subversion and git services commented on CB-7373: - Commit 7ab651d523f5b92ee1816205058eaf29884d3eb3 in cordova-plugin-contacts's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=7ab651d ] CB-7373 Adds additional output if method is not supported. > Mobilespec manual contacts test provide no output for errors. > - > > Key: CB-7373 > URL: https://issues.apache.org/jira/browse/CB-7373 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Reporter: Vladimir Kotikov >Priority: Minor > Labels: contacts, mobilespec, windows8, windows81 > > Mobilespec's manual test for contact->save method provdies no output if any > errors happens during test. > E.g. saving contacts is not supported on windows8/8.1, and save method always > resolves with NOT_SUPPORTED_ERR, but user can't see this in test results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7357) Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR
[ https://issues.apache.org/jira/browse/CB-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139710#comment-14139710 ] ASF GitHub Bot commented on CB-7357: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-contacts/pull/43 > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > > > Key: CB-7357 > URL: https://issues.apache.org/jira/browse/CB-7357 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: Windows 8.1, Windows Phone 8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: contacts, windows-phone-81, wp8.1 > > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > Repro steps: > 1. Create mobilespec app with latest contacts plugin included > 2. Run mobilespec app on wp8.1 device/emulator and navigate to New-style > tests -> Manual tests -> contact tests. > 3. Click on Get phone's contacts > Expected: > Contacts data shown in status box. or 'No contacts found' if no contacts > exists on device > Actual: > 'Error 3' message shown in status box. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7373) Mobilespec manual contacts test provide no output for errors.
[ https://issues.apache.org/jira/browse/CB-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139708#comment-14139708 ] ASF subversion and git services commented on CB-7373: - Commit b695ec7d1f8850e66216381d6cd51d02c728d9f3 in cordova-plugin-contacts's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=b695ec7 ] CB-7373 Removes unnecessary Error object creation > Mobilespec manual contacts test provide no output for errors. > - > > Key: CB-7373 > URL: https://issues.apache.org/jira/browse/CB-7373 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Reporter: Vladimir Kotikov >Priority: Minor > Labels: contacts, mobilespec, windows8, windows81 > > Mobilespec's manual test for contact->save method provdies no output if any > errors happens during test. > E.g. saving contacts is not supported on windows8/8.1, and save method always > resolves with NOT_SUPPORTED_ERR, but user can't see this in test results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6911) [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139712#comment-14139712 ] Greg commented on CB-6911: -- Is there any word on how we can add this to cordova.js without having it re-write itself every-time you do a cordova build ios? Greg > [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when > accessing anything off window.navigator > > > Key: CB-6911 > URL: https://issues.apache.org/jira/browse/CB-6911 > Project: Apache Cordova > Issue Type: Sub-task > Components: CordovaJS > Environment: iOS 8 beta 5 (device) >Reporter: Jeff Schilling >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot > 2014-09-04 at 9.30.58 pm.png > > > references to window.navigator.* (platform, geolocation) etc fail with > Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7357) Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR
[ https://issues.apache.org/jira/browse/CB-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139706#comment-14139706 ] ASF subversion and git services commented on CB-7357: - Commit c15a15e95b12f56a3a3a367a078bd7accd0c6456 in cordova-plugin-contacts's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=c15a15e ] Merge branch 'CB-7357' of https://github.com/MSOpenTech/cordova-plugin-contacts > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > > > Key: CB-7357 > URL: https://issues.apache.org/jira/browse/CB-7357 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: Windows 8.1, Windows Phone 8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: contacts, windows-phone-81, wp8.1 > > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > Repro steps: > 1. Create mobilespec app with latest contacts plugin included > 2. Run mobilespec app on wp8.1 device/emulator and navigate to New-style > tests -> Manual tests -> contact tests. > 3. Click on Get phone's contacts > Expected: > Contacts data shown in status box. or 'No contacts found' if no contacts > exists on device > Actual: > 'Error 3' message shown in status box. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139702#comment-14139702 ] ASF GitHub Bot commented on CB-7493: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-windows/pull/43#issuecomment-56117107 Conflicted! > Add e2e test for 'space-in-path' and 'unicode in path/name' for core > platforms. > --- > > Key: CB-7493 > URL: https://issues.apache.org/jira/browse/CB-7493 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Since we have several issues with unicode in paths and app names it will be > great to have automated testing of these cases. > Best place to keep these tests is platform repo, so these tests can be ran > via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and > iOS) > For WP8 and windows platforms we already have such tests, so we need just to > improve them to test new cases. > For Android and iOS it will be necessary to implement tests. Implementation > will be very similar to windows/wp8 implementation. > Note that android currently doesn't have support for unicode symbols in app > name (due to android tools restrictions). So test for android should contain > only 'space' case test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7520) Add MRT image support for Windows platform icons
[ https://issues.apache.org/jira/browse/CB-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139697#comment-14139697 ] ASF subversion and git services commented on CB-7520: - Commit 44afcd3eb58dd06e0fb56643bfefcde8baebc662 in cordova-windows's branch refs/heads/master from sgrebnov [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=44afcd3 ] CB-7520 refine image names, use wildcard to include MRT images > Add MRT image support for Windows platform icons > > > Key: CB-7520 > URL: https://issues.apache.org/jira/browse/CB-7520 > Project: Apache Cordova > Issue Type: Improvement > Components: Windows >Reporter: Sergey Grebnov >Assignee: Sergey Grebnov > Labels: config.xml, icons, images, windows > > MS platforms support the idea of MRT images where you refer to it as follows: > image.png > ...but underneath there are actually different images per DPI... > image.scale-100.png > image.scale-140.png > ... etc ... > The following must be improved to support MRT images > 1. Scaled image versions are copied to platform images folder if defined in > config.xml > 2. Ensure all new image files from platform images folder are added to the > project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7520) Add MRT image support for Windows platform icons
[ https://issues.apache.org/jira/browse/CB-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139699#comment-14139699 ] ASF subversion and git services commented on CB-7520: - Commit 87ba72f78711e29aa53753fd61b622c574de55a2 in cordova-windows's branch refs/heads/master from sgrebnov [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=87ba72f ] CB-7520 copy MRT images defined in config.xml > Add MRT image support for Windows platform icons > > > Key: CB-7520 > URL: https://issues.apache.org/jira/browse/CB-7520 > Project: Apache Cordova > Issue Type: Improvement > Components: Windows >Reporter: Sergey Grebnov >Assignee: Sergey Grebnov > Labels: config.xml, icons, images, windows > > MS platforms support the idea of MRT images where you refer to it as follows: > image.png > ...but underneath there are actually different images per DPI... > image.scale-100.png > image.scale-140.png > ... etc ... > The following must be improved to support MRT images > 1. Scaled image versions are copied to platform images folder if defined in > config.xml > 2. Ensure all new image files from platform images folder are added to the > project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7520) Add MRT image support for Windows platform icons
[ https://issues.apache.org/jira/browse/CB-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139701#comment-14139701 ] ASF GitHub Bot commented on CB-7520: Github user asfgit closed the pull request at: https://github.com/apache/cordova-windows/pull/45 > Add MRT image support for Windows platform icons > > > Key: CB-7520 > URL: https://issues.apache.org/jira/browse/CB-7520 > Project: Apache Cordova > Issue Type: Improvement > Components: Windows >Reporter: Sergey Grebnov >Assignee: Sergey Grebnov > Labels: config.xml, icons, images, windows > > MS platforms support the idea of MRT images where you refer to it as follows: > image.png > ...but underneath there are actually different images per DPI... > image.scale-100.png > image.scale-140.png > ... etc ... > The following must be improved to support MRT images > 1. Scaled image versions are copied to platform images folder if defined in > config.xml > 2. Ensure all new image files from platform images folder are added to the > project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7520) Add MRT image support for Windows platform icons
[ https://issues.apache.org/jira/browse/CB-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139698#comment-14139698 ] ASF subversion and git services commented on CB-7520: - Commit b2848a979944f29d0b3e6a2167a4b3b1257bb261 in cordova-windows's branch refs/heads/master from sgrebnov [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=b2848a9 ] CB-7520 .appxbundle package format support > Add MRT image support for Windows platform icons > > > Key: CB-7520 > URL: https://issues.apache.org/jira/browse/CB-7520 > Project: Apache Cordova > Issue Type: Improvement > Components: Windows >Reporter: Sergey Grebnov >Assignee: Sergey Grebnov > Labels: config.xml, icons, images, windows > > MS platforms support the idea of MRT images where you refer to it as follows: > image.png > ...but underneath there are actually different images per DPI... > image.scale-100.png > image.scale-140.png > ... etc ... > The following must be improved to support MRT images > 1. Scaled image versions are copied to platform images folder if defined in > config.xml > 2. Ensure all new image files from platform images folder are added to the > project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[ https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139693#comment-14139693 ] ASF GitHub Bot commented on CB-7494: Github user asfgit closed the pull request at: https://github.com/apache/cordova-windows/pull/44 > cordova-windows fails to build app with unicode name using cordova/build.bat > script > --- > > Key: CB-7494 > URL: https://issues.apache.org/jira/browse/CB-7494 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Reporter: Vladimir Kotikov > > Repro steps (in cordova-windows repo): > {{windows\bin\create "testcreate 応用" com.test.app 応用}} > {{".windows\testcreate 応用\cordova\build"}} > Expected: > App builds successfully. > Actual: > {noformat} > package.windows80.appxmanifest(35,22): error APPX3032: App manifest > validation failed. > Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a > valid ASCII Windows ID. > It must contain one or more parts, separated with periods, where each part > contains only characters a-z, A-Z, 0-9, and does no t start with a digit. > [d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj] > {noformat} > This doesn't affects CLI > The reason is that bin/create script write app name and app id in wrong > places at *.manifest files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[ https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139692#comment-14139692 ] ASF subversion and git services commented on CB-7494: - Commit a315941efa1921712da7280689854a2e1daec34d in cordova-windows's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=a315941 ] Merge branch 'CB-7494' of https://github.com/MSOpenTech/cordova-windows > cordova-windows fails to build app with unicode name using cordova/build.bat > script > --- > > Key: CB-7494 > URL: https://issues.apache.org/jira/browse/CB-7494 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Reporter: Vladimir Kotikov > > Repro steps (in cordova-windows repo): > {{windows\bin\create "testcreate 応用" com.test.app 応用}} > {{".windows\testcreate 応用\cordova\build"}} > Expected: > App builds successfully. > Actual: > {noformat} > package.windows80.appxmanifest(35,22): error APPX3032: App manifest > validation failed. > Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a > valid ASCII Windows ID. > It must contain one or more parts, separated with periods, where each part > contains only characters a-z, A-Z, 0-9, and does no t start with a digit. > [d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj] > {noformat} > This doesn't affects CLI > The reason is that bin/create script write app name and app id in wrong > places at *.manifest files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[ https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139691#comment-14139691 ] ASF subversion and git services commented on CB-7494: - Commit fdce7411529e3630f6b7c17f9942a3113ba67c6e in cordova-windows's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=fdce741 ] CB-7494 Fixes wrong replacements in *.appxmanifest files > cordova-windows fails to build app with unicode name using cordova/build.bat > script > --- > > Key: CB-7494 > URL: https://issues.apache.org/jira/browse/CB-7494 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Reporter: Vladimir Kotikov > > Repro steps (in cordova-windows repo): > {{windows\bin\create "testcreate 応用" com.test.app 応用}} > {{".windows\testcreate 応用\cordova\build"}} > Expected: > App builds successfully. > Actual: > {noformat} > package.windows80.appxmanifest(35,22): error APPX3032: App manifest > validation failed. > Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a > valid ASCII Windows ID. > It must contain one or more parts, separated with periods, where each part > contains only characters a-z, A-Z, 0-9, and does no t start with a digit. > [d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj] > {noformat} > This doesn't affects CLI > The reason is that bin/create script write app name and app id in wrong > places at *.manifest files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6911) [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139687#comment-14139687 ] Angus Bremner commented on CB-6911: --- Hey Shazron, why is this pushed to 3.7? Can we get it in the 3.6 release? I know you say it doesn't cause any issues, but I am certain it is causing various js issues in my app. > [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when > accessing anything off window.navigator > > > Key: CB-6911 > URL: https://issues.apache.org/jira/browse/CB-6911 > Project: Apache Cordova > Issue Type: Sub-task > Components: CordovaJS > Environment: iOS 8 beta 5 (device) >Reporter: Jeff Schilling >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot > 2014-09-04 at 9.30.58 pm.png > > > references to window.navigator.* (platform, geolocation) etc fail with > Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-6911) [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-6911: - Fix Version/s: 3.7.0 > [CordovaJS][iOS 8] - "deprecated attempt to access property" errors when > accessing anything off window.navigator > > > Key: CB-6911 > URL: https://issues.apache.org/jira/browse/CB-6911 > Project: Apache Cordova > Issue Type: Sub-task > Components: CordovaJS > Environment: iOS 8 beta 5 (device) >Reporter: Jeff Schilling >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot > 2014-09-04 at 9.30.58 pm.png > > > references to window.navigator.* (platform, geolocation) etc fail with > Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7549) [StatusBar][iOS 8] Landscape issue
[ https://issues.apache.org/jira/browse/CB-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139656#comment-14139656 ] Shazron Abdullah commented on CB-7549: -- See CB-7596 > [StatusBar][iOS 8] Landscape issue > -- > > Key: CB-7549 > URL: https://issues.apache.org/jira/browse/CB-7549 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Statusbar >Affects Versions: 3.5.0 > Environment: Jquerymobile 1.4.3, Jquery 2.0.3, cordova 3.5 iOS, iOS 8 >Reporter: Tim Higgins >Assignee: Shazron Abdullah > > not for sure if this is an xcode setting, cordova ios8 issue or jquerymobile > ios8 issue. if you create a new cordova project, force it to Landscape > only(phone or ipad doesnt matter), then include JqueryMobile (1.4.3) and run > the project in iOS 8 the display will be chopped up into 3 sections. ReRun > it in iOS 7 simulator and everything is fine. so it has something to do with > being forced to Landscape. enclosed is the code i am using to recreate the > problem. > {code} > > > > > > > > > > href="http://code.jquery.com/mobile/1.4.3/jquery.mobile-1.4.3.min.css";> > > > > > > > div.div_Body { > height: 100%; > > position: relative; > border:2px solid DarkGoldenrod; > border-radius:7px; > font: bold 14px Arial; > font-family:Arial, Helvetica, sans-serif; > color:Black; > text-align:center; > background: #FF; > } > > > > > > > > window.addEventListener('load', function () { > document.addEventListener('deviceready', function () {onDeviceReady() }, > false); }, false); > > /* When this function is called, PhoneGap has been initialized and > is ready to roll */ > function onDeviceReady() > { > console.log("in device ready"); > console.log("height " + screen.height); > console.log("width " + screen.width); > var myscreenWidth = screen.width; >} > > > > > > >aria-level="1">Test > > > Send Help > > > >src="cordova.js"> > http://code.jquery.com/jquery-1.9.1.js";> > src="http://code.jquery.com/mobile/1.4.3/jquery.mobile-1.4.3.min.js";> > > > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139654#comment-14139654 ] ASF GitHub Bot commented on CB-7493: Github user asfgit closed the pull request at: https://github.com/apache/cordova-wp8/pull/57 > Add e2e test for 'space-in-path' and 'unicode in path/name' for core > platforms. > --- > > Key: CB-7493 > URL: https://issues.apache.org/jira/browse/CB-7493 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Since we have several issues with unicode in paths and app names it will be > great to have automated testing of these cases. > Best place to keep these tests is platform repo, so these tests can be ran > via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and > iOS) > For WP8 and windows platforms we already have such tests, so we need just to > improve them to test new cases. > For Android and iOS it will be necessary to implement tests. Implementation > will be very similar to windows/wp8 implementation. > Note that android currently doesn't have support for unicode symbols in app > name (due to android tools restrictions). So test for android should contain > only 'space' case test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139649#comment-14139649 ] ASF subversion and git services commented on CB-7493: - Commit a745b1293ee079805304ad9b81a611fdd1a5b9f3 in cordova-wp8's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;h=a745b12 ] Merge branch 'CB-7493' of https://github.com/MSOpenTech/cordova-wp8 > Add e2e test for 'space-in-path' and 'unicode in path/name' for core > platforms. > --- > > Key: CB-7493 > URL: https://issues.apache.org/jira/browse/CB-7493 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Since we have several issues with unicode in paths and app names it will be > great to have automated testing of these cases. > Best place to keep these tests is platform repo, so these tests can be ran > via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and > iOS) > For WP8 and windows platforms we already have such tests, so we need just to > improve them to test new cases. > For Android and iOS it will be necessary to implement tests. Implementation > will be very similar to windows/wp8 implementation. > Note that android currently doesn't have support for unicode symbols in app > name (due to android tools restrictions). So test for android should contain > only 'space' case test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139648#comment-14139648 ] ASF subversion and git services commented on CB-7493: - Commit 08e99982c7284090e08761e442b89463cd107450 in cordova-wp8's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;h=08e9998 ] CB-7493 Adds 'space-in-path' and 'unicode in name' tests for CI > Add e2e test for 'space-in-path' and 'unicode in path/name' for core > platforms. > --- > > Key: CB-7493 > URL: https://issues.apache.org/jira/browse/CB-7493 > Project: Apache Cordova > Issue Type: Bug > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Since we have several issues with unicode in paths and app names it will be > great to have automated testing of these cases. > Best place to keep these tests is platform repo, so these tests can be ran > via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and > iOS) > For WP8 and windows platforms we already have such tests, so we need just to > improve them to test new cases. > For Android and iOS it will be necessary to implement tests. Implementation > will be very similar to windows/wp8 implementation. > Note that android currently doesn't have support for unicode symbols in app > name (due to android tools restrictions). So test for android should contain > only 'space' case test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7596) [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent
[ https://issues.apache.org/jira/browse/CB-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139623#comment-14139623 ] ASF subversion and git services commented on CB-7596: - Commit b06ca8db4288f47e99f32294080106884e236d47 in cordova-ios's branch refs/heads/master from Clafou [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=b06ca8d ] CB-7596 - [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent iOS8 introduces a change to screen orientation, making [UIScreen bounds] orientation-dependent. Testing for the iPhone5 screen resolution now needs to account for landscape (568x320) in addition to portrait (320x568). Details at http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bound s-size-becoming-orientation-dependent-in-ios8 Signed-off-by: Shazron Abdullah > [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now > orientation dependent > -- > > Key: CB-7596 > URL: https://issues.apache.org/jira/browse/CB-7596 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > > UIScreen is now orientation dependent in iOS 8: > http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bounds-size-becoming-orientation-dependent-in-ios8 > If phone is 320x480 (w x h) portrait > in iOS 7, the (w x h) in landscape is 320x480. > Now in iOS 8, the (w x h) in landscape is 480x320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CB-7596) [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent
[ https://issues.apache.org/jira/browse/CB-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-7596. -- Resolution: Fixed > [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now > orientation dependent > -- > > Key: CB-7596 > URL: https://issues.apache.org/jira/browse/CB-7596 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > > UIScreen is now orientation dependent in iOS 8: > http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bounds-size-becoming-orientation-dependent-in-ios8 > If phone is 320x480 (w x h) portrait > in iOS 7, the (w x h) in landscape is 320x480. > Now in iOS 8, the (w x h) in landscape is 480x320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139621#comment-14139621 ] Martin Gonzalez commented on CB-6837: - Ok, I'll try to do this in another way. [~iclelland] do you have any comments regarding this issue? > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small time > window during the timeout in which this can be reproduced, something on the > order of 200ms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7596) [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent
[ https://issues.apache.org/jira/browse/CB-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-7596: - Issue Type: Sub-task (was: Bug) Parent: CB-7043 > [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now > orientation dependent > -- > > Key: CB-7596 > URL: https://issues.apache.org/jira/browse/CB-7596 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > > UIScreen is now orientation dependent in iOS 8: > http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bounds-size-becoming-orientation-dependent-in-ios8 > If phone is 320x480 (w x h) portrait > in iOS 7, the (w x h) in landscape is 320x480. > Now in iOS 8, the (w x h) in landscape is 480x320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139495#comment-14139495 ] Shazron Abdullah commented on CB-7539: -- It's perfectly good code, they just didn't bother to update it for the later SDKs, because... not important to them. The only way to see if this passes app review is to submit for app review. I wouldn't stir the hornet's nest by filing a radar -- lots of other apps use local webservers. GoodReader for example, and other apps that allow people to download the documents from the apps by sending ppl to a local url. > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7596) [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent
[ https://issues.apache.org/jira/browse/CB-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139492#comment-14139492 ] ASF GitHub Bot commented on CB-7596: Github user shazron commented on the pull request: https://github.com/apache/cordova-ios/pull/105#issuecomment-56101072 Ouch, yeah this resulted in a bug for the statusbar plugin as well for landscape (fixed) :/ Filed https://issues.apache.org/jira/browse/CB-7596 > [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now > orientation dependent > -- > > Key: CB-7596 > URL: https://issues.apache.org/jira/browse/CB-7596 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Fix For: 3.7.0 > > > UIScreen is now orientation dependent in iOS 8: > http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bounds-size-becoming-orientation-dependent-in-ios8 > If phone is 320x480 (w x h) portrait > in iOS 7, the (w x h) in landscape is 320x480. > Now in iOS 8, the (w x h) in landscape is 480x320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7596) [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent
Shazron Abdullah created CB-7596: Summary: [iOS 8] CDV_IsIPhone5() Macro needs to be updated because screen size is now orientation dependent Key: CB-7596 URL: https://issues.apache.org/jira/browse/CB-7596 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.7.0 UIScreen is now orientation dependent in iOS 8: http://stackoverflow.com/questions/24150359/is-uiscreen-mainscreen-bounds-size-becoming-orientation-dependent-in-ios8 If phone is 320x480 (w x h) portrait in iOS 7, the (w x h) in landscape is 320x480. Now in iOS 8, the (w x h) in landscape is 480x320 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139482#comment-14139482 ] Joe Bowser commented on CB-6837: OK, sorry about the blank message. Here's my comment. On Thu, Sep 18, 2014 at 11:22 AM, Martin Gonzalez (JIRA) The ChromeClient is no longer part of the Third-Party WebView API, so this is a non-starter. This would require an API change, and would have to be implemented on all Third Party WebViews This is the easiest, but the bug still exists. Either two or three, but I think that Ian should also comment on this API change, since this affects his work as well. > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small time > window during the timeout in which this ca
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139479#comment-14139479 ] Joe Bowser commented on CB-6837: On Thu, Sep 18, 2014 at 11:22 AM, Martin Gonzalez (JIRA) > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small time > window during the timeout in which this can be reproduced, something on the > order of 200ms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139471#comment-14139471 ] Carlos Santana commented on CB-7539: even without blessing from Apple and getting feedback. For Apps that are not publish to the App store like Enterprise Apps :-) I think it will be still useful to have this in. my 2 cents > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139468#comment-14139468 ] Carlos Santana commented on CB-7539: My point is that I saw this and means that Xcode is no longer recommending this code. and yes I agree with you using other code is even worst. Is there a way we can validate that if we use this code it passes App review. Maybe opening a radar asking? > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7383) [Release + 3.6.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139449#comment-14139449 ] ASF subversion and git services commented on CB-7383: - Commit e6c08eab884b139cfb90a7ef7ad509390082ba55 in cordova-cli's branch refs/heads/rb_3.6.0-0.2.8 from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=e6c08ea ] CB-7383 Updated version and RELEASENOTES.md for release 3.6.3-0.2.13 > [Release + 3.6.0] Parent Issue > -- > > Key: CB-7383 > URL: https://issues.apache.org/jira/browse/CB-7383 > Project: Apache Cordova > Issue Type: Task > Components: Amazon FireOS, Android, App Hello World, BlackBerry, > CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, > WP8 >Reporter: Steve Gill >Assignee: Jesse MacFadyen > Fix For: 3.6.0 > > > Parent bug for the 3.6.0 Cordova Release. > Workflow here: > http://wiki.apache.org/cordova/CuttingReleases > Release Master: ? > Component Leads: Refer to assignee of "Test & Tag" sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7383) [Release + 3.6.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139447#comment-14139447 ] ASF subversion and git services commented on CB-7383: - Commit 4ae0fa4bc3314930bcf4a83d95fe44f5b66221ee in cordova-plugman's branch refs/heads/rb_0.22.7 from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=4ae0fa4 ] CB-7383 Updated version and RELEASENOTES.md for release 0.22.10 > [Release + 3.6.0] Parent Issue > -- > > Key: CB-7383 > URL: https://issues.apache.org/jira/browse/CB-7383 > Project: Apache Cordova > Issue Type: Task > Components: Amazon FireOS, Android, App Hello World, BlackBerry, > CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, > WP8 >Reporter: Steve Gill >Assignee: Jesse MacFadyen > Fix For: 3.6.0 > > > Parent bug for the 3.6.0 Cordova Release. > Workflow here: > http://wiki.apache.org/cordova/CuttingReleases > Release Master: ? > Component Leads: Refer to assignee of "Test & Tag" sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7383) [Release + 3.6.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139416#comment-14139416 ] ASF subversion and git services commented on CB-7383: - Commit db6b5f5bf0d944b40d06f3b519aa8bf4a927af95 in cordova-lib's branch refs/heads/rb_0.21.10 from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=db6b5f5 ] CB-7383 Updated version and RELEASENOTES.md for release 0.21.13 > [Release + 3.6.0] Parent Issue > -- > > Key: CB-7383 > URL: https://issues.apache.org/jira/browse/CB-7383 > Project: Apache Cordova > Issue Type: Task > Components: Amazon FireOS, Android, App Hello World, BlackBerry, > CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, > WP8 >Reporter: Steve Gill >Assignee: Jesse MacFadyen > Fix For: 3.6.0 > > > Parent bug for the 3.6.0 Cordova Release. > Workflow here: > http://wiki.apache.org/cordova/CuttingReleases > Release Master: ? > Component Leads: Refer to assignee of "Test & Tag" sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CB-7518) Android - Don't run "android" command from within CLI/Plugman
[ https://issues.apache.org/jira/browse/CB-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-7518. --- Resolution: Fixed Fixed in 3.6.0-x.x.x > Android - Don't run "android" command from within CLI/Plugman > - > > Key: CB-7518 > URL: https://issues.apache.org/jira/browse/CB-7518 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Andrew Grieve >Assignee: Andrew Grieve >Priority: Minor > > The Android SDK auto-detection code (e.g. location ANDROID_HOME, putting > things in your PATH), is a part of cordova-android's check_reqs script, which > is not called from within CLI. So, we don't want to rely on the presense of > the "android" executable from within CLI. > Currently the only time it's called is for `` within plugins. With > the ANDROID_HOME changes in 3.6.0, running this isn't necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139326#comment-14139326 ] ASF subversion and git services commented on CB-7471: - Commit 407fbf291d9a99b8ba81251f4d6842cc0e4bd0b1 in cordova-coho's branch refs/heads/CB-7471 from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=407fbf2 ] Merge branch 'CB-7471' > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139325#comment-14139325 ] ASF subversion and git services commented on CB-7471: - Commit 2d4ac35161f3ecde9b898aedbd7b0214e4b2e81a in cordova-coho's branch refs/heads/CB-7471 from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=2d4ac35 ] CB-7471 added link to youtube video demoing Cordova translations > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139322#comment-14139322 ] ASF subversion and git services commented on CB-7471: - Commit 407fbf291d9a99b8ba81251f4d6842cc0e4bd0b1 in cordova-coho's branch refs/heads/master from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=407fbf2 ] Merge branch 'CB-7471' > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139320#comment-14139320 ] ASF subversion and git services commented on CB-7471: - Commit f4ae79d4c1ee74a9bab75c113e7b480957329c04 in cordova-coho's branch refs/heads/master from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=f4ae79d ] CB-7471 added link to youtube video demoing Cordova translations > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139321#comment-14139321 ] ASF subversion and git services commented on CB-7471: - Commit 2d4ac35161f3ecde9b898aedbd7b0214e4b2e81a in cordova-coho's branch refs/heads/master from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=2d4ac35 ] CB-7471 added link to youtube video demoing Cordova translations > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139297#comment-14139297 ] Shazron Abdullah commented on CB-7539: -- If we update to whatever Xcode recommends, should be ok. We only need this as an asset loader. I'm reluctant to use other code with more whizbang features that we don't need and don't understand. Trying to keep it simple. > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139286#comment-14139286 ] Martin Gonzalez commented on CB-6837: - 1.- I can, just use the CordovaView to call the destruction of the dialogs, at the chromeClient, without touch the activity, refactor all of it, and make a PR for 4.x too, addressing to its respective classes there. 2.- Do not touch ChromeClient at all, and somehow fix the issue just during handleDestroy() at CordovaWebView/AndroidWebView (refactor too). 3.- Can't accept any of this changes for any of the classes, don't spend more time with it. well Joe, could you please tell me, which path should I follow? > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small t
[jira] [Commented] (CB-7539) [WKWebView][iOS 8] Use local webserver option to load local HTML file from www
[ https://issues.apache.org/jira/browse/CB-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139270#comment-14139270 ] Carlos Santana commented on CB-7539: I went to the link and get this, any concerns? Retired Document Important: This sample code may not represent best practices for current development. The project may use deprecated symbols and illustrate technologies and techniques that are no longer recommended. > [WKWebView][iOS 8] Use local webserver option to load local HTML file from www > -- > > Key: CB-7539 > URL: https://issues.apache.org/jira/browse/CB-7539 > Project: Apache Cordova > Issue Type: Sub-task > Components: iOS >Reporter: Shazron Abdullah >Priority: Blocker > > This workaround is because of this bug: > http://www.openradar.me/radar?id=5839348817723392 > (filed with Apple of course also) > I'm still hoping that Apple fixes this in iOS 8.1, but we should have this as > a contingency plan. > Create this as an included plugin, so it can be extracted later if need be. > We need to secure access to the local webserver, probably through a session > token in the header, since background apps can have access to the webserver. > The session token is passed down to the initially loaded local page specified > from the tag in config.xml, and should be used in the cordova.exec > call. We would also need to implement local proxy support , see CB-7348 > This all sounds more complex than it needs to be than just loading a file url > -- wishing Apple would just fix this in iOS 8.1 instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139235#comment-14139235 ] Joe Bowser commented on CB-6837: I think handleDestroy would have to be where this lives, and I really don't want extra code in CordovaWebView or CordovaChromeClient, especially since those classes have been through a massive refactor. I can't accept the pull request as is right now since it's not compatible with the 4.0.x branch. > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small time > window during the timeout in which this can be reproduced, something on the > order of 200ms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7595) network.connection.type bug on Android L
Nathaniel Foster created CB-7595: Summary: network.connection.type bug on Android L Key: CB-7595 URL: https://issues.apache.org/jira/browse/CB-7595 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Network Information Affects Versions: 3.5.0 Environment: Android, Nexus 5, Reporter: Nathaniel Foster I am testing out my Cordova 3.5 app on the developer version of Android L. Navigator.connection.type returns "unknown" when I am connected to my mobile network (TMobile). When I am connected to wifi it returns "wifi". It works fine when I test on previous versions of Android. Not sure if this is a Cordova issue or Android issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6837) Hitting Back button while alert being rendered causes leaked window
[ https://issues.apache.org/jira/browse/CB-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139209#comment-14139209 ] Martin Gonzalez commented on CB-6837: - Hey [~bowserj], well the CordovaChromeClient will capture all dialogs and keep a record of them, CordovaActivy doesn't have a direct access to the chromeClient, the other way to do so, it would be call 'destroyAllDialogs' (this.chromeClient.destroyAllDialogs()) , from 'handleDestroy()' at CordovaWebView. Removing the CordovaActivity involvement and also 'destroyDialogs' method from the CordovaWebView. > Hitting Back button while alert being rendered causes leaked window > --- > > Key: CB-6837 > URL: https://issues.apache.org/jira/browse/CB-6837 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Marcel Kinard >Assignee: Martin Gonzalez > Attachments: index.html > > > On master and using dialogs plugin. Using a trivial app that has a button to > create an alert dialog after 500ms timeout. If the Back button is hit at > approximately the same time as the timer expires and the alert is to be > shown, the following exception appears in logcat: > D/CordovaWebView( 8178): The current URL is: > file:///android_asset/www/index.html > D/CordovaWebView( 8178): The URL at item 0 is: > file:///android_asset/www/index.html > D/dalvikvm( 513): GC_FOR_ALLOC freed 306K, 13% free 14164K/16240K, paused > 54ms, total 55ms > D/CordovaActivity( 8178): Paused the application! > D/CordovaWebView( 8178): Handle the pause > W/IInputConnectionWrapper( 8178): showStatusIcon on inactive InputConnection > W/InputMethodManagerService( 513): Starting input on non-focused client > com.android.internal.view.IInputMethodClient$Stub$Proxy@42396598 (uid=10050 > pid=8178) > D/CordovaActivity( 8178): CordovaActivity.onDestroy() > D/CordovaWebView( 8178): >>> loadUrlNow() > E/WindowManager( 8178): > E/WindowManager( 8178): android.view.WindowLeaked: Activity > com.example.Example has leaked window > com.android.internal.policy.impl.PhoneWindow$DecorView{41f0d8b8 V.E. > R.I. 0,0-465,256} that was originally added here > E/WindowManager( 8178): at > android.view.ViewRootImpl.(ViewRootImpl.java:348) > E/WindowManager( 8178): at > android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:248) > E/WindowManager( 8178): at > android.view.WindowManagerImpl.addView(WindowManagerImpl.java:69) > E/WindowManager( 8178): at android.app.Dialog.show(Dialog.java:286) > E/WindowManager( 8178): at > android.app.AlertDialog$Builder.show(AlertDialog.java:951) > E/WindowManager( 8178): at > org.apache.cordova.CordovaChromeClient.onJsAlert(CordovaChromeClient.java:143) > E/WindowManager( 8178): at > com.android.webview.chromium.WebViewContentsClientAdapter.handleJsAlert(WebViewContentsClientAdapter.java:606) > E/WindowManager( 8178): at > com.android.org.chromium.android_webview.AwContentsClientBridge.handleJsAlert(AwContentsClientBridge.java:73) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native > Method) > E/WindowManager( 8178): at > com.android.org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:27) > E/WindowManager( 8178): at > android.os.Handler.dispatchMessage(Handler.java:102) > E/WindowManager( 8178): at android.os.Looper.loop(Looper.java:136) > E/WindowManager( 8178): at > android.app.ActivityThread.main(ActivityThread.java:5017) > E/WindowManager( 8178): at java.lang.reflect.Method.invokeNative(Native > Method) > E/WindowManager( 8178): at > java.lang.reflect.Method.invoke(Method.java:515) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) > E/WindowManager( 8178): at > com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) > E/WindowManager( 8178): at dalvik.system.NativeStart.main(Native Method) > D/CordovaWebViewClient( 8178): onPageFinished(about:blank) > D/CordovaActivity( 8178): onMessage(onPageFinished,about:blank) > D/CordovaActivity( 8178): onMessage(exit,null) > It looks like there is an attempt to show the alert dialog after the > activity's onDestroy() method has been called. > When resuming the app by clicking on it's icon in the home screen or using > the Multitask button, the webview doesn't render completely, I see only a > black screen with the usual status bar. The app must be killed, and then it > works fine after a restart. It appears that there is a pretty small time > window during the timeout in which this can be reproduced, something on the > order of 200ms. -- Th
[jira] [Commented] (CB-7548) [BlackBerry10] dateToString format error
[ https://issues.apache.org/jira/browse/CB-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139212#comment-14139212 ] ASF subversion and git services commented on CB-7548: - Commit d497d35c2361acd7b05b5950cc371625b23cad9d in cordova-plugin-globalization's branch refs/heads/master from Lianghui Chen [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-globalization.git;h=d497d35 ] CB-7548 [BlackBerry10] Re-implement getPreferredLanguage() and getLocaleName(). Previous implementation of getPreferredLanguage() is using language info from default locale, which is wrong. The new implementation reflects the actual UI language selected, instead of the language for the default locale. > [BlackBerry10] dateToString format error > > > Key: CB-7548 > URL: https://issues.apache.org/jira/browse/CB-7548 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Globalization >Reporter: Bryan Higgins >Assignee: Bryan Higgins >Priority: Minor > Fix For: 3.6.0 > > > Tested on Z10, trunk (2558) > and iOS 7.1 > --- Steps to Reproduce: --- > var date1 = new Date(01/01/01); > function dateToStringSuccessCallback(date) { > console.log("date: " + date.value); > } > function errorCallback(err) { > console.log("ERROR: " + err.message); > } > navigator.globalization.dateToString(date1, dateToStringSuccessCallback, > errorCallback, {formatLength:'full', selector:'date and time'} ); > When running the above date in iOS and BlackBerry results in a date of > Wed Dec 31 1969 19:00:00 GMT-0500 (EST) > But when executing the dateToString on the same value, results in two > different values. > --- Actual Result: --- > on iOS you get: > 12/31/69, 7:00 PM > on BlackBerry you will get: > Date in wrong format! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7471) Translations for September
[ https://issues.apache.org/jira/browse/CB-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139208#comment-14139208 ] ASF subversion and git services commented on CB-7471: - Commit f4ae79d4c1ee74a9bab75c113e7b480957329c04 in cordova-coho's branch refs/heads/CB-7471 from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=f4ae79d ] CB-7471 added link to youtube video demoing Cordova translations > Translations for September > -- > > Key: CB-7471 > URL: https://issues.apache.org/jira/browse/CB-7471 > Project: Apache Cordova > Issue Type: Improvement > Components: Translation >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7574) coho create-archive has fatal error for plugins
[ https://issues.apache.org/jira/browse/CB-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139205#comment-14139205 ] ASF subversion and git services commented on CB-7574: - Commit a5decc8a99712cc2fc28984e7d8ff85bae1a5d0a in cordova-coho's branch refs/heads/CB-7471 from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=a5decc8 ] CB-7574 generate plugins as a zip archive instead npm pack > coho create-archive has fatal error for plugins > --- > > Key: CB-7574 > URL: https://issues.apache.org/jira/browse/CB-7574 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: 3.7.0 > > > When trying to create a signed archive for a plugin, it fails with the error > "argument to path.join is null". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7590) Cordova W3C Battery Alignment - levelchange event
Lisa Seacat DeLuca created CB-7590: -- Summary: Cordova W3C Battery Alignment - levelchange event Key: CB-7590 URL: https://issues.apache.org/jira/browse/CB-7590 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called level. The level attribute must be set to 0 if the system's battery is depleted and the system is about to be suspended, and to 1.0 if the battery is full, the implementation is unable to report the battery's level, or there is no battery attached to the system. Mulitple Batteries. level attribute. The level attribute can be set to the average of the levels of batteries of same capacity, or the weighted average of the battery level attributes for batteries of different capacities. Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CB-7371) [Android] App crashes after phone language change
[ https://issues.apache.org/jira/browse/CB-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Gonzalez closed CB-7371. --- Resolution: Cannot Reproduce The latest changes on master, resolved this specific issue, so the fix made, won't be applied, it's not required. > [Android] App crashes after phone language change > - > > Key: CB-7371 > URL: https://issues.apache.org/jira/browse/CB-7371 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 > Environment: 4.2.2 (Jelly-Bean) > 4.4.2 (KitKat) >Reporter: Martin Gonzalez >Assignee: Martin Gonzalez > Labels: android, crash > Fix For: 3.7.0 > > > After switching device language on android, the app will fails to reload > scenario: > 1. Create new app > 2. open it and exit with the home button > 3.Switch device language to or any other > 4. Resume the app > Expected result : > the app should run > Actual result: > app crashes on first load > Log: > 07-28 16:24:10.018: D/CordovaActivity(25402): CordovaActivity.onDestroy() > 07-28 16:24:10.028: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.038: I/CordovaLog(25402): Changing log level to DEBUG(3) > 07-28 16:24:10.038: I/CordovaLog(25402): Found start page location: > cdvtests/index.html > 07-28 16:24:10.038: D/CordovaActivity(25402): CordovaActivity.onCreate() > 07-28 16:24:10.048: D/CordovaActivity(25402): CordovaActivity.init() > 07-28 16:24:10.058: D/CordovaWebView(25402): >>> > loadUrl(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.068: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.068: I/CordovaLog(25402): Found start page location: > cdvtests/index.html > 07-28 16:24:10.068: D/CordovaActivity(25402): Resuming the App > 07-28 16:24:10.068: D/CordovaActivity(25402): CB-3064: The errorUrl is null > 07-28 16:24:10.078: D/CordovaWebViewClient(25402): onPageStarted(about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): > onMessage(onPageStarted,about:blank) > 07-28 16:24:10.078: D/CordovaWebViewClient(25402): onPageFinished(about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): > onMessage(onPageFinished,about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): onMessage(exit,null) > 07-28 16:24:10.088: D/CordovaWebViewClient(25402): > onPageStarted(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.088: D/CordovaActivity(25402): > onMessage(onPageStarted,file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.108: D/CordovaActivity(25402): Paused the application! > 07-28 16:24:10.108: D/CordovaWebView(25402): Handle the pause > 07-28 16:24:10.148: D/CordovaActivity(25402): CordovaActivity.onDestroy() > 07-28 16:24:10.148: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.158: D/CordovaWebViewClient(25402): > onPageFinished(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.158: D/CordovaActivity(25402): > onMessage(onPageFinished,file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.168: D/CordovaWebViewClient(25402): onPageStarted(about:blank) > 07-28 16:24:10.168: D/CordovaActivity(25402): > onMessage(onPageStarted,about:blank) > 07-28 16:24:10.188: D/CordovaWebViewClient(25402): onPageFinished(about:blank) > 07-28 16:24:10.188: D/CordovaActivity(25402): > onMessage(onPageFinished,about:blank) > 07-28 16:24:10.188: D/CordovaActivity(25402): onMessage(exit,null) > 07-28 16:24:12.168: D/CordovaActivity(25402): onMessage(spinner,stop) > 07-28 16:24:12.188: D/CordovaActivity(25402): onMessage(spinner,stop) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7594) Cordova W3C Battery Alignment - Deprecate support for batterylow
[ https://issues.apache.org/jira/browse/CB-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7594: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterylow. There is no notion of batterylow in the latest W3C spec for battery was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterystatus. There is no notion of batterystatus in the latest W3C spec for battery > Cordova W3C Battery Alignment - Deprecate support for batterylow > > > Key: CB-7594 > URL: https://issues.apache.org/jira/browse/CB-7594 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > Deprecate support for batterylow. There is no notion of batterylow in the > latest W3C spec for battery -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7371) [Android] App crashes after phone language change
[ https://issues.apache.org/jira/browse/CB-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139156#comment-14139156 ] Martin Gonzalez commented on CB-7371: - Tested and confirmed that the issues has been fixed with the latest changes on master. By the time that I made it, the issue still was present in master. Thanks for the review Joe. > [Android] App crashes after phone language change > - > > Key: CB-7371 > URL: https://issues.apache.org/jira/browse/CB-7371 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 > Environment: 4.2.2 (Jelly-Bean) > 4.4.2 (KitKat) >Reporter: Martin Gonzalez >Assignee: Martin Gonzalez > Labels: android, crash > Fix For: 3.7.0 > > > After switching device language on android, the app will fails to reload > scenario: > 1. Create new app > 2. open it and exit with the home button > 3.Switch device language to or any other > 4. Resume the app > Expected result : > the app should run > Actual result: > app crashes on first load > Log: > 07-28 16:24:10.018: D/CordovaActivity(25402): CordovaActivity.onDestroy() > 07-28 16:24:10.028: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.038: I/CordovaLog(25402): Changing log level to DEBUG(3) > 07-28 16:24:10.038: I/CordovaLog(25402): Found start page location: > cdvtests/index.html > 07-28 16:24:10.038: D/CordovaActivity(25402): CordovaActivity.onCreate() > 07-28 16:24:10.048: D/CordovaActivity(25402): CordovaActivity.init() > 07-28 16:24:10.058: D/CordovaWebView(25402): >>> > loadUrl(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.068: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.068: I/CordovaLog(25402): Found start page location: > cdvtests/index.html > 07-28 16:24:10.068: D/CordovaActivity(25402): Resuming the App > 07-28 16:24:10.068: D/CordovaActivity(25402): CB-3064: The errorUrl is null > 07-28 16:24:10.078: D/CordovaWebViewClient(25402): onPageStarted(about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): > onMessage(onPageStarted,about:blank) > 07-28 16:24:10.078: D/CordovaWebViewClient(25402): onPageFinished(about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): > onMessage(onPageFinished,about:blank) > 07-28 16:24:10.078: D/CordovaActivity(25402): onMessage(exit,null) > 07-28 16:24:10.088: D/CordovaWebViewClient(25402): > onPageStarted(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.088: D/CordovaActivity(25402): > onMessage(onPageStarted,file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.108: D/CordovaActivity(25402): Paused the application! > 07-28 16:24:10.108: D/CordovaWebView(25402): Handle the pause > 07-28 16:24:10.148: D/CordovaActivity(25402): CordovaActivity.onDestroy() > 07-28 16:24:10.148: D/CordovaWebView(25402): >>> loadUrlNow() > 07-28 16:24:10.158: D/CordovaWebViewClient(25402): > onPageFinished(file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.158: D/CordovaActivity(25402): > onMessage(onPageFinished,file:///android_asset/www/cdvtests/index.html) > 07-28 16:24:10.168: D/CordovaWebViewClient(25402): onPageStarted(about:blank) > 07-28 16:24:10.168: D/CordovaActivity(25402): > onMessage(onPageStarted,about:blank) > 07-28 16:24:10.188: D/CordovaWebViewClient(25402): onPageFinished(about:blank) > 07-28 16:24:10.188: D/CordovaActivity(25402): > onMessage(onPageFinished,about:blank) > 07-28 16:24:10.188: D/CordovaActivity(25402): onMessage(exit,null) > 07-28 16:24:12.168: D/CordovaActivity(25402): onMessage(spinner,stop) > 07-28 16:24:12.188: D/CordovaActivity(25402): onMessage(spinner,stop) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7592) Cordova W3C Battery Alignment - Deprecate support for batterycritical
[ https://issues.apache.org/jira/browse/CB-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7592: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterycritical. There is no notion of batterycritical in the latest W3C spec for battery was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Multiple Batteries. BatteryManager should expose a unified view of the batteries. See individual property sub-bullets for more information on how to handle multiple batteries for each property > Cordova W3C Battery Alignment - Deprecate support for batterycritical > - > > Key: CB-7592 > URL: https://issues.apache.org/jira/browse/CB-7592 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > Deprecate support for batterycritical. There is no notion of batterycritical > in the latest W3C spec for battery -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7594) Cordova W3C Battery Alignment - Deprecate support for batterylow
Lisa Seacat DeLuca created CB-7594: -- Summary: Cordova W3C Battery Alignment - Deprecate support for batterylow Key: CB-7594 URL: https://issues.apache.org/jira/browse/CB-7594 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterystatus. There is no notion of batterystatus in the latest W3C spec for battery -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7593) Cordova W3C Battery Alignment - Deprecate support for batterystatus
Lisa Seacat DeLuca created CB-7593: -- Summary: Cordova W3C Battery Alignment - Deprecate support for batterystatus Key: CB-7593 URL: https://issues.apache.org/jira/browse/CB-7593 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterycritical. There is no notion of batterycritical in the latest W3C spec for battery -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7593) Cordova W3C Battery Alignment - Deprecate support for batterystatus
[ https://issues.apache.org/jira/browse/CB-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7593: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterystatus. There is no notion of batterystatus in the latest W3C spec for battery was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Deprecate support for batterycritical. There is no notion of batterycritical in the latest W3C spec for battery > Cordova W3C Battery Alignment - Deprecate support for batterystatus > --- > > Key: CB-7593 > URL: https://issues.apache.org/jira/browse/CB-7593 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > Deprecate support for batterystatus. There is no notion of batterystatus in > the latest W3C spec for battery -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7592) Cordova W3C Battery Alignment - Deprecate support for batterycritical
Lisa Seacat DeLuca created CB-7592: -- Summary: Cordova W3C Battery Alignment - Deprecate support for batterycritical Key: CB-7592 URL: https://issues.apache.org/jira/browse/CB-7592 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Multiple Batteries. BatteryManager should expose a unified view of the batteries. See individual property sub-bullets for more information on how to handle multiple batteries for each property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7591) Cordova W3C Battery Alignment - multiple batteries
[ https://issues.apache.org/jira/browse/CB-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7591: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing Multiple Batteries. BatteryManager should expose a unified view of the batteries. See individual property sub-bullets for more information on how to handle multiple batteries for each property was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing levelchange event. When the battery level is updated, the user agent mustqueue a task which sets the level attribute's value and fires a simple eventnamed levelchange at the BatteryManager object. event handler: onlevelchange Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); > Cordova W3C Battery Alignment - multiple batteries > -- > > Key: CB-7591 > URL: https://issues.apache.org/jira/browse/CB-7591 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > Multiple Batteries. BatteryManager should expose a unified view of the > batteries. See individual property sub-bullets for more information on how > to handle multiple batteries for each property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7590) Cordova W3C Battery Alignment - levelchange event
[ https://issues.apache.org/jira/browse/CB-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7590: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing levelchange event. When the battery level is updated, the user agent mustqueue a task which sets the level attribute's value and fires a simple eventnamed levelchange at the BatteryManager object. event handler: onlevelchange Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called level. The level attribute must be set to 0 if the system's battery is depleted and the system is about to be suspended, and to 1.0 if the battery is full, the implementation is unable to report the battery's level, or there is no battery attached to the system. Mulitple Batteries. level attribute. The level attribute can be set to the average of the levels of batteries of same capacity, or the weighted average of the battery level attributes for batteries of different capacities. Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); > Cordova W3C Battery Alignment - levelchange event > - > > Key: CB-7590 > URL: https://issues.apache.org/jira/browse/CB-7590 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > levelchange event. When the battery level is updated, the user agent > mustqueue a task which sets the level attribute's value and fires a simple > eventnamed levelchange at the BatteryManager object. > event handler: onlevelchange > Example: > // We get the initial value when the promise resolves ... > navigator.getBattery().then(function(battery) { > console.log(battery.level); > // ... and any subsequent updates. > battery.onlevelchange = function() { > console.log(this.level); > }; > }); > Example 2 (Alternative): > navigator.getBattery().then(function(battery) { > console.log(battery.level); > battery.addEventListener('levelchange', function() { > console.log(this.level); > }); > }); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7589) Cordova W3C Battery Alignment - level property
[ https://issues.apache.org/jira/browse/CB-7589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7589: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called level. The level attribute must be set to 0 if the system's battery is depleted and the system is about to be suspended, and to 1.0 if the battery is full, the implementation is unable to report the battery's level, or there is no battery attached to the system. Mulitple Batteries. level attribute. The level attribute can be set to the average of the levels of batteries of same capacity, or the weighted average of the battery level attributes for batteries of different capacities. Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing dischargingtimechange event. When the battery discharging time is updated, the user agent must queue a task which sets the dischargingTime attribute's value and fires a simple event nameddischargingtimechange at the BatteryManager object. event handler: ondischargingtimechange > Cordova W3C Battery Alignment - level property > -- > > Key: CB-7589 > URL: https://issues.apache.org/jira/browse/CB-7589 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > The BatteryManager object should have a readonly property called level. The > level attribute must be set to 0 if the system's battery is depleted and the > system is about to be suspended, and to 1.0 if the battery is full, the > implementation is unable to report the battery's level, or there is no > battery attached to the system. > Mulitple Batteries. level attribute. The level attribute can be set to the > average of the levels of batteries of same capacity, or the weighted average > of the battery level attributes for batteries of different capacities. > Example: > // We get the initial value when the promise resolves ... > navigator.getBattery().then(function(battery) { > console.log(battery.level); > // ... and any subsequent updates. > battery.onlevelchange = function() { > console.log(this.level); > }; > }); > Example 2 (Alternative): > navigator.getBattery().then(function(battery) { > console.log(battery.level); > battery.addEventListener('levelchange', function() { > console.log(this.level); > }); > }); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7591) Cordova W3C Battery Alignment - multiple batteries
Lisa Seacat DeLuca created CB-7591: -- Summary: Cordova W3C Battery Alignment - multiple batteries Key: CB-7591 URL: https://issues.apache.org/jira/browse/CB-7591 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing levelchange event. When the battery level is updated, the user agent mustqueue a task which sets the level attribute's value and fires a simple eventnamed levelchange at the BatteryManager object. event handler: onlevelchange Example: // We get the initial value when the promise resolves ... navigator.getBattery().then(function(battery) { console.log(battery.level); // ... and any subsequent updates. battery.onlevelchange = function() { console.log(this.level); }; }); Example 2 (Alternative): navigator.getBattery().then(function(battery) { console.log(battery.level); battery.addEventListener('levelchange', function() { console.log(this.level); }); }); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7589) Cordova W3C Battery Alignment - level property
Lisa Seacat DeLuca created CB-7589: -- Summary: Cordova W3C Battery Alignment - level property Key: CB-7589 URL: https://issues.apache.org/jira/browse/CB-7589 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing dischargingtimechange event. When the battery discharging time is updated, the user agent must queue a task which sets the dischargingTime attribute's value and fires a simple event nameddischargingtimechange at the BatteryManager object. event handler: ondischargingtimechange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7588) Cordova W3C Battery Alignment - dischargingTimeChange event
[ https://issues.apache.org/jira/browse/CB-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7588: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing dischargingtimechange event. When the battery discharging time is updated, the user agent must queue a task which sets the dischargingTime attribute's value and fires a simple event nameddischargingtimechange at the BatteryManager object. event handler: ondischargingtimechange was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called dischargingTime. The dischargingTime attribute must be set to the value positive Infinity, if the battery is charging, the implementation is unable to report the remaining discharging time, there is no battery attached to the system, or otherwise. Multiple Batteries. dischargingTime. The dischargingTime attribute can be set to the maximum discharging time of the individual batteries if discharging in parallel, and to the sum of individual discharging times if discharging serial > Cordova W3C Battery Alignment - dischargingTimeChange event > --- > > Key: CB-7588 > URL: https://issues.apache.org/jira/browse/CB-7588 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > dischargingtimechange event. When the battery discharging time is updated, > the user agent must queue a task which sets the dischargingTime attribute's > value and fires a simple event nameddischargingtimechange at the > BatteryManager object. > event handler: ondischargingtimechange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7588) Cordova W3C Battery Alignment - dischargingTimeChange event
Lisa Seacat DeLuca created CB-7588: -- Summary: Cordova W3C Battery Alignment - dischargingTimeChange event Key: CB-7588 URL: https://issues.apache.org/jira/browse/CB-7588 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called dischargingTime. The dischargingTime attribute must be set to the value positive Infinity, if the battery is charging, the implementation is unable to report the remaining discharging time, there is no battery attached to the system, or otherwise. Multiple Batteries. dischargingTime. The dischargingTime attribute can be set to the maximum discharging time of the individual batteries if discharging in parallel, and to the sum of individual discharging times if discharging serial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7587) Cordova W3C Battery Alignment - dischargingTime event
[ https://issues.apache.org/jira/browse/CB-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7587: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called dischargingTime. The dischargingTime attribute must be set to the value positive Infinity, if the battery is charging, the implementation is unable to report the remaining discharging time, there is no battery attached to the system, or otherwise. Multiple Batteries. dischargingTime. The dischargingTime attribute can be set to the maximum discharging time of the individual batteries if discharging in parallel, and to the sum of individual discharging times if discharging serial was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing chargingtimechange event. When the battery charging time is updated, the user agent mustqueue a task which sets the chargingTime attribute's value and fires a simple event named chargingtimechange at the BatteryManager object. event handler: onchargingtimechange > Cordova W3C Battery Alignment - dischargingTime event > - > > Key: CB-7587 > URL: https://issues.apache.org/jira/browse/CB-7587 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > The BatteryManager object should have a readonly property called > dischargingTime. The dischargingTime attribute must be set to the value > positive Infinity, if the battery is charging, the implementation is unable > to report the remaining discharging time, there is no battery attached to the > system, or otherwise. > Multiple Batteries. dischargingTime. The dischargingTime attribute can be set > to the maximum discharging time of the individual batteries if discharging in > parallel, and to the sum of individual discharging times if discharging serial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7587) Cordova W3C Battery Alignment - dischargingTime property
[ https://issues.apache.org/jira/browse/CB-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7587: --- Summary: Cordova W3C Battery Alignment - dischargingTime property (was: Cordova W3C Battery Alignment - dischargingTime event) > Cordova W3C Battery Alignment - dischargingTime property > > > Key: CB-7587 > URL: https://issues.apache.org/jira/browse/CB-7587 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > The BatteryManager object should have a readonly property called > dischargingTime. The dischargingTime attribute must be set to the value > positive Infinity, if the battery is charging, the implementation is unable > to report the remaining discharging time, there is no battery attached to the > system, or otherwise. > Multiple Batteries. dischargingTime. The dischargingTime attribute can be set > to the maximum discharging time of the individual batteries if discharging in > parallel, and to the sum of individual discharging times if discharging serial -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7585) Cordova W3C Battery Alignment - chargingTime property
[ https://issues.apache.org/jira/browse/CB-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7585: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called chargingTime. The chargingTime attribute must be set to 0, if the battery is full or there is no battery attached to the system, and to the value positive Infinity if the battery is discharging, the implementation is unable to report the remaining charging time, or otherwise. Multiple Batteries. chargingTime. The chargingTime attribute can be set to the maximum charging time of the individual batteries if charging in parallel, and to the sum of the individual charging times if charging serially. was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing chargingchange event. When the battery charging state is updated, the user agent must queue a task which sets the charging attribute's value and fires a simple event named chargingchange at the BatteryManager object. event handler: onchargingchange > Cordova W3C Battery Alignment - chargingTime property > - > > Key: CB-7585 > URL: https://issues.apache.org/jira/browse/CB-7585 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > The BatteryManager object should have a readonly property called > chargingTime. The chargingTime attribute must be set to 0, if the battery is > full or there is no battery attached to the system, and to the value positive > Infinity if the battery is discharging, the implementation is unable to > report the remaining charging time, or otherwise. > Multiple Batteries. chargingTime. The chargingTime attribute can be set to > the maximum charging time of the individual batteries if charging in > parallel, and to the sum of the individual charging times if charging > serially. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7586) Cordova W3C Battery Alignment - chargingTimeChange event
[ https://issues.apache.org/jira/browse/CB-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7586: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing chargingtimechange event. When the battery charging time is updated, the user agent mustqueue a task which sets the chargingTime attribute's value and fires a simple event named chargingtimechange at the BatteryManager object. event handler: onchargingtimechange was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called chargingTime. The chargingTime attribute must be set to 0, if the battery is full or there is no battery attached to the system, and to the value positive Infinity if the battery is discharging, the implementation is unable to report the remaining charging time, or otherwise. Multiple Batteries. chargingTime. The chargingTime attribute can be set to the maximum charging time of the individual batteries if charging in parallel, and to the sum of the individual charging times if charging serially. > Cordova W3C Battery Alignment - chargingTimeChange event > > > Key: CB-7586 > URL: https://issues.apache.org/jira/browse/CB-7586 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > chargingtimechange event. When the battery charging time is updated, the user > agent mustqueue a task which sets the chargingTime attribute's value and > fires a simple event named chargingtimechange at the BatteryManager object. > event handler: onchargingtimechange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7584) Cordova W3C Battery Alignment - chargingchange event
[ https://issues.apache.org/jira/browse/CB-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-7584: --- Description: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing chargingchange event. When the battery charging state is updated, the user agent must queue a task which sets the charging attribute's value and fires a simple event named chargingchange at the BatteryManager object. event handler: onchargingchange was: JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called charging. Charging is a boolean. The charging attribute must be set to false if the battery is discharging, and set to true, if the battery is charging, the implementation is unable to report the state, or there is no battery attached to the system, or otherwise. Multiple Batteries. charging. The charging attribute must be set to true if at least one battery's charging state as described above is true. Otherwise, it must be set to false. > Cordova W3C Battery Alignment - chargingchange event > > > Key: CB-7584 > URL: https://issues.apache.org/jira/browse/CB-7584 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin Battery Status >Reporter: Lisa Seacat DeLuca > > JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 > Cordova documentation: > https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md > > w3c spec: http://www.w3.org/TR/battery-status > Gap analysis document can be found here: > https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing > chargingchange event. When the battery charging state is updated, the user > agent must queue a task which sets the charging attribute's value and fires a > simple event named chargingchange at the BatteryManager object. > event handler: onchargingchange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7587) Cordova W3C Battery Alignment - dischargingTime event
Lisa Seacat DeLuca created CB-7587: -- Summary: Cordova W3C Battery Alignment - dischargingTime event Key: CB-7587 URL: https://issues.apache.org/jira/browse/CB-7587 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing chargingtimechange event. When the battery charging time is updated, the user agent mustqueue a task which sets the chargingTime attribute's value and fires a simple event named chargingtimechange at the BatteryManager object. event handler: onchargingtimechange -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7586) Cordova W3C Battery Alignment - chargingTimeChange event
Lisa Seacat DeLuca created CB-7586: -- Summary: Cordova W3C Battery Alignment - chargingTimeChange event Key: CB-7586 URL: https://issues.apache.org/jira/browse/CB-7586 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Battery Status Reporter: Lisa Seacat DeLuca JIRA parent issue: https://issues.apache.org/jira/browse/CB-6065 Cordova documentation: https://github.com/apache/cordova-plugin-battery-status/blob/master/doc/index.md w3c spec: http://www.w3.org/TR/battery-status Gap analysis document can be found here: https://docs.google.com/document/d/1mAcjwf39IcIqpIuS-7SzlDxTgk4OebCHae6yfOwnStE/edit?usp=sharing The BatteryManager object should have a readonly property called chargingTime. The chargingTime attribute must be set to 0, if the battery is full or there is no battery attached to the system, and to the value positive Infinity if the battery is discharging, the implementation is unable to report the remaining charging time, or otherwise. Multiple Batteries. chargingTime. The chargingTime attribute can be set to the maximum charging time of the individual batteries if charging in parallel, and to the sum of the individual charging times if charging serially. -- This message was sent by Atlassian JIRA (v6.3.4#6332)