[jira] [Assigned] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov reassigned CB-5192: -- Assignee: Sergey Grebnov Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Assignee: Sergey Grebnov Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5192) Plugman engine check fails on Windows
Sergey Grebnov created CB-5192: -- Summary: Plugman engine check fails on Windows Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13803889#comment-13803889 ] Sergey Grebnov commented on CB-5192: Proposed solution 1. remove .bat extension from other script locations to be consistent - see cordova-wp8 above as an example, 2. Remove check for the file location on Windows before executing script since .exec or .spawn cmd /c will be able to run it just fine if(fs.existsSync(engine.scriptSrc)){ fs.chmodSync(engine.scriptSrc, '755'); var d = Q.defer(); child_process.exec(engine.scriptSrc, function(error, stdout, stderr) { Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov resolved CB-5192. Resolution: Fixed Assignee: (was: Sergey Grebnov) Fixed by pull request below. Please review and merge https://github.com/apache/cordova-plugman/pull/29 Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804041#comment-13804041 ] Piotr Zalewa commented on CB-4966: -- Design added - seems like it's ready for testing. Could someone help me with that? dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4714) Allow removing a plugin that is a dependency (using -f or -force flag)
[ https://issues.apache.org/jira/browse/CB-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804040#comment-13804040 ] Jonathan Bond-Caron commented on CB-4714: - Sorry keep pushing this back, back on cordova early next week. Allow removing a plugin that is a dependency (using -f or -force flag) -- Key: CB-4714 URL: https://issues.apache.org/jira/browse/CB-4714 Project: Apache Cordova Issue Type: Improvement Components: CLI, Plugman Affects Versions: 3.0.0 Environment: Windows 8 Reporter: Jonathan Bond-Caron Assignee: Braden Shepherdson Priority: Minor Labels: patch Fix For: 3.2.0 Some context: I wanted to start using the mobile spec app for cordova. The problem is I didn't know which dependencies were required for the application. So I created a plugin which just lists some dependencies: https://github.com/jbondc/cordova-plugin-mobile-spec cordova create test cordova platform add android cordova plugin list No plugins added. Use `cordova plugin add plugin`. cordova plugin add https://github.com/jbondc/cordova-plugin-mobile-spec cordova plugin list [ 'org.apache.cordova.core.battery-status', 'org.apache.cordova.core.camera', 'org.apache.cordova.core.device', 'org.apache.cordova.core.file', 'org.apache.cordova.core.media-capture', 'org.apache.cordova.core.mobile-spec' ] To test a modifications/patches to a specific plugin (media-capture), I wanted to do: cordova plugin rm org.apache.cordova.core.media-capture [Error: Another top-level plugin (org.apache.cordova.core.mobile-spec) relies on plugin org.apache.cordova.core.media-capture, therefore aborting uninstallation .] A lot of dependency management systems (freebsd ports, debian packages) allow you to forcefully remove a dependency. That's what I'm proposing: cordova plugin rm org.apache.cordova.core.media-capture -f cordova plugin list [ 'org.apache.cordova.core.battery-status', 'org.apache.cordova.core.camera', 'org.apache.cordova.core.device', 'org.apache.cordova.core.mobile-spec' ] cordova plugin add F:\Jonathan\GitHub\Cordova\cordova-plugin-media-capture cordova plugin list [ 'org.apache.cordova.core.battery-status', 'org.apache.cordova.core.camera', 'org.apache.cordova.core.device', 'org.apache.cordova.core.media-capture', 'org.apache.cordova.core.mobile-spec' ] It makes it easier to add/remove a plugin even if some dependencies are not met. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3205) orientation
[ https://issues.apache.org/jira/browse/CB-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804118#comment-13804118 ] Piotr Zalewa commented on CB-3205: -- https://github.com/zalun/cordova-plugin-device-orientation I need to add testing to it, but otherwise seems to work. orientation --- Key: CB-3205 URL: https://issues.apache.org/jira/browse/CB-3205 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: Herm Wong Assignee: Herm Wong -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804154#comment-13804154 ] Nic commented on CB-3020: - Hi All, Great to see the work done on this. I've been through all the comments here and can't get it working perfectly. Best I can do is a blink of black/accessorybar on first launch of keyboard, and from then on it's fine. This is really quite important for my project, so hope to get to the bottom of it. Where is this left? A plugin is coming in 3.2 which i've tried in 3.1 but to no avail. To me it seems like it attempts to hide the bar after it has been created but just isn't fast enough. I've even tried calling the keyboard up before I hide the splash just to remove the bar but of course the keyboard appears over the splash. So any help would be greatly appreciated. Many thanks Nic HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: bug, ios, ios6.1.3 Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804263#comment-13804263 ] Tom Wilson commented on CB-3020: I see the black box still show up in 3.1. It looks like the frame isn't being re-sized until after the keyboard animation is complete. Here is a post that might be related. http://stackoverflow.com/questions/18957476/ios-7-keyboard-animation They are mimicking the keyboard show animation and applying that same animation to re-sizing of the webview so that you don't get the black box. With the default 3.1 code my fixed headers were also getting repositioned when the keyboard was shown and atleast adding in the basic animation prevented this. I couldn't get the keyboard animation to work as expected but maybe someone else could? Tom HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: bug, ios, ios6.1.3 Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804269#comment-13804269 ] Daniel Roizman commented on CB-3020: Has anyone tried appgyver? They say the fetchnotes has added a plugin for hiding the keyboard and I'm curious if that works in ios7. Daniel Roizman CEO, Founder Hiyu gethiyu.com HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: bug, ios, ios6.1.3 Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson reopened CB-5192: Assignee: Braden Shepherdson It's not resolved until the code hits the Apache repos. I'll review and merge this today. Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Assignee: Braden Shepherdson Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5193) WebSQL on Android fails with multiple databases
[ https://issues.apache.org/jira/browse/CB-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804294#comment-13804294 ] ASF subversion and git services commented on CB-5193: - Commit bb08abc0b9fddc160d345de9479923bef5414015 in branch refs/heads/2.9.x from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=bb08abc ] CB-5193 Fix Android WebSQL sometime throwing SECURITY_ERR. Turns out our Quota logic has been wrong all along. If we were to actually track the quota needed, we'd need to store a map of dbName-quota for all dbNames. Instead, we just set a really high quota since we don't ever want to decline storage. I *think* this fixes all of the SECURITY_ERR exceptions we've been seeing. Even those on Honeycomb / ICS. (cherry picked from commit 6e4ef508e8f9f2d396515bd1d7465481d2f1285c) WebSQL on Android fails with multiple databases --- Key: CB-5193 URL: https://issues.apache.org/jira/browse/CB-5193 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Priority: Minor openDatabase() with two different names and the second one will fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5193) WebSQL on Android fails with multiple databases
[ https://issues.apache.org/jira/browse/CB-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804295#comment-13804295 ] ASF subversion and git services commented on CB-5193: - Commit 6e4ef508e8f9f2d396515bd1d7465481d2f1285c in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=6e4ef50 ] CB-5193 Fix Android WebSQL sometime throwing SECURITY_ERR. Turns out our Quota logic has been wrong all along. If we were to actually track the quota needed, we'd need to store a map of dbName-quota for all dbNames. Instead, we just set a really high quota since we don't ever want to decline storage. I *think* this fixes all of the SECURITY_ERR exceptions we've been seeing. Even those on Honeycomb / ICS. WebSQL on Android fails with multiple databases --- Key: CB-5193 URL: https://issues.apache.org/jira/browse/CB-5193 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Priority: Minor openDatabase() with two different names and the second one will fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5193) WebSQL on Android fails with multiple databases
[ https://issues.apache.org/jira/browse/CB-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804301#comment-13804301 ] Andrew Grieve commented on CB-5193: --- Note - I tested this on the 3.0 emulator, the 4.0.3 emulator, and my JB N7, and can no longer get a SECURITY_ERR to happen. Woohoo! WebSQL on Android fails with multiple databases --- Key: CB-5193 URL: https://issues.apache.org/jira/browse/CB-5193 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor Fix For: 3.2.0 openDatabase() with two different names and the second one will fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5193) WebSQL on Android fails with multiple databases
[ https://issues.apache.org/jira/browse/CB-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804286#comment-13804286 ] ASF subversion and git services commented on CB-5193: - Commit df4f86d88054b7026726a6c729a8c13d0a295d4e in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=df4f86d ] CB-5193 Update manual SQL test to open multiple databases and have a reload button WebSQL on Android fails with multiple databases --- Key: CB-5193 URL: https://issues.apache.org/jira/browse/CB-5193 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Andrew Grieve Priority: Minor openDatabase() with two different names and the second one will fail. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5194) Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified
Andre Asselin created CB-5194: - Summary: Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified Key: CB-5194 URL: https://issues.apache.org/jira/browse/CB-5194 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Galaxy S4 Reporter: Andre Asselin Priority: Minor Use Camera.getPicture() with sourceType: PHOTOLIBRARY to retrieve a picture from the library. The correctOrientation option will be ignored unless you also specify targetWidth/Height as options. The documentation doesn't state there is a dependency. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5195) Camera.getPicture with sourceType: PHOTOLIBRARY scales image before rotating
Andre Asselin created CB-5195: - Summary: Camera.getPicture with sourceType: PHOTOLIBRARY scales image before rotating Key: CB-5195 URL: https://issues.apache.org/jira/browse/CB-5195 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Galaxy S4 Reporter: Andre Asselin Use Camera.getPicture() with sourceType: PHOTOLIBRARY to retrieve a picture from the library. If you specify both the correctOrientation and targetWidth/Height options (which currently you must do if you want correctOrientation to work because of bug CB-5194), the code scales the image first before rotating it, so the final dimensions are incorrect. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5194) Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified
[ https://issues.apache.org/jira/browse/CB-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804326#comment-13804326 ] Andre Asselin commented on CB-5194: --- Note: Reading the source on github, I believe this is still a bug in the current version of the code. Camera.getPicture with sourceType: PHOTOLIBRARY doesn't respect correctOrientation unless targetWidth/Height also specified --- Key: CB-5194 URL: https://issues.apache.org/jira/browse/CB-5194 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.6.0 Environment: Galaxy S4 Reporter: Andre Asselin Priority: Minor Use Camera.getPicture() with sourceType: PHOTOLIBRARY to retrieve a picture from the library. The correctOrientation option will be ignored unless you also specify targetWidth/Height as options. The documentation doesn't state there is a dependency. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4760) Android Quirks should be documented for WebSQL
[ https://issues.apache.org/jira/browse/CB-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804330#comment-13804330 ] Andrew Grieve commented on CB-4760: --- CB-5193 Is now fixed, and with it, I think there are actually no quirks on Android. I still plan to update the docs, but there's no need to mention quirks now I think. Android Quirks should be documented for WebSQL -- Key: CB-4760 URL: https://issues.apache.org/jira/browse/CB-4760 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Andrew Grieve Apparently the WebSQL implementation is known broken on some Android devices. See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164 But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail See CB-4742, CB-3047 Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073 -- The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide. Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3020) HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it
[ https://issues.apache.org/jira/browse/CB-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804402#comment-13804402 ] Nic commented on CB-3020: - I've tried AppGyver Steroids, but they seem to retain their source code as part of their IP. Do you have a link to this keyboard reference? Thanks, Nic HideKeyboardFormAccessoryBar and KeyboardShrinksView show white bar instead of removing it -- Key: CB-3020 URL: https://issues.apache.org/jira/browse/CB-3020 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.6.0, 3.0.0 Environment: ios 6.1.3 Reporter: Horst Perfect Assignee: Shazron Abdullah Priority: Minor Labels: bug, ios, ios6.1.3 Fix For: 3.1.0 Attachments: Classes.zip, iOS Simulator Screen shot 2013-10-05 2.27.26 PM.png, iOS Simulator Screen shot 2013-10-05 2.27.36 PM.png, ios.zip I use phonegap 2.6 with the two new preferences HideKeyboardFormAccessoryBar KeyboardShrinksView set to true. Instead of the AccessoryBar a white bar appears ([screenshot|http://i.stack.imgur.com/3fgV8.png]). This is just happening when i set *both* of the preferences to true. When i just set the AccessoryBar preference to true the bar disappears as planned. Horst -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5115) On iOS 7, events are dispatched to wrong elements when taping an input field pops the virtual keyboard
[ https://issues.apache.org/jira/browse/CB-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804435#comment-13804435 ] Adrian Vasiliu commented on CB-5115: Thanks for the investigation. I have also reproduced a different variant of this misbehavior, which matches more closely the misbehavior that hurts hybrid apps using Dojo Mobile. For this new test case just as for the initial one, I have reproduced the issue with an iOS app using a UIWebView without Cordova (tested on Xcode 5 5A1413, Mac OS X 10.8.5). And for both the initial and the new test, the issue appears as a regression in iOS 7, since I don't reproduce when running on iOS 6. The root cause of the different misbehavior in these two tests might be the same, or might be different. In doubt, thinking you may want to add this second test case to a bug submission to Apple, let me describe the second test case: Same as my initially attached test_Cordova-pure-html.html but with the following slight CSS modification: {code} .msgArea { height: 100px; /* instead of a percentage */ /* remaining similar as in the initial test case */ } .clearButton { height: 30px; /* instead of a percentage */ /* remaining similar as in the initial test case */ } {code} With this slight modification, the behavior in iOS 7 is the following: 1/ when touching one of the input element on the top - above the area that will be covered by the virtual keyboard - the focus and click events are received by the correct element (the one you touched). 2/ when touching an input element on the bottom - inside the area covered by the keyboard as soon as it shows up - there is no event (thus, it is not focused and typing on the keyboard does not fill the input element). This differs from the behavior on iOS 7 of the initial test, which is that for any input element - placed inside or outside the area that will be covered by the keyboard - the events are received by the wrong element. Both tests do not have this problem on iOS 6. On iOS 7, events are dispatched to wrong elements when taping an input field pops the virtual keyboard -- Key: CB-5115 URL: https://issues.apache.org/jira/browse/CB-5115 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.1.0 Environment: iOS 7 Reporter: Adrian Vasiliu Attachments: test_Cordova-pure-html.html On iOS 7, when a Cordova 3.1 app contains input fields (input, textarea), the events such as focus and click can be dispatched to the wrong element when taping the field causes the virtual keyboard to show up. Apparently, the event dispatching mechanism is confused by the fact the page is pushed by the keyboard showing up: the events are dispatched to the element at the coordinate after the push, instead of the element at the coordinate of the initial tap gesture. Reproduced with Cordova 3.1 using Xcode 5.0 on Mac OS X 10.8.5, running on iPhone and iPad simulators and real devices. How to reproduce: Run on iOS 7 a Cordova 3.1 app using the code from the attached test file. The test contains several input elements, and a message area which displays a message for each focus and click events received by the input elements; the message includes the id of the element. When tapping an input element while the keyboard is not visible, the message shows that the event is received by wrong element. Also, the wrong input is focused. Differently, when the keyboard is already visible, the events are dispatched to the correct element. Notes: - Reproduced only when *not* using height:device-height in the meta tag, per the recommendation in the Cordova 3.1 doc (http://cordova.apache.org/docs/en/3.1.0/guide_platforms_ios_upgrading.md.html#Upgrading%20iOS). - Setting KeyboardShrinksView to either true or false in config.xml does not matter for this issue. - The same test code works fine in a pure webapp in Safari on iOS 7. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-5192. Resolution: Fixed Merged in. Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Assignee: Braden Shepherdson Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4918) [ios]status bar is overlapping with the view on iOS7
[ https://issues.apache.org/jira/browse/CB-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804474#comment-13804474 ] Timothy Joseph Duavis commented on CB-4918: --- The statusbar plugin does not seem to support when the App first starts in landscape mode. Can you confirm if this is a known bug? [ios]status bar is overlapping with the view on iOS7 Key: CB-4918 URL: https://issues.apache.org/jira/browse/CB-4918 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.0.0 Environment: xcode 5.0 ios 7.0 Reporter: lmnbeyond how to reproduce: don't hide status bar, and run mobile spec result: status bar is overlapping with the view on iOS7 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5192) Plugman engine check fails on Windows
[ https://issues.apache.org/jira/browse/CB-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1380#comment-1380 ] ASF subversion and git services commented on CB-5192: - Commit 5dd5091fa33679312e3c1a3bc748d9091503e9cd in branch refs/heads/master from [~sgrebnov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=5dd5091 ] CB-5192 Plugman engine check fails on Windows Plugman engine check fails on Windows - Key: CB-5192 URL: https://issues.apache.org/jira/browse/CB-5192 Project: Apache Cordova Issue Type: Bug Components: Plugman Environment: Windows Reporter: Sergey Grebnov Assignee: Braden Shepherdson Right now the simplest (and also the most correct IMO) way to specify plugin restrictions to specific cordova version is the following: plugin.xml: engines engine name=cordova version==2.7.0 / /engines But in this case as per plugman current implementation and engines definition(plugman/src/util/default-engines.js) plugman won't be able to resove script because on Windows the script named 'version.bat', not just 'version'. module.exports = function(project_dir){ return { 'cordova': { 'platform':'*', 'scriptSrc': path.join(project_dir,'cordova','version') }, - works in general, but NOT for WP7/8 ... 'cordova-wp8': { 'platform':'wp8', 'scriptSrc': path.join(project_dir,'cordova','version.bat') }, - correct location, not used in case of example above child_process.exec should correctly resolve this case (missing cmd file extension) but plugman check for file location so it fails to find it. This should affect all platforms which are supported on Windows and use .bat files (WP7/8, BlackBerry, Android) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5052) Andorid's media capture doesn't use ThreadPool
[ https://issues.apache.org/jira/browse/CB-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Billau updated CB-5052: Priority: Minor (was: Major) Andorid's media capture doesn't use ThreadPool -- Key: CB-5052 URL: https://issues.apache.org/jira/browse/CB-5052 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Capture Environment: Windows 7 Reporter: Mike Billau Assignee: David Kemp Priority: Minor From: http://stackoverflow.com/questions/19282318/phongap-capture-plugin-crashes-android Taking a picture with media-capture plugin will crash the app when the plugin returns from the camera app. Reproduced with Nexus 7 on 4.2, I used the simple Full Example from the docs. Got this in logcat: {noformat} I/ActivityManager( 476): Displayed com.google.android.gallery3d/com.android.camera.CameraActivity: +1s80ms W/IInputConnectionWrapper(31792): showStatusIcon on inactive InputConnection V/CAM_PhotoModule(29129): Preview size is 960x720 V/CAM_PhotoModule(29129): onShutterButtonClick: mCameraState=1 E/NvOmxCamera( 128): OMX_ERRORTYPE android::NvOmxCamera::getCameraStereoMode(NvxComponent*, NvOmxCameraUserStereoMode): Error: invalid NVX mode 0. E/NvOmxCamera( 128): OMX_ERRORTYPE android::NvOmxCamera::getCameraStereoModeAndCaptureInfo(NvxComponent*, NvOmxCameraUserStereoMode, NVX_STEREOCAPTUREINFO): getCameraStereoMode failed with 0x D/NvOsDebugPrintf( 128): NvMMLiteJPEGEncSetAttribute: Incorrect value 0 for stereo capture type E/NvOmxCameraSettings( 128): OMX_ERRORTYPE android::programStereoInfo(OMX_HANDLETYPE, const NVX_STEREOCAPTUREINFO, android::NvxWrappers*): pNvxWrappers-OMX_SetConfigIL failed with 0x80001005 V/CAM_PhotoModule(29129): mShutterToRawCallbackTime = 1381355622457ms V/CAM_PhotoModule(29129): mShutterLag = 422ms D/dalvikvm(29129): GC_FOR_ALLOC freed 679K, 15% free 1K/14236K, paused 27ms, total 28ms I/dalvikvm-heap(29129): Grow heap (frag case) to 13.063MB for 1036816-byte allocation D/NvOsDebugPrintf( 128): Tryproc: INBuffer-Values of Width and Height 1280 960 D/dalvikvm(29129): GC_FOR_ALLOC freed 1K, 14% free 13233K/15252K, paused 33ms, total 33ms V/CAM_PhotoModule(29129): mShutterToPostViewCallbackTime = 88ms V/CAM_PhotoModule(29129): mShutterToRawCallbackTime = 109ms V/CAM_PhotoModule(29129): mPictureDisplayedToJpegCallbackTime = 25ms D/CameraStorage(29129): External storage state=mounted V/CAM_PhotoModule(29129): mJpegCallbackFinishTime = 2ms I/MPL-storeload( 476): mpl state size = 5512 E/MPL-storeload( 476): calData from inv_save_mpl_states, size=2 I/MPL-storeload( 476): cal data size to write = 5512 I/MPL-storeload( 476): Bytes written = 5512 V/CAM_PhotoModule(29129): stopPreview D/( 128): Camera fd close (MI1040) E/NvOmxCamera( 128): Already called release() I/CameraClient( 128): Destroying camera 0 W/NvOmxCamera( 128): Already called release() D/MediaProvider(27296): object removed 2270 W/AudioFlinger( 128): session id 453 not found for pid 128 W/AudioFlinger( 128): session id 454 not found for pid 128 D/CordovaActivity(31792): Request code = 1 D/AndroidRuntime(31792): Shutting down VM W/dalvikvm(31792): threadid=1: thread exiting with uncaught exception (group=0x410ee930) E/AndroidRuntime(31792): FATAL EXCEPTION: main E/AndroidRuntime(31792): java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=1, result=-1, data=null} to activity {io.cordova.hellocordova/io.cordova.hellocordova.HelloCordova}: java.lang.IllegalStateException: Do not perform IO operations on the UI thread. Use Cordova Interface.getThreadPool() instead. E/AndroidRuntime(31792):at android.app.ActivityThread.deliverResults(ActivityThread.java:3319) E/AndroidRuntime(31792):at android.app.ActivityThread.handleSendResult(ActivityThread.java:3362) E/AndroidRuntime(31792):at android.app.ActivityThread.access$1100(ActivityThread.java:141) E/AndroidRuntime(31792):at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1282) E/AndroidRuntime(31792):at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime(31792):at android.os.Looper.loop(Looper.java:137) E/AndroidRuntime(31792):at android.app.ActivityThread.main(ActivityThread.java:5041) E/AndroidRuntime(31792):at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(31792):at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime(31792):at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793) E/AndroidRuntime(31792):at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
[jira] [Created] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
Mike Billau created CB-5196: --- Summary: BB10 invoke() plugin is shadowded by cordova.js Key: CB-5196 URL: https://issues.apache.org/jira/browse/CB-5196 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0 Environment: Blackberry 10 Reporter: Mike Billau Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to call any BB API, webworks.js needs to be included in the html file. The problem is that there does not seem to be a way to call invoke(): 1. Create a simple BB10 app using the attached HTML file, 2. Add feature to the config.xml: feature id=blackberry.invoke name=blackberry.invoke value=blackberry.invoke/ 3. Run the app. Press the button; the browser window doesn't open. 4. Edit the HTML file and place the cordova.js script before webworks.js script 5. Run the app again, and there is a popup saying: Error intializing cordova:undefined. After dismissing the alert, you can press the button and the browser opens just fine. Analysis: Internally blackberry.invoke.invoke() ('invoke' plugin) calls *window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where the problem is: *window.webworks* is defined in both cordova.js and webworks.js.The one in cordova.js doesn't have 'event' function whereas it is available in window.webworks of webworks.js. Hence when webworks.js is loaded after cordova.js, it works fine and not if it is reversed. Even though it works when we put webworks.js first we need to squash the alert() and make sure cordova initializes correctly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[ https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Billau updated CB-5196: Attachment: bbInvoke.html BB10 invoke() plugin is shadowded by cordova.js --- Key: CB-5196 URL: https://issues.apache.org/jira/browse/CB-5196 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0 Environment: Blackberry 10 Reporter: Mike Billau Attachments: bbInvoke.html Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to call any BB API, webworks.js needs to be included in the html file. The problem is that there does not seem to be a way to call invoke(): 1. Create a simple BB10 app using the attached HTML file, 2. Add feature to the config.xml: feature id=blackberry.invoke name=blackberry.invoke value=blackberry.invoke/ 3. Run the app. Press the button; the browser window doesn't open. 4. Edit the HTML file and place the cordova.js script before webworks.js script 5. Run the app again, and there is a popup saying: Error intializing cordova:undefined. After dismissing the alert, you can press the button and the browser opens just fine. Analysis: Internally blackberry.invoke.invoke() ('invoke' plugin) calls *window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where the problem is: *window.webworks* is defined in both cordova.js and webworks.js.The one in cordova.js doesn't have 'event' function whereas it is available in window.webworks of webworks.js. Hence when webworks.js is loaded after cordova.js, it works fine and not if it is reversed. Even though it works when we put webworks.js first we need to squash the alert() and make sure cordova initializes correctly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4345) [BlackBerry10] Improve error output for common failure scenarios
[ https://issues.apache.org/jira/browse/CB-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-4345. --- Resolution: Fixed Fix Version/s: (was: 3.2.0) 3.1.0 [BlackBerry10] Improve error output for common failure scenarios Key: CB-4345 URL: https://issues.apache.org/jira/browse/CB-4345 Project: Apache Cordova Issue Type: Improvement Components: BlackBerry Affects Versions: 3.0.0 Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 3.1.0 In general, we spew a lot of information out when a failure happens. The output should be more concise.Exact improvements needed TBD. The common things which throw off users are: - no signing key provided - build without run warns about debug token - run with no debug token (complains about author id mismatch) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CB-5186) onResume for CordovaActivity not propagated to plugins on startup.
[ https://issues.apache.org/jira/browse/CB-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804536#comment-13804536 ] Joe Bowser edited comment on CB-5186 at 10/24/13 6:53 PM: -- We don't want onResume to propagate to the plugins on start up because of the following reasons: 1. The plugins may not exist 2. The plugins should be cleanly initialized and don't need to know about onResume in this use case was (Author: bowserj): We don't want onResume to propogate to the plugins on start up because of the following reasons: 1. The plugins may not exist 2. The plugins should be cleanly initialized and don't need to know about onResume in this use case onResume for CordovaActivity not propagated to plugins on startup. -- Key: CB-5186 URL: https://issues.apache.org/jira/browse/CB-5186 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Reporter: James Stephenson Priority: Minor Why does CordovaActivity do the following? https://github.com/apache/cordova-android/blob/28c41294bba746c75beae0ab26a42c8412cc665a/framework/src/org/apache/cordova/CordovaActivity.java#L742 From a plugin's POV, it then becomes difficult to determine when the main activity initially starts up. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4620) spinnerStop causes java.lang.IllegalArgumentException: View not attached to window manager
[ https://issues.apache.org/jira/browse/CB-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-4620. Resolution: Implemented I'm going to say that this is implemented. I have no idea if this is fixed since I can't reproduce this on my end, but yeah, I at least give this a shot. spinnerStop causes java.lang.IllegalArgumentException: View not attached to window manager Key: CB-4620 URL: https://issues.apache.org/jira/browse/CB-4620 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.0.0 Environment: Android 4.1.1 Reporter: Clayton Grassick Assignee: Joe Bowser Occasionally, when a Cordova application is switched away from and then switched back to, it crashes with the following stack trace: java.lang.IllegalArgumentException: View not attached to window manager android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:378) android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:223) android.view.Window$LocalWindowManager.removeView(Window.java:432) android.app.Dialog.dismissDialog(Dialog.java:278) android.app.Dialog.access$000(Dialog.java:71) android.app.Dialog$1.run(Dialog.java:111) android.app.Dialog.dismiss(Dialog.java:268) org.apache.cordova.CordovaActivity.spinnerStop(CordovaActivity.java:812) org.apache.cordova.CordovaActivity.onMessage(CordovaActivity.java:1132) org.apache.cordova.PluginManager.postMessage(PluginManager.java:336) org.apache.cordova.CordovaWebView.postMessage(CordovaWebView.java:538) org.apache.cordova.CordovaWebViewClient$1$1.run(CordovaWebViewClient.java:311) android.os.Handler.handleCallback(Handler.java:587) android.os.Handler.dispatchMessage(Handler.java:92) android.os.Looper.loop(Looper.java:130) android.app.ActivityThread.main(ActivityThread.java:3687) java.lang.reflect.Method.invokeNative(Native Method) java.lang.reflect.Method.invoke(Method.java:507) com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867) com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625) dalvik.system.NativeStart.main(Native Method) It occurs approximately once per day per user, enough to flood ACRA with crash reports. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4760) Android Quirks should be documented for WebSQL
[ https://issues.apache.org/jira/browse/CB-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804558#comment-13804558 ] ASF subversion and git services commented on CB-4760: - Commit d27fff8b554007d8d39f0725afbdcdd8453acdab in branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=d27fff8 ] CB-4760 Remove docs for WebSQL and replace them with a Storage options overview. Android Quirks should be documented for WebSQL -- Key: CB-4760 URL: https://issues.apache.org/jira/browse/CB-4760 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Andrew Grieve Apparently the WebSQL implementation is known broken on some Android devices. See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164 But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail See CB-4742, CB-3047 Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073 -- The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide. Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4760) Android Quirks should be documented for WebSQL
[ https://issues.apache.org/jira/browse/CB-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-4760. --- Resolution: Fixed Android Quirks should be documented for WebSQL -- Key: CB-4760 URL: https://issues.apache.org/jira/browse/CB-4760 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Andrew Grieve Apparently the WebSQL implementation is known broken on some Android devices. See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164 But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail See CB-4742, CB-3047 Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073 -- The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide. Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Reopened] (CB-4760) Android Quirks should be documented for WebSQL
[ https://issues.apache.org/jira/browse/CB-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve reopened CB-4760: --- Android Quirks should be documented for WebSQL -- Key: CB-4760 URL: https://issues.apache.org/jira/browse/CB-4760 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Andrew Grieve Fix For: 3.2.0 Apparently the WebSQL implementation is known broken on some Android devices. See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164 But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail See CB-4742, CB-3047 Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073 -- The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide. Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4760) Android Quirks should be documented for WebSQL
[ https://issues.apache.org/jira/browse/CB-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve resolved CB-4760. --- Resolution: Fixed Fix Version/s: 3.2.0 Android Quirks should be documented for WebSQL -- Key: CB-4760 URL: https://issues.apache.org/jira/browse/CB-4760 Project: Apache Cordova Issue Type: Bug Components: Android, Docs Affects Versions: 2.9.0 Reporter: Peter Assignee: Andrew Grieve Fix For: 3.2.0 Apparently the WebSQL implementation is known broken on some Android devices. See https://issues.apache.org/jira/browse/CB-4742?focusedCommentId=13759164page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13759164 But the Cordova provided implementation also has some behaviours which cause mobile-spec storage.spec.18 to fail See CB-4742, CB-3047 Furthermore, the advice from Cordova dev is to just avoid using the WebSQL API See https://issues.apache.org/jira/browse/CB-3047?focusedCommentId=13633073page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13633073 -- The problem is that the Storage Guide documentation (http://cordova.apache.org/docs/en/3.0.0/cordova_storage_storage.md.html#Storage) currently doesn't mention any *Android Quirks* at all, so as far as user knows it should all work OK as per the API guide. Since (from above) there are known problems with the WebSQL API, and Cordova devs recommend to avoid using the WebSQL API, and the Cordova impl of WebSQL sometimes has unexpected behaviour, then all these should be documented as Android Quirks so the user is more aware of potential issues they will face. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5186) onResume for CordovaActivity not propagated to plugins on startup.
[ https://issues.apache.org/jira/browse/CB-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804561#comment-13804561 ] James Stephenson commented on CB-5186: -- So the sanctioned approach is to assume the plugin's constructor is, essentially, equivalent to onStart? onResume for CordovaActivity not propagated to plugins on startup. -- Key: CB-5186 URL: https://issues.apache.org/jira/browse/CB-5186 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Reporter: James Stephenson Priority: Minor Why does CordovaActivity do the following? https://github.com/apache/cordova-android/blob/28c41294bba746c75beae0ab26a42c8412cc665a/framework/src/org/apache/cordova/CordovaActivity.java#L742 From a plugin's POV, it then becomes difficult to determine when the main activity initially starts up. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4620) spinnerStop causes java.lang.IllegalArgumentException: View not attached to window manager
[ https://issues.apache.org/jira/browse/CB-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804576#comment-13804576 ] Clayton Grassick commented on CB-4620: -- I have not had the issue recur except on Android 2.3 since I patched. Since all of our current users are Android 4+, it's no longer a problem. I haven't tried on 3.1.0 as things are stable with the app at this point. spinnerStop causes java.lang.IllegalArgumentException: View not attached to window manager Key: CB-4620 URL: https://issues.apache.org/jira/browse/CB-4620 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.0.0 Environment: Android 4.1.1 Reporter: Clayton Grassick Assignee: Joe Bowser Occasionally, when a Cordova application is switched away from and then switched back to, it crashes with the following stack trace: java.lang.IllegalArgumentException: View not attached to window manager android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:378) android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:223) android.view.Window$LocalWindowManager.removeView(Window.java:432) android.app.Dialog.dismissDialog(Dialog.java:278) android.app.Dialog.access$000(Dialog.java:71) android.app.Dialog$1.run(Dialog.java:111) android.app.Dialog.dismiss(Dialog.java:268) org.apache.cordova.CordovaActivity.spinnerStop(CordovaActivity.java:812) org.apache.cordova.CordovaActivity.onMessage(CordovaActivity.java:1132) org.apache.cordova.PluginManager.postMessage(PluginManager.java:336) org.apache.cordova.CordovaWebView.postMessage(CordovaWebView.java:538) org.apache.cordova.CordovaWebViewClient$1$1.run(CordovaWebViewClient.java:311) android.os.Handler.handleCallback(Handler.java:587) android.os.Handler.dispatchMessage(Handler.java:92) android.os.Looper.loop(Looper.java:130) android.app.ActivityThread.main(ActivityThread.java:3687) java.lang.reflect.Method.invokeNative(Native Method) java.lang.reflect.Method.invoke(Method.java:507) com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867) com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625) dalvik.system.NativeStart.main(Native Method) It occurs approximately once per day per user, enough to flood ACRA with crash reports. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5186) onResume for CordovaActivity not propagated to plugins on startup.
[ https://issues.apache.org/jira/browse/CB-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804578#comment-13804578 ] Andrew Grieve commented on CB-5186: --- Slight clarification - You should use the initialize() method as your constructor since that's when you get a reference to the WebView. If you want your plugin to load when the app starts, use add param name=onload value=true / inside of your feature tag. onResume for CordovaActivity not propagated to plugins on startup. -- Key: CB-5186 URL: https://issues.apache.org/jira/browse/CB-5186 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Reporter: James Stephenson Priority: Minor Why does CordovaActivity do the following? https://github.com/apache/cordova-android/blob/28c41294bba746c75beae0ab26a42c8412cc665a/framework/src/org/apache/cordova/CordovaActivity.java#L742 From a plugin's POV, it then becomes difficult to determine when the main activity initially starts up. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[ https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804577#comment-13804577 ] Jeffrey Heifetz commented on CB-5196: - Use the cordova 3.0 compatible plugin - http://plugins.cordova.io/#/com.blackberry.invoke BB10 invoke() plugin is shadowded by cordova.js --- Key: CB-5196 URL: https://issues.apache.org/jira/browse/CB-5196 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0 Environment: Blackberry 10 Reporter: Mike Billau Attachments: bbInvoke.html Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to call any BB API, webworks.js needs to be included in the html file. The problem is that there does not seem to be a way to call invoke(): 1. Create a simple BB10 app using the attached HTML file, 2. Add feature to the config.xml: feature id=blackberry.invoke name=blackberry.invoke value=blackberry.invoke/ 3. Run the app. Press the button; the browser window doesn't open. 4. Edit the HTML file and place the cordova.js script before webworks.js script 5. Run the app again, and there is a popup saying: Error intializing cordova:undefined. After dismissing the alert, you can press the button and the browser opens just fine. Analysis: Internally blackberry.invoke.invoke() ('invoke' plugin) calls *window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where the problem is: *window.webworks* is defined in both cordova.js and webworks.js.The one in cordova.js doesn't have 'event' function whereas it is available in window.webworks of webworks.js. Hence when webworks.js is loaded after cordova.js, it works fine and not if it is reversed. Even though it works when we put webworks.js first we need to squash the alert() and make sure cordova initializes correctly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5187) cordova-cli on windows broken for compile, emulate, run
[ https://issues.apache.org/jira/browse/CB-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804586#comment-13804586 ] ASF subversion and git services commented on CB-5187: - Commit f76dfb80df6f605c69328a0ad33f5faea68a8751 in branch refs/heads/master from [~csantana] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=f76dfb8 ] CB-5187: remove unused var os_platform cordova-cli on windows broken for compile, emulate, run --- Key: CB-5187 URL: https://issues.apache.org/jira/browse/CB-5187 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: Master Reporter: Carlos Santana Assignee: Carlos Santana When running cordova-cli on windows is not taking the .bat in the scripts Steps to reproduce: On Windows run C:\Users\Carlos\Desktop node Z:\Documents\cordova\cordova-cli\bin\cordova create C:\Users\Carlos\Desktop\clispawn -d Creating a new cordova project with name HelloCordova and id io.cordova.hellocordova at location C:\Users\Carlos\Desktop\clispawn Using stock cordova hello-world application. cordova library for www already exists. No need to download. Continuing. Copying stock Cordova www assets into C:\Users\Carlos\Desktop\clispawn\www C:\Users\Carlos\Desktop cd .\clispawn C:\Users\Carlos\Desktop\clispawn node Z:\Documents\cordova\cordova-cli\bin\cordova platform add wp8 Downloading cordova library for wp8... Download complete Checking wp8 requirements... Creating wp8 project... Preparing wp8 project C:\Users\Carlos\Desktop\clispawn node Z:\Documents\cordova\cordova-cli\bin\cordova build -d cordova library for wp8 already exists. No need to download. Continuing. Generating config.xml from defaults for platform wp8 Calling plugman.prepare for platform wp8 Preparing wp8 project Processing configuration changes for plugins. Iterating over installed plugins: [] Writing out cordova_plugins.js... Compiling app on platform wp8 via command C:\Users\Carlos\Desktop\clispawn\platforms\wp8\cordova\build Error: spawn ENOENT at errnoException (child_process.js:980:11) at Process.ChildProcess._handle.onexit (child_process.js:771:34) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[ https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804577#comment-13804577 ] Jeffrey Heifetz edited comment on CB-5196 at 10/24/13 7:27 PM: --- Use the cordova 3.0 compatible plugin - http://plugins.cordova.io/#/com.blackberry.invoke If you do this the balckberry.invoke APIs will be added automatically no modification to the framework or config.xml should be necessary was (Author: jeffheifetz): Use the cordova 3.0 compatible plugin - http://plugins.cordova.io/#/com.blackberry.invoke BB10 invoke() plugin is shadowded by cordova.js --- Key: CB-5196 URL: https://issues.apache.org/jira/browse/CB-5196 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.1.0 Environment: Blackberry 10 Reporter: Mike Billau Attachments: bbInvoke.html Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to call any BB API, webworks.js needs to be included in the html file. The problem is that there does not seem to be a way to call invoke(): 1. Create a simple BB10 app using the attached HTML file, 2. Add feature to the config.xml: feature id=blackberry.invoke name=blackberry.invoke value=blackberry.invoke/ 3. Run the app. Press the button; the browser window doesn't open. 4. Edit the HTML file and place the cordova.js script before webworks.js script 5. Run the app again, and there is a popup saying: Error intializing cordova:undefined. After dismissing the alert, you can press the button and the browser opens just fine. Analysis: Internally blackberry.invoke.invoke() ('invoke' plugin) calls *window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where the problem is: *window.webworks* is defined in both cordova.js and webworks.js.The one in cordova.js doesn't have 'event' function whereas it is available in window.webworks of webworks.js. Hence when webworks.js is loaded after cordova.js, it works fine and not if it is reversed. Even though it works when we put webworks.js first we need to squash the alert() and make sure cordova initializes correctly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5186) onResume for CordovaActivity not propagated to plugins on startup.
[ https://issues.apache.org/jira/browse/CB-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804587#comment-13804587 ] Joe Bowser commented on CB-5186: [~agrieve] Good point. I completely forgot about the initialize method. onResume for CordovaActivity not propagated to plugins on startup. -- Key: CB-5186 URL: https://issues.apache.org/jira/browse/CB-5186 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.1.0 Reporter: James Stephenson Priority: Minor Why does CordovaActivity do the following? https://github.com/apache/cordova-android/blob/28c41294bba746c75beae0ab26a42c8412cc665a/framework/src/org/apache/cordova/CordovaActivity.java#L742 From a plugin's POV, it then becomes difficult to determine when the main activity initially starts up. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5187) cordova-cli on windows broken for compile, emulate, run
[ https://issues.apache.org/jira/browse/CB-5187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Santana resolved CB-5187. Resolution: Fixed Fix Version/s: 3.2.0 cordova-cli on windows broken for compile, emulate, run --- Key: CB-5187 URL: https://issues.apache.org/jira/browse/CB-5187 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: Master Reporter: Carlos Santana Assignee: Carlos Santana Fix For: 3.2.0 When running cordova-cli on windows is not taking the .bat in the scripts Steps to reproduce: On Windows run C:\Users\Carlos\Desktop node Z:\Documents\cordova\cordova-cli\bin\cordova create C:\Users\Carlos\Desktop\clispawn -d Creating a new cordova project with name HelloCordova and id io.cordova.hellocordova at location C:\Users\Carlos\Desktop\clispawn Using stock cordova hello-world application. cordova library for www already exists. No need to download. Continuing. Copying stock Cordova www assets into C:\Users\Carlos\Desktop\clispawn\www C:\Users\Carlos\Desktop cd .\clispawn C:\Users\Carlos\Desktop\clispawn node Z:\Documents\cordova\cordova-cli\bin\cordova platform add wp8 Downloading cordova library for wp8... Download complete Checking wp8 requirements... Creating wp8 project... Preparing wp8 project C:\Users\Carlos\Desktop\clispawn node Z:\Documents\cordova\cordova-cli\bin\cordova build -d cordova library for wp8 already exists. No need to download. Continuing. Generating config.xml from defaults for platform wp8 Calling plugman.prepare for platform wp8 Preparing wp8 project Processing configuration changes for plugins. Iterating over installed plugins: [] Writing out cordova_plugins.js... Compiling app on platform wp8 via command C:\Users\Carlos\Desktop\clispawn\platforms\wp8\cordova\build Error: spawn ENOENT at errnoException (child_process.js:980:11) at Process.ChildProcess._handle.onexit (child_process.js:771:34) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5129) Cordova File Entry objects (FileEntry, DirectoryEntry) should have a filesystem attribute
[ https://issues.apache.org/jira/browse/CB-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland resolved CB-5129. -- Resolution: Fixed Fix Version/s: 3.2.0 Cordova File Entry objects (FileEntry, DirectoryEntry) should have a filesystem attribute - Key: CB-5129 URL: https://issues.apache.org/jira/browse/CB-5129 Project: Apache Cordova Issue Type: Bug Components: Plugin File Affects Versions: 3.1.0 Reporter: Ian Clelland Assignee: Ian Clelland Fix For: 3.2.0 According to the [spec|http://www.w3.org/TR/file-system-api/#idl-def-Entry], objects derived from Entry should have a {{filesystem}} attribute, which points to the FileSystem object from whence they came. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804647#comment-13804647 ] Anis Kadri commented on CB-5198: I completely favor solution number 2. I think it makes the most sense in my opinion. Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-566) Add manual tests for all Capture APIs and reorganize audio tests
[ https://issues.apache.org/jira/browse/CB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-566: Assignee: (was: Filip Maj) Add manual tests for all Capture APIs and reorganize audio tests Key: CB-566 URL: https://issues.apache.org/jira/browse/CB-566 Project: Apache Cordova Issue Type: Test Components: mobile-spec Affects Versions: 1.6.1 Reporter: Filip Maj Fix For: 3.3.0 Currently we do not have manual tests for using the capture API to capture an image, audio and video. Also, we should reorganize the audio manual tests. These should be renamed to media. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-566) Add manual tests for all Capture APIs and reorganize audio tests
[ https://issues.apache.org/jira/browse/CB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-566: Fix Version/s: 3.3.0 Add manual tests for all Capture APIs and reorganize audio tests Key: CB-566 URL: https://issues.apache.org/jira/browse/CB-566 Project: Apache Cordova Issue Type: Test Components: mobile-spec Affects Versions: 1.6.1 Reporter: Filip Maj Fix For: 3.3.0 Currently we do not have manual tests for using the capture API to capture an image, audio and video. Also, we should reorganize the audio manual tests. These should be renamed to media. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-566) Add manual tests for all Capture APIs and reorganize audio tests
[ https://issues.apache.org/jira/browse/CB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804684#comment-13804684 ] Shazron Abdullah commented on CB-566: - Encountered this one when backporting for 2.9.1. We should add this sorely needed manual test for 3.3.0, I'll take this one. Add manual tests for all Capture APIs and reorganize audio tests Key: CB-566 URL: https://issues.apache.org/jira/browse/CB-566 Project: Apache Cordova Issue Type: Test Components: mobile-spec Affects Versions: 1.6.1 Reporter: Filip Maj Fix For: 3.3.0 Currently we do not have manual tests for using the capture API to capture an image, audio and video. Also, we should reorganize the audio manual tests. These should be renamed to media. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-566) Add manual tests for all Capture APIs and reorganize audio tests
[ https://issues.apache.org/jira/browse/CB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-566: --- Assignee: Shazron Abdullah Add manual tests for all Capture APIs and reorganize audio tests Key: CB-566 URL: https://issues.apache.org/jira/browse/CB-566 Project: Apache Cordova Issue Type: Test Components: mobile-spec Affects Versions: 1.6.1 Reporter: Filip Maj Assignee: Shazron Abdullah Fix For: 3.3.0 Currently we do not have manual tests for using the capture API to capture an image, audio and video. Also, we should reorganize the audio manual tests. These should be renamed to media. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5189) iOS Backport for 2.9.1
[ https://issues.apache.org/jira/browse/CB-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804710#comment-13804710 ] Shazron Abdullah commented on CB-5189: -- AutoTests: === iOS 7.0.3 (all pass) iOS 6.1.4 (all pass) Manual Tests (iOS 6.1.4) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass - but got a multiple loadstart events (2) popup error each time a page was loaded - I think this the test is causing this) Accelerometer (pass) Camera (pass) Media Capture Audio (pass) Manual Tests (iOS 7.0.3) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass) Accelerometer (pass) Camera (pass) Media Capture Audio (pass, but UI is shifted up a bit, instead of sticking to the bottom, un-related to recording) iOS Backport for 2.9.1 -- Key: CB-5189 URL: https://issues.apache.org/jira/browse/CB-5189 Project: Apache Cordova Issue Type: Sub-task Components: iOS, Plugin Camera, Plugin Device Motion, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin SplashScreen Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 2.9.1 --1. CB-4958, CB-3482, CB-3453 (Camera - iOS 7, among others)-- --2. CB-4930 (InAppBrowser - iOS 7)-- --3. CB-4847 (Media/Media Capture - iOS 7)-- --4. CB-4825 (Device Motion)-- --5. CB-5035 (Device Motion)-- --6. CB-4806, CB-4355 (Splashscreen - iOS 7)-- --7. Add CoreMotion.framework to the default template-- 8. Fix warnings/update default template to Xcode 5 settings -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5199) Media Capture - UI issues under iOS 7
Shazron Abdullah created CB-5199: Summary: Media Capture - UI issues under iOS 7 Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Fix For: 3.2.0 See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5199: - Attachment: CaptureVideo.PNG CaptureImage.PNG CaptureAudio.PNG Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5199: - Description: See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) was: See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden (see Camera plugin, where this is fixed) Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804741#comment-13804741 ] Steve Gill commented on CB-5198: Looks like cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 doesn't work with cordova 3.0.0. We must have added it in later. Actually, cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 doesn't work with cordova 3.0.10 but cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#r0.3.3 does. We must have changed something with plugins from the 3.0.0 tag to r0.3.3 tag. Haven't bothered investigating further. Something worth backporting? Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804742#comment-13804742 ] Shazron Abdullah commented on CB-5199: -- The Image and Video captures are a quick patch: {code} // add in CDVImagePicker implementation - (BOOL)prefersStatusBarHidden { return YES; } - (UIViewController*)childViewControllerForStatusBarHidden { return nil; } - (void)viewWillAppear:(BOOL)animated { SEL sel = NSSelectorFromString(@setNeedsStatusBarAppearanceUpdate); if ([self respondsToSelector:sel]) { [self performSelector:sel withObject:nil afterDelay:0]; } [super viewWillAppear:animated]; } {code} For the Audio capture, from closer inspection it appears the whole view goes *under* the toolbar and the statusbar. Notice the timer label is missing. Also, the bottom empty area corresponds to the toolbar+statusbar height. Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (CB-5155) [Release + 3.2.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill reassigned CB-5155: -- Assignee: Steve Gill (was: Jesse MacFadyen) [Release + 3.2.0] Parent Issue -- Key: CB-5155 URL: https://issues.apache.org/jira/browse/CB-5155 Project: Apache Cordova Issue Type: Task Components: Android, App Hello World, BlackBerry, CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Windows 8, WP8 Reporter: Steve Gill Assignee: Steve Gill Fix For: 3.2.0 Parent bug for the 3.2.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.1#6144)
[jira] [Commented] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804766#comment-13804766 ] Shazron Abdullah commented on CB-5199: -- For Capture Audio, patch the loadView function in CDVAudioRecorderViewController, add this at the start: {code} if ([self respondsToSelector:@selector(edgesForExtendedLayout)]) { self.edgesForExtendedLayout = UIRectEdgeNone; } {code} Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804765#comment-13804765 ] ASF subversion and git services commented on CB-5199: - Commit 7e6ad2e6beb7511398139529cc74f5ebd7169430 in branch refs/heads/2.9.x from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=7e6ad2e ] CB-5199 - Media Capture - UI issues under iOS 7 (uncrustify style fix-ups as well) Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5199) Media Capture - UI issues under iOS 7
[ https://issues.apache.org/jira/browse/CB-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-5199. -- Resolution: Fixed Media Capture - UI issues under iOS 7 - Key: CB-5199 URL: https://issues.apache.org/jira/browse/CB-5199 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: Master Reporter: Shazron Abdullah Labels: ios7 Fix For: 3.2.0 Attachments: CaptureAudio.PNG, CaptureImage.PNG, CaptureVideo.PNG See attached screenshots. 1. Capture Audio - the microphone and record bar should stick to the bottom, right now it is shifted to the middle 2. Capture Video - the statusbar should be hidden (see Camera plugin, where this is fixed) 3. Capture Image - the statusbar should be hidden, you can see the battery status (see Camera plugin, where this is fixed) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CB-5189) iOS Backport for 2.9.1
[ https://issues.apache.org/jira/browse/CB-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804710#comment-13804710 ] Shazron Abdullah edited comment on CB-5189 at 10/24/13 10:45 PM: - AutoTests: === iOS 7.0.3 (all pass) iOS 6.1.4 (all pass) Manual Tests (iOS 6.1.4) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass - but got a multiple loadstart events (2) popup error each time a page was loaded - I think this the test is causing this) Accelerometer (pass) Camera (pass) Media Capture Audio (pass) Manual Tests (iOS 7.0.3) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass) Accelerometer (pass) Camera (pass) Media Capture Audio (pass --, but UI is shifted up a bit, instead of sticking to the bottom, un-related to recording - fixed in CB-5199--) was (Author: shazron): AutoTests: === iOS 7.0.3 (all pass) iOS 6.1.4 (all pass) Manual Tests (iOS 6.1.4) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass - but got a multiple loadstart events (2) popup error each time a page was loaded - I think this the test is causing this) Accelerometer (pass) Camera (pass) Media Capture Audio (pass) Manual Tests (iOS 7.0.3) === Media Record (pass) Splashscreen (pass) InAppBrowser (pass) Accelerometer (pass) Camera (pass) Media Capture Audio (pass, but UI is shifted up a bit, instead of sticking to the bottom, un-related to recording) iOS Backport for 2.9.1 -- Key: CB-5189 URL: https://issues.apache.org/jira/browse/CB-5189 Project: Apache Cordova Issue Type: Sub-task Components: iOS, Plugin Camera, Plugin Device Motion, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin SplashScreen Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 2.9.1 --1. CB-4958, CB-3482, CB-3453 (Camera - iOS 7, among others)-- --2. CB-4930 (InAppBrowser - iOS 7)-- --3. CB-4847 (Media/Media Capture - iOS 7)-- --4. CB-4825 (Device Motion)-- --5. CB-5035 (Device Motion)-- --6. CB-4806, CB-4355 (Splashscreen - iOS 7)-- --7. Add CoreMotion.framework to the default template-- 8. Fix warnings/update default template to Xcode 5 settings --9. CB-5199 (Media Capture - iOS 7)-- -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-3205) orientation
[ https://issues.apache.org/jira/browse/CB-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill resolved CB-3205. Resolution: Fixed I tested this on my device using cordova-mobile-spec. All tests pass. I have merged this into dev branch and it will be out for the next plugins release orientation --- Key: CB-3205 URL: https://issues.apache.org/jira/browse/CB-3205 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: Herm Wong Assignee: Herm Wong -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804817#comment-13804817 ] Steve Gill commented on CB-4966: This plugin is causing device ready not to fire on ffos. I haven't debugged it. Needs more work dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804887#comment-13804887 ] Steve Gill commented on CB-5198: Just to add to the discussion, our current master branch is already using the registry for dependencies. So this means that people using cordova 3.0 should already be facing this problem. Surprised it hasn't been reported. Maybe most people have upgraded to 3.1? Anyways, i suggest this not be a blocker for the plugin release. After the release, maybe we spend some time backporting the git ref stuff to cordova 3.0? Then we change the 3.0 docs to download using refs effectively killing our reliance on master. Maybe we just add a note on the 3.0.0 docs that they should seriously upgrade! I don't know. Thoughts? Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5201) Scrolling artifacts android
Vunda Von created CB-5201: - Summary: Scrolling artifacts android Key: CB-5201 URL: https://issues.apache.org/jira/browse/CB-5201 Project: Apache Cordova Issue Type: Bug Components: Android Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli Reporter: Vunda Von Fix For: 3.1.0 Real simple example here with a long list of items. As you scroll, you'll notice that the items are blank at either end you are scrolling towards. On a larger list with pictures and text, you can see so much tearing and tiling as you scroll. This does not happen in chrome web browser, only cordova apps. {code} !DOCTYPE html html head titleFoo/title /head body divHeader/div ul id=foo style=height:300px; overflow:auto; /ul divFooter/div script for(var i=0; i 1000; i++){ var foo = document.createElement('li'); foo.innerHTML = i; document.getElementById('foo').appendChild(foo); } /script /body /html {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5201) Scrolling produces artifacts on android
[ https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vunda Von updated CB-5201: -- Summary: Scrolling produces artifacts on android (was: Scrolling artifacts android) Scrolling produces artifacts on android --- Key: CB-5201 URL: https://issues.apache.org/jira/browse/CB-5201 Project: Apache Cordova Issue Type: Bug Components: Android Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli Reporter: Vunda Von Fix For: 3.1.0 Real simple example here with a long list of items. As you scroll, you'll notice that the items are blank at either end you are scrolling towards. On a larger list with pictures and text, you can see so much tearing and tiling as you scroll. This does not happen in chrome web browser, only cordova apps. {code} !DOCTYPE html html head titleFoo/title /head body divHeader/div ul id=foo style=height:300px; overflow:auto; /ul divFooter/div script for(var i=0; i 1000; i++){ var foo = document.createElement('li'); foo.innerHTML = i; document.getElementById('foo').appendChild(foo); } /script /body /html {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[ https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805042#comment-13805042 ] Vunda Von commented on CB-5201: --- Another example with images to show the tearing as you scroll: {code} !DOCTYPE html html head titleFoo/title style *{ padding: 0; margin: 0; } img{ max-width: 100% } #foo{ width: 100%; height: 300px; overflow: auto; } /style /head body divHeader/div ul id=foo /ul divFooter/div script for(var i=0; i 1000; i++){ var foo = document.createElement('li'); foo.innerHTML = i + ' img src=https://www.google.com/images/srpr/logo11w.png/ '; document.getElementById('foo').appendChild(foo); } /script /body /html {code} Scrolling produces artifacts on android --- Key: CB-5201 URL: https://issues.apache.org/jira/browse/CB-5201 Project: Apache Cordova Issue Type: Bug Components: Android Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli Reporter: Vunda Von Fix For: 3.1.0 Real simple example here with a long list of items. As you scroll, you'll notice that the items are blank at either end you are scrolling towards. On a larger list with pictures and text, you can see so much tearing and tiling as you scroll. This does not happen in chrome web browser, only cordova apps. {code} !DOCTYPE html html head titleFoo/title /head body divHeader/div ul id=foo style=height:300px; overflow:auto; /ul divFooter/div script for(var i=0; i 1000; i++){ var foo = document.createElement('li'); foo.innerHTML = i; document.getElementById('foo').appendChild(foo); } /script /body /html {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-5201) Scrolling produces artifacts on android
[ https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vunda Von updated CB-5201: -- Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli, android:hardwareAccelerated=true (was: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli) Scrolling produces artifacts on android --- Key: CB-5201 URL: https://issues.apache.org/jira/browse/CB-5201 Project: Apache Cordova Issue Type: Bug Components: Android Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli, android:hardwareAccelerated=true Reporter: Vunda Von Fix For: 3.1.0 Real simple example here with a long list of items. As you scroll, you'll notice that the items are blank at either end you are scrolling towards. On a larger list with pictures and text, you can see so much tearing and tiling as you scroll. This does not happen in chrome web browser, only cordova apps. {code} !DOCTYPE html html head titleFoo/title /head body divHeader/div ul id=foo style=height:300px; overflow:auto; /ul divFooter/div script for(var i=0; i 1000; i++){ var foo = document.createElement('li'); foo.innerHTML = i; document.getElementById('foo').appendChild(foo); } /script /body /html {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5202) Android Video Capture crashes app on 4.3
Tom Saunders created CB-5202: Summary: Android Video Capture crashes app on 4.3 Key: CB-5202 URL: https://issues.apache.org/jira/browse/CB-5202 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Capture Affects Versions: 3.0.0 Environment: Android 4.3 Reporter: Tom Saunders Priority: Critical Using the cordova video capture plugin crashes the application when returning from the capture video intent. No data is returned. This is a known issue with Android 4.3, the workaround is to explicitly specify a location for saving the video Relevant stackoverflows: http://stackoverflow.com/questions/18472953/video-capture-in-android-4-3-using-camera-app-intent http://stackoverflow.com/questions/18120775/android-android-provider-mediastore-action-video-capture-return-null-onactivityr -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5054) cordova-plugin-media-capture crash on wp8
[ https://issues.apache.org/jira/browse/CB-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805053#comment-13805053 ] Tom Saunders commented on CB-5054: -- I ran into this problem as well. I assume it started when all the plugins were separated... the correct path is now something like /Plugins/org.apache./AudioRecorder.xaml cordova-plugin-media-capture crash on wp8 -- Key: CB-5054 URL: https://issues.apache.org/jira/browse/CB-5054 Project: Apache Cordova Issue Type: Bug Components: Plugin Media Capture Affects Versions: 3.0.0 Environment: wp8+vs2012 Reporter: TianBo Yang Priority: Critical Labels: cordova-plugin-media-capture, wp8 1.use Cordova CLI create WP8 template project, add plugin cordova-plugin-media-capture. 2.then add the captureAudio Example.html(http://cordova.apache.org/docs/en/3.0.0/cordova_media_capture_capture.md.html#Capture) when i run this project, click CaptureAudio there is a carsh. i debug in vs2012,there is the exception log! stackTrace: at System.Windows.Navigation.NavigationService.Navigate(Uri source) uri: {./CordovaLib/UI/AudioRecorder.xaml?dummy=bc51b4bf-8798-46ee-a2a6-cad51bd23401} exception msg: Navigation is only supported to relative URIs that are fragments, or begin with '/', or which contain ';component/'. Parameter name: uri it's also crash, when excute CaptureVideo ! there is the crash reason caused crash, bad navigate uri. AudioCaptureTask.cs line 79 root.Navigate(new System.Uri(baseUrl + CordovaLib/UI/AudioRecorder.xaml?dummy= + Guid.NewGuid().ToString(), UriKind.Relative)); VideoCaptureTask.cs line 79. root.Navigate(new System.Uri(baseUrl + CordovaLib/UI/VideoRecorder.xaml?dummy= + Guid.NewGuid().ToString(), UriKind.Relative)); -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5202) Android Video Capture crashes app on 4.3
[ https://issues.apache.org/jira/browse/CB-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805054#comment-13805054 ] Tom Saunders commented on CB-5202: -- E/AndroidRuntime( 6464): FATAL EXCEPTION: main E/AndroidRuntime( 6464): java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=2, result=-1, data=Intent { }} to activity {com.noggin.oca/com.noggin.oca.OCApp}: java.lang.NullPointerException E/AndroidRuntime( 6464): at android.app.ActivityThread.deliverResults(ActivityThread.java:3367) E/AndroidRuntime( 6464): at android.app.ActivityThread.handleSendResult(ActivityThread.java:3410) E/AndroidRuntime( 6464): at android.app.ActivityThread.access$1100(ActivityThread.java:141) E/AndroidRuntime( 6464): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1304) E/AndroidRuntime( 6464): at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime( 6464): at android.os.Looper.loop(Looper.java:137) E/AndroidRuntime( 6464): at android.app.ActivityThread.main(ActivityThread.java:5103) E/AndroidRuntime( 6464): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime( 6464): at java.lang.reflect.Method.invoke(Method.java:525) E/AndroidRuntime( 6464): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) E/AndroidRuntime( 6464): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) E/AndroidRuntime( 6464): at dalvik.system.NativeStart.main(Native Method) E/AndroidRuntime( 6464): Caused by: java.lang.NullPointerException E/AndroidRuntime( 6464): at org.apache.cordova.FileHelper.getRealPath(FileHelper.java:84) E/AndroidRuntime( 6464): at org.apache.cordova.core.Capture.createMediaFile(Capture.java:353) E/AndroidRuntime( 6464): at org.apache.cordova.core.Capture.onActivityResult(Capture.java:310) E/AndroidRuntime( 6464): at org.apache.cordova.CordovaActivity.onActivityResult(CordovaActivity.java:882) E/AndroidRuntime( 6464): at android.app.Activity.dispatchActivityResult(Activity.java:5322) E/AndroidRuntime( 6464): at android.app.ActivityThread.deliverResults(ActivityThread.java:3363) E/AndroidRuntime( 6464): ... 11 more W/ActivityManager( 534): Force finishing activity com.noggin.oca/.OCApp Android Video Capture crashes app on 4.3 Key: CB-5202 URL: https://issues.apache.org/jira/browse/CB-5202 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Media Capture Affects Versions: 3.0.0 Environment: Android 4.3 Reporter: Tom Saunders Priority: Critical Using the cordova video capture plugin crashes the application when returning from the capture video intent. No data is returned. This is a known issue with Android 4.3, the workaround is to explicitly specify a location for saving the video Relevant stackoverflows: http://stackoverflow.com/questions/18472953/video-capture-in-android-4-3-using-camera-app-intent http://stackoverflow.com/questions/18120775/android-android-provider-mediastore-action-video-capture-return-null-onactivityr -- This message was sent by Atlassian JIRA (v6.1#6144)