[jira] [Commented] (CB-3451) iOS Cordova app crashes with "failed to resume in time" when reopening
[ https://issues.apache.org/jira/browse/CB-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666033#comment-13666033 ] Brendan commented on CB-3451: - I have no restore handler setup. window.onload mainly sets up the ondeviceready handler. The ondeviceready handler does kick off some asset retrieval: the streaming of mp3 audio, loading some web audio assets, and creating some canvas objects. As the app runs, more of these assets are loaded and discarded from time to time. Upon restoration, does window.onload or ondeviceready fire again? From what I can tell they aren't. > iOS Cordova app crashes with "failed to resume in time" when reopening > -- > > Key: CB-3451 > URL: https://issues.apache.org/jira/browse/CB-3451 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 > Environment: Running on iPhone 5 >Reporter: Brendan >Assignee: Shazron Abdullah > Fix For: 2.8.0 > > > I have a Cordova 2.6.0 app that runs well on my iPhone 5. It uses web audio > and canvas, it that's relevant. When I reopen the app, it sometimes restores > fine, but often it crashes, and the crash log indicates "failed to resume in > time". I can share an entire crash log if useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3063) localStorage not persistent on Samsung Galaxy S3, maybe others
[ https://issues.apache.org/jira/browse/CB-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666012#comment-13666012 ] Matthew Eno commented on CB-3063: - Yep, it's all working now. > localStorage not persistent on Samsung Galaxy S3, maybe others > -- > > Key: CB-3063 > URL: https://issues.apache.org/jira/browse/CB-3063 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.6.0 > Environment: App running Jquery 2.0 beta, Jquery Mobile 1.3, > RequireJS, UnderscoreJS, BackboneJS and Phonegap/Cordova 2.6.0. Samsung > Galaxy S3 JellyBean (4.1.2) >Reporter: Sindre Haaland >Assignee: Joe Bowser > Labels: android, localStorage > Attachments: index.html > > > After upgrading from Phonegap 2.5.0 to Phonegap 2.6.0 localStorage stopped > working. setting and getting items from localStorage works when the app is in > memory. One can go to the home screen and start the application again, but > when it is completely closed the data from localStorage is lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3063) localStorage not persistent on Samsung Galaxy S3, maybe others
[ https://issues.apache.org/jira/browse/CB-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666005#comment-13666005 ] aaron triant commented on CB-3063: -- Matthew, im experiencing the same problem with 2.6. Are you able to let us know if using the latest (2.7) resolved your problem? > localStorage not persistent on Samsung Galaxy S3, maybe others > -- > > Key: CB-3063 > URL: https://issues.apache.org/jira/browse/CB-3063 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.6.0 > Environment: App running Jquery 2.0 beta, Jquery Mobile 1.3, > RequireJS, UnderscoreJS, BackboneJS and Phonegap/Cordova 2.6.0. Samsung > Galaxy S3 JellyBean (4.1.2) >Reporter: Sindre Haaland >Assignee: Joe Bowser > Labels: android, localStorage > Attachments: index.html > > > After upgrading from Phonegap 2.5.0 to Phonegap 2.6.0 localStorage stopped > working. setting and getting items from localStorage works when the app is in > memory. One can go to the home screen and start the application again, but > when it is completely closed the data from localStorage is lost. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3494) Enable script debugging
[ https://issues.apache.org/jira/browse/CB-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665994#comment-13665994 ] Martin Naumann commented on CB-3494: [~purplecabbage] Sorry, it's been a long day but I'd like to contribute to Weinre. Edited the issue to make it clearer. It may be non-trivial, but the tools should be there. WebInspector, for example, contains the "Scripts" panel and hints to a Javascript Debugger, which isn't enabled. Sure there is the Safari debugger and sure for Chrome on Android there is remote web debugging - but why not have it in Weinre? I basically want the ability to set/unset breakpoints and if I'm really lucky watch expressions, scope etc. [~pmuellr] The joys of open source. I digged into the code, found the DebuggerModel, DebuggerDispatcher, some hints in vendor/webkit/WebCore/inspector/InjectedScriptHost.idl and the hidden "Scripts" Panel. For there I started trying. Aardwolf would be a good starting point and seeing that Chrome on Android has a debugger protocol (https://developers.google.com/chrome-developer-tools/docs/debugger-protocol) I think there's some development in this direction, so maybe it will be easier in the future.. > Enable script debugging > --- > > Key: CB-3494 > URL: https://issues.apache.org/jira/browse/CB-3494 > Project: Apache Cordova > Issue Type: New Feature > Components: weinre > Environment: Server: OSX > Target: Android 4.0.3, Cordova 2.7.0 >Reporter: Martin Naumann >Assignee: Patrick Mueller > Labels: javascript, newbie > > Debugging Javascript in a cordova application or on any mobile target would > be very handy and many colleagues requested it or expressed the need for it. > It would be great to be able to set / unset breakpoints in Javascript > (executing on the target device) and see the "Scripts" panel, that > WebInspector provides. > I tried enabling the scripts panel / JS debugger but I think I need some > poking in the right direction here, as I got stuck. > I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3494) Enable script debugging
[ https://issues.apache.org/jira/browse/CB-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Naumann updated CB-3494: --- Description: Debugging Javascript in a cordova application or on any mobile target would be very handy and many colleagues requested it or expressed the need for it. It would be great to be able to set / unset breakpoints in Javascript (executing on the target device) and see the "Scripts" panel, that WebInspector provides. I tried enabling the scripts panel / JS debugger but I think I need some poking in the right direction here, as I got stuck. I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large was: Debugging Javascript in a cordova application or on any mobile target would be very handy and many colleagues requested it or expressed the need for it. I tried enabling the scripts panel / JS debugger but I think I need some poking in the right direction here, as I got stuck. I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large Environment: Server: OSX Target: Android 4.0.3, Cordova 2.7.0 > Enable script debugging > --- > > Key: CB-3494 > URL: https://issues.apache.org/jira/browse/CB-3494 > Project: Apache Cordova > Issue Type: New Feature > Components: weinre > Environment: Server: OSX > Target: Android 4.0.3, Cordova 2.7.0 >Reporter: Martin Naumann >Assignee: Patrick Mueller > Labels: javascript, newbie > > Debugging Javascript in a cordova application or on any mobile target would > be very handy and many colleagues requested it or expressed the need for it. > It would be great to be able to set / unset breakpoints in Javascript > (executing on the target device) and see the "Scripts" panel, that > WebInspector provides. > I tried enabling the scripts panel / JS debugger but I think I need some > poking in the right direction here, as I got stuck. > I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3500) plugman uninstall with plugin living on github.
[ https://issues.apache.org/jira/browse/CB-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Filip Maj resolved CB-3500. --- Resolution: Fixed You should specify uninstall by providing the plugin id. Elaborated on the uninstall instructions in this commit: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=648694b847f70f340ed08e852634182c7172a445 > plugman uninstall with plugin living on github. > --- > > Key: CB-3500 > URL: https://issues.apache.org/jira/browse/CB-3500 > Project: Apache Cordova > Issue Type: Bug > Components: Plugman >Affects Versions: 2.8.0 >Reporter: Steve Gill >Assignee: Filip Maj > Fix For: 2.9.0 > > > Not sure if this is a bug or design decision. > When installing plugins with plugman, you can set your --plugin tag to use > the plugin git repo. > When uninstalling plugins, you can't set your --plugin tag to a use the > plugin git repo. > I understand that we probably don't want to be downloading the repo for a > uninstall. Hence why I am unsure about it being a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3470) Tag Windows 8
[ https://issues.apache.org/jira/browse/CB-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-3470. - Resolution: Fixed > Tag Windows 8 > - > > Key: CB-3470 > URL: https://issues.apache.org/jira/browse/CB-3470 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows 8 >Reporter: Andrew Grieve >Assignee: Jesse MacFadyen > > Steps: > 1. Update cordova.js snapshot to newly tagged version > 2. Update snapshot of cordova-app-hello-world within create template (if it > has changed since previous release) > 3. Run Apache RAT > 4. Test (refer to http://wiki.apache.org/cordova/CuttingReleases#What_to_Test) > 5. Tag! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3500) plugman uninstall with plugin living on github.
Steve Gill created CB-3500: -- Summary: plugman uninstall with plugin living on github. Key: CB-3500 URL: https://issues.apache.org/jira/browse/CB-3500 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 2.8.0 Reporter: Steve Gill Assignee: Filip Maj Fix For: 2.9.0 Not sure if this is a bug or design decision. When installing plugins with plugman, you can set your --plugin tag to use the plugin git repo. When uninstalling plugins, you can't set your --plugin tag to a use the plugin git repo. I understand that we probably don't want to be downloading the repo for a uninstall. Hence why I am unsure about it being a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3499) Plugman uninstall not removing javascript + cordova_plugins.json reference
Steve Gill created CB-3499: -- Summary: Plugman uninstall not removing javascript + cordova_plugins.json reference Key: CB-3499 URL: https://issues.apache.org/jira/browse/CB-3499 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 2.8.0 Reporter: Steve Gill Assignee: Filip Maj Fix For: 2.9.0 As the title states. Plugman uninstall doesn't remove the plugin javascript files and it doesn't remove the plugin reference from cordova_plugins.json. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3495) Create script needs to clean bin/obj folders
[ https://issues.apache.org/jira/browse/CB-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benn Mapes updated CB-3495: --- Fix Version/s: (was: 2.9.0) 2.8.0 > Create script needs to clean bin/obj folders > > > Key: CB-3495 > URL: https://issues.apache.org/jira/browse/CB-3495 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 >Affects Versions: 2.8.0 >Reporter: Jesse MacFadyen >Assignee: Benn Mapes > Fix For: 2.8.0 > > > When creating a new project with the create script, the contents of the > template are blindly copied to a new project. > If the user has ever built the template project then there will be build > artifacts copied over that will cause running the new project to fail. > This happens more for committers than anyone else, but still it would be nice > to not copy over junk. > This may also apply to WP7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3495) Create script needs to clean bin/obj folders
[ https://issues.apache.org/jira/browse/CB-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benn Mapes resolved CB-3495. Resolution: Fixed WP7 : https://git-wip-us.apache.org/repos/asf?p=cordova-wp7.git;a=commit;h=03eb9b76078c1d2a56e1a0891328f7b120edbba7 WP8 : https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=commit;h=cef4e7951728b868265a91a08abb76fde800e685 > Create script needs to clean bin/obj folders > > > Key: CB-3495 > URL: https://issues.apache.org/jira/browse/CB-3495 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 >Affects Versions: 2.8.0 >Reporter: Jesse MacFadyen >Assignee: Benn Mapes > Fix For: 2.8.0 > > > When creating a new project with the create script, the contents of the > template are blindly copied to a new project. > If the user has ever built the template project then there will be build > artifacts copied over that will cause running the new project to fail. > This happens more for committers than anyone else, but still it would be nice > to not copy over junk. > This may also apply to WP7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3498) Certificate Pinning
mgill created CB-3498: - Summary: Certificate Pinning Key: CB-3498 URL: https://issues.apache.org/jira/browse/CB-3498 Project: Apache Cordova Issue Type: Wish Affects Versions: 2.7.0 Reporter: mgill Priority: Minor It would be a handy feature to have certificate pinning supported Examples: https://github.com/iSECPartners/ssl-conservatory/tree/master/ios https://github.com/moxie0/AndroidPinning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3497) ./bin/create script requires `npm install` to be run
Filip Maj created CB-3497: - Summary: ./bin/create script requires `npm install` to be run Key: CB-3497 URL: https://issues.apache.org/jira/browse/CB-3497 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 2.8.0 Reporter: Filip Maj Assignee: Tim Kim Tsted with latest 2.8.x branch. The create script should bootstrap itself as appropriate. Right now, you need to run npm install before you can run create. This is an issue for tools consuming the script (i.e. cordova-cli). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3494) Enable script debugging
[ https://issues.apache.org/jira/browse/CB-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665810#comment-13665810 ] Patrick Mueller commented on CB-3494: - Not sure what you did to get as far as you did. But as far as I know, it's non-trivial to enable script debugging for weinre. Best thing we could do is something like [Aardwolf|https://github.com/lexandera/Aardwolf]. I've never thought it was worth the effort. * for iOS >= 6, you can use remote debugging with Safari on a Mac. * for the Chrome browser on Android, you can also do remote debugging with Chrome on your desktop, not much help for Cordova apps though. * recent Blackberry devices have supported remote debugging as well > Enable script debugging > --- > > Key: CB-3494 > URL: https://issues.apache.org/jira/browse/CB-3494 > Project: Apache Cordova > Issue Type: New Feature > Components: weinre >Reporter: Martin Naumann >Assignee: Patrick Mueller > Labels: javascript, newbie > > Debugging Javascript in a cordova application or on any mobile target would > be very handy and many colleagues requested it or expressed the need for it. > I tried enabling the scripts panel / JS debugger but I think I need some > poking in the right direction here, as I got stuck. > I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3496) Media API does not work at all on Cordova 2.8.0rc1
[ https://issues.apache.org/jira/browse/CB-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3496: --- Priority: Blocker (was: Major) > Media API does not work at all on Cordova 2.8.0rc1 > -- > > Key: CB-3496 > URL: https://issues.apache.org/jira/browse/CB-3496 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 2.8.0 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Fix For: 2.8.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3496) Media API does not work at all on Cordova 2.8.0rc1
Joe Bowser created CB-3496: -- Summary: Media API does not work at all on Cordova 2.8.0rc1 Key: CB-3496 URL: https://issues.apache.org/jira/browse/CB-3496 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.8.0 Reporter: Joe Bowser Assignee: Joe Bowser Fix For: 2.8.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3494) Enable script debugging
[ https://issues.apache.org/jira/browse/CB-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665786#comment-13665786 ] Jesse MacFadyen commented on CB-3494: - Pretty vague request. What platform are you having the issue on? What aspect of 'script debugging' are you asking for? Remote debugging? or on the device? > Enable script debugging > --- > > Key: CB-3494 > URL: https://issues.apache.org/jira/browse/CB-3494 > Project: Apache Cordova > Issue Type: New Feature > Components: weinre >Reporter: Martin Naumann >Assignee: Patrick Mueller > Labels: javascript, newbie > > Debugging Javascript in a cordova application or on any mobile target would > be very handy and many colleagues requested it or expressed the need for it. > I tried enabling the scripts panel / JS debugger but I think I need some > poking in the right direction here, as I got stuck. > I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3495) Create script needs to clean bin/obj folders
[ https://issues.apache.org/jira/browse/CB-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen updated CB-3495: Assignee: Benn Mapes (was: Jesse MacFadyen) > Create script needs to clean bin/obj folders > > > Key: CB-3495 > URL: https://issues.apache.org/jira/browse/CB-3495 > Project: Apache Cordova > Issue Type: Bug > Components: WP8 >Affects Versions: 2.8.0 >Reporter: Jesse MacFadyen >Assignee: Benn Mapes > Fix For: 2.9.0 > > > When creating a new project with the create script, the contents of the > template are blindly copied to a new project. > If the user has ever built the template project then there will be build > artifacts copied over that will cause running the new project to fail. > This happens more for committers than anyone else, but still it would be nice > to not copy over junk. > This may also apply to WP7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3495) Create script needs to clean bin/obj folders
Jesse MacFadyen created CB-3495: --- Summary: Create script needs to clean bin/obj folders Key: CB-3495 URL: https://issues.apache.org/jira/browse/CB-3495 Project: Apache Cordova Issue Type: Bug Components: WP8 Affects Versions: 2.8.0 Reporter: Jesse MacFadyen Assignee: Jesse MacFadyen Fix For: 2.9.0 When creating a new project with the create script, the contents of the template are blindly copied to a new project. If the user has ever built the template project then there will be build artifacts copied over that will cause running the new project to fail. This happens more for committers than anyone else, but still it would be nice to not copy over junk. This may also apply to WP7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3494) Enable script debugging
Martin Naumann created CB-3494: -- Summary: Enable script debugging Key: CB-3494 URL: https://issues.apache.org/jira/browse/CB-3494 Project: Apache Cordova Issue Type: New Feature Components: weinre Reporter: Martin Naumann Assignee: Patrick Mueller Debugging Javascript in a cordova application or on any mobile target would be very handy and many colleagues requested it or expressed the need for it. I tried enabling the scripts panel / JS debugger but I think I need some poking in the right direction here, as I got stuck. I got to this point: https://pbs.twimg.com/media/BK-16yOCMAEmm9K.png:large -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3456) InAppBrowser Causing Viewport Issues on iPad
[ https://issues.apache.org/jira/browse/CB-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-3456. -- Resolution: Duplicate Awesome! Duped this issue. The fix should be (from the original): https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=commit;h=681016b3 > InAppBrowser Causing Viewport Issues on iPad > > > Key: CB-3456 > URL: https://issues.apache.org/jira/browse/CB-3456 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.5.0 > Environment: iPad 6.1 >Reporter: Josh Dean >Assignee: Shazron Abdullah > > Pretty much what was described here > (https://issues.apache.org/jira/browse/CB-3065?focusedCommentId=13635379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13635379), > except on 2.5: > In landscape mode on iPad, when opening the InAppBrowser in landscape mode, > the moment you close the InAppBrowser the viewport of the app switches to > portrait mode. I can't make heads or tails of it. > For reference: here is my viewport meta tag: > > Images showing the issue visually here: http://imgur.com/a/KJMST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665728#comment-13665728 ] Tim Kim commented on CB-3234: - Pushed up the changes here: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=ec82bfaa406860255cc1c4f3d5e49c9fd8a6b26a > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3234) plugman should enforce
[ https://issues.apache.org/jira/browse/CB-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Kim resolved CB-3234. - Resolution: Fixed > plugman should enforce > > > Key: CB-3234 > URL: https://issues.apache.org/jira/browse/CB-3234 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugman >Reporter: Filip Maj >Assignee: Tim Kim > > enforcing cordova project version constraints. likely needs a per-platform > handler addition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3493) Update deletes project if the update fails
Joe Bowser created CB-3493: -- Summary: Update deletes project if the update fails Key: CB-3493 URL: https://issues.apache.org/jira/browse/CB-3493 Project: Apache Cordova Issue Type: Bug Affects Versions: 2.8.0 Reporter: Joe Bowser Priority: Blocker Fix For: 2.8.0 This is extremely bad! We don't want to delete people's stuff, especially if they're too dumb to use version control. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3492) update hasn't been updated to work with cordova.js
[ https://issues.apache.org/jira/browse/CB-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3492: --- Fix Version/s: 2.8.0 Description: Still needs version numbers for cordova.js, this needs to be fixed before 2.8.0 (was: Still needs version numbers.) Affects Version/s: 2.8.0 > update hasn't been updated to work with cordova.js > -- > > Key: CB-3492 > URL: https://issues.apache.org/jira/browse/CB-3492 > Project: Apache Cordova > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Joe Bowser > Fix For: 2.8.0 > > > Still needs version numbers for cordova.js, this needs to be fixed before > 2.8.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3492) update hasn't been updated to work with cordova.js
Joe Bowser created CB-3492: -- Summary: update hasn't been updated to work with cordova.js Key: CB-3492 URL: https://issues.apache.org/jira/browse/CB-3492 Project: Apache Cordova Issue Type: Bug Reporter: Joe Bowser Still needs version numbers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3471) Tag Windows Phone 7
[ https://issues.apache.org/jira/browse/CB-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benn Mapes resolved CB-3471. Resolution: Fixed Tag: https://git-wip-us.apache.org/repos/asf?p=cordova-wp7.git;a=commit;h=d4adc15d7b74a7e08f9887947df004dc59569f6d > Tag Windows Phone 7 > --- > > Key: CB-3471 > URL: https://issues.apache.org/jira/browse/CB-3471 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP7 >Reporter: Andrew Grieve >Assignee: Benn Mapes > > Steps: > 1. Update cordova.js snapshot to newly tagged version > 2. Update snapshot of cordova-app-hello-world within create template (if it > has changed since previous release) > 3. Run Apache RAT > 4. Test (refer to http://wiki.apache.org/cordova/CuttingReleases#What_to_Test) > 5. Tag! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3471) Tag Windows Phone 7
[ https://issues.apache.org/jira/browse/CB-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benn Mapes reassigned CB-3471: -- Assignee: Benn Mapes (was: Jesse MacFadyen) > Tag Windows Phone 7 > --- > > Key: CB-3471 > URL: https://issues.apache.org/jira/browse/CB-3471 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP7 >Reporter: Andrew Grieve >Assignee: Benn Mapes > > Steps: > 1. Update cordova.js snapshot to newly tagged version > 2. Update snapshot of cordova-app-hello-world within create template (if it > has changed since previous release) > 3. Run Apache RAT > 4. Test (refer to http://wiki.apache.org/cordova/CuttingReleases#What_to_Test) > 5. Tag! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3472) Tag Windows Phone 8
[ https://issues.apache.org/jira/browse/CB-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen resolved CB-3472. - Resolution: Fixed > Tag Windows Phone 8 > --- > > Key: CB-3472 > URL: https://issues.apache.org/jira/browse/CB-3472 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP8 >Reporter: Andrew Grieve >Assignee: Jesse MacFadyen > > Steps: > 1. Update cordova.js snapshot to newly tagged version > 2. Update snapshot of cordova-app-hello-world within create template (if it > has changed since previous release) > 3. Run Apache RAT > 4. Test (refer to http://wiki.apache.org/cordova/CuttingReleases#What_to_Test) > 5. Tag! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3451) iOS Cordova app crashes with "failed to resume in time" when reopening
[ https://issues.apache.org/jira/browse/CB-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-3451: - Fix Version/s: 2.8.0 Assigning 2.8.0 for now if I can repro, a fix can go in before final. > iOS Cordova app crashes with "failed to resume in time" when reopening > -- > > Key: CB-3451 > URL: https://issues.apache.org/jira/browse/CB-3451 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 > Environment: Running on iPhone 5 >Reporter: Brendan >Assignee: Shazron Abdullah > Fix For: 2.8.0 > > > I have a Cordova 2.6.0 app that runs well on my iPhone 5. It uses web audio > and canvas, it that's relevant. When I reopen the app, it sometimes restores > fine, but often it crashes, and the crash log indicates "failed to resume in > time". I can share an entire crash log if useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3451) iOS Cordova app crashes with "failed to resume in time" when reopening
[ https://issues.apache.org/jira/browse/CB-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665700#comment-13665700 ] Shazron Abdullah commented on CB-3451: -- Yup, anything fancy going on either window.onload / ondeviceready / resume event? Is your index.html page loading anything besides js/images/html/css, like SVG and the like? > iOS Cordova app crashes with "failed to resume in time" when reopening > -- > > Key: CB-3451 > URL: https://issues.apache.org/jira/browse/CB-3451 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 > Environment: Running on iPhone 5 >Reporter: Brendan >Assignee: Shazron Abdullah > > I have a Cordova 2.6.0 app that runs well on my iPhone 5. It uses web audio > and canvas, it that's relevant. When I reopen the app, it sometimes restores > fine, but often it crashes, and the crash log indicates "failed to resume in > time". I can share an entire crash log if useful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665687#comment-13665687
]
Anis Kadri commented on CB-3459:
Actually, forcing plugin developers to update their spec is not a big issue
because as you mentioned the spec has changed and might change again before
3.0. Worst-case scenario we can do it for them.
Nevertheless, should a plugin that uses the latest spec be backward compatible
with previous Cordova versions? What do you think of that use-case ? I
personally think it should.
> plugman should handle configuration automatically
> -
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 2.7.0
>Reporter: Anis Kadri
>Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> string="MyPlugin" />
> {code}
> OR better yet
> Have the latest plugin.xml spec support old Cordova versions (plist, new/old
> xml).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3491) MobileSpec - Storage test should check for openDatabase function
[ https://issues.apache.org/jira/browse/CB-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665672#comment-13665672 ] Lisa Seacat DeLuca commented on CB-3491: fixed here: https://github.com/ldeluca/cordova-mobile-spec/blob/CB-3491/autotest/tests/storage.tests.js pull requested: https://github.com/apache/cordova-mobile-spec/pull/24 > MobileSpec - Storage test should check for openDatabase function > > > Key: CB-3491 > URL: https://issues.apache.org/jira/browse/CB-3491 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: storage, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Storage test should check for openDatabase function -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3491) MobileSpec - Storage test should check for openDatabase function
Lisa Seacat DeLuca created CB-3491: -- Summary: MobileSpec - Storage test should check for openDatabase function Key: CB-3491 URL: https://issues.apache.org/jira/browse/CB-3491 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor MobileSpec - Storage test should check for openDatabase function -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3420) InAppBrowser Option to Start Hidden
[
https://issues.apache.org/jira/browse/CB-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665643#comment-13665643
]
David Kemp commented on CB-3420:
It seems like focus() and blur() typically mean things like z-ordering and
entry.
I would like to move forward with this item using the syntax:
var iab = window.open('$OAUTH_URL', 'hidden=yes');
//some time later.
iab.show();
// some time later than that
iab.hide();
with the added note that since there is no open requests for hide(), it be left
for later.
> InAppBrowser Option to Start Hidden
> ---
>
> Key: CB-3420
> URL: https://issues.apache.org/jira/browse/CB-3420
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CordovaJS, mobile-spec
>Reporter: Andrew Grieve
>Assignee: Andrew Grieve
>Priority: Minor
>
> One common use-case for the InAppBrowser is to handle an OAuth flow. Some
> flows can be done without any user interaction, so it would be great if the
> InAppBrowser had an option where it would start hidden, and could later be
> reveals through a JS call.
> E.g.
> var iab = window.open('$OAUTH_URL', 'hidden=yes');
> //some time later.
> iab.show();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3488) MobileSpec - Globalization doesn't check for constants
[ https://issues.apache.org/jira/browse/CB-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-3488: --- Summary: MobileSpec - Globalization doesn't check for constants (was: MobileSpec - Globalzation doesn't check for constants) > MobileSpec - Globalization doesn't check for constants > -- > > Key: CB-3488 > URL: https://issues.apache.org/jira/browse/CB-3488 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalzation doesn't check for constants -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3489) MobileSpec - There is no automated test for splashscreen
[ https://issues.apache.org/jira/browse/CB-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665616#comment-13665616 ] Lisa Seacat DeLuca commented on CB-3489: fixed in local repos: https://github.com/ldeluca/cordova-mobile-spec/pull/new/CB-3489 pull request: https://github.com/apache/cordova-mobile-spec/pull/23 > MobileSpec - There is no automated test for splashscreen > > > Key: CB-3489 > URL: https://issues.apache.org/jira/browse/CB-3489 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - There is no automated test for splashscreen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3490) Update CordovaLib iOS Deployment Target in Project Setting to 5.0
Shazron Abdullah created CB-3490: Summary: Update CordovaLib iOS Deployment Target in Project Setting to 5.0 Key: CB-3490 URL: https://issues.apache.org/jira/browse/CB-3490 Project: Apache Cordova Issue Type: Task Components: iOS Affects Versions: Master Reporter: Shazron Abdullah Assignee: Shazron Abdullah Priority: Trivial Fix For: 2.8.0 This in practice is a non-issue since the Target (which overrides the Project Build Setting) is at 5.0. Just a bit of clean up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3489) MobileSpec - There is no automated test for splashscreen
Lisa Seacat DeLuca created CB-3489: -- Summary: MobileSpec - There is no automated test for splashscreen Key: CB-3489 URL: https://issues.apache.org/jira/browse/CB-3489 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor MobileSpec - There is no automated test for splashscreen -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3481) MobileSpec - Compass test fails on all tests when device doesn't have compass support
[ https://issues.apache.org/jira/browse/CB-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca reassigned CB-3481: -- Assignee: Lisa Seacat DeLuca > MobileSpec - Compass test fails on all tests when device doesn't have compass > support > - > > Key: CB-3481 > URL: https://issues.apache.org/jira/browse/CB-3481 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: compass, test > Original Estimate: 48h > Remaining Estimate: 48h > > When the compass hardware is not supported on a device all of the compass > related tests will fail. Rather than fail them all, fail the hardware check > and give the user a helpful message as to why the test failed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3484) MobileSpec - Camera test doesn't test for cleanup function
[ https://issues.apache.org/jira/browse/CB-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-3484: --- Assignee: Lisa Seacat DeLuca > MobileSpec - Camera test doesn't test for cleanup function > -- > > Key: CB-3484 > URL: https://issues.apache.org/jira/browse/CB-3484 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: camera,, test, > Original Estimate: 24h > Remaining Estimate: 24h > > The Mobilespec automated test for camera doesn't check for the cleanup > function -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3485) MobileSpec - Device test should include a check for model spec
[ https://issues.apache.org/jira/browse/CB-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-3485: --- Assignee: Lisa Seacat DeLuca > MobileSpec - Device test should include a check for model spec > -- > > Key: CB-3485 > URL: https://issues.apache.org/jira/browse/CB-3485 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: device, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Device test should include a check for model spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3466) Create Release Branches
[ https://issues.apache.org/jira/browse/CB-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve updated CB-3466: -- Summary: Create Release Branches (was: Create 2.8.x Branches) > Create Release Branches > --- > > Key: CB-3466 > URL: https://issues.apache.org/jira/browse/CB-3466 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android, App Hello World, BlackBerry, CLI, CordovaJS, > Docs, iOS, mobile-spec, OSX, Windows 8, WP7, WP8 >Reporter: Andrew Grieve >Assignee: Andrew Grieve > > Steps: > 1. Create remote branches > 2. Update all VERSION files -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3488) MobileSpec - Globalzation doesn't check for constants
[ https://issues.apache.org/jira/browse/CB-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665493#comment-13665493 ] Lisa Seacat DeLuca commented on CB-3488: fixed in forked repos and requested pull: https://github.com/apache/cordova-mobile-spec/pull/22 > MobileSpec - Globalzation doesn't check for constants > - > > Key: CB-3488 > URL: https://issues.apache.org/jira/browse/CB-3488 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalzation doesn't check for constants -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3305) Automate Release Steps
[ https://issues.apache.org/jira/browse/CB-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665494#comment-13665494 ] Andrew Grieve commented on CB-3305: --- As of commit: https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;a=commit;h=ea2090ae10e20e1c56d75275c29669df8dd81153 Script has ability to: - create release branches - tag release branches - update cordova.js file - update VERSION file > Automate Release Steps > -- > > Key: CB-3305 > URL: https://issues.apache.org/jira/browse/CB-3305 > Project: Apache Cordova > Issue Type: Improvement > Components: Coho >Reporter: Andrew Grieve >Assignee: Andrew Grieve >Priority: Minor > > Going to try and write scripts for dealing with the routine parts of making a > release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3488) MobileSpec - Globalzation doesn't check for constants
Lisa Seacat DeLuca created CB-3488: -- Summary: MobileSpec - Globalzation doesn't check for constants Key: CB-3488 URL: https://issues.apache.org/jira/browse/CB-3488 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor MobileSpec - Globalzation doesn't check for constants -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anis Kadri updated CB-3459:
---
Description:
plugman should know how to handle configuration automatically no matter what
cordova version a project uses.
{code:xml}
{code}
OR
{code:xml}
{code}
OR
{code:xml}
{code}
OR better yet
Have the latest plugin.xml spec support old Cordova versions (plist, new/old
xml).
was:
plugman should know how to handle configuration automatically no matter what
cordova version a project uses.
{code:xml}
{code}
OR
{code:xml}
{code}
OR
{code:xml}
{code}
> plugman should handle configuration automatically
> -
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 2.7.0
>Reporter: Anis Kadri
>Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> string="MyPlugin" />
> {code}
> OR better yet
> Have the latest plugin.xml spec support old Cordova versions (plist, new/old
> xml).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3487) MobileSpec - Globalization doesn't test for getPreferredLanguage
[ https://issues.apache.org/jira/browse/CB-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Jong reassigned CB-3487: -- Assignee: James Jong > MobileSpec - Globalization doesn't test for getPreferredLanguage > > > Key: CB-3487 > URL: https://issues.apache.org/jira/browse/CB-3487 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: James Jong >Priority: Minor > Labels: globalization, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalization doesn't test for getPreferredLanguage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CB-3487) MobileSpec - Globalization doesn't test for getPreferredLanguage
[ https://issues.apache.org/jira/browse/CB-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Jong reassigned CB-3487: -- Assignee: Lisa Seacat DeLuca (was: James Jong) > MobileSpec - Globalization doesn't test for getPreferredLanguage > > > Key: CB-3487 > URL: https://issues.apache.org/jira/browse/CB-3487 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalization doesn't test for getPreferredLanguage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3487) MobileSpec - Globalization doesn't test for getPreferredLanguage
[ https://issues.apache.org/jira/browse/CB-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665473#comment-13665473 ] Lisa Seacat DeLuca commented on CB-3487: fixed in personal repos: https://github.com/ldeluca/cordova-mobile-spec/blob/CB-3487/autotest/tests/globalization.tests.js requested pull: https://github.com/apache/cordova-mobile-spec/pull/21 > MobileSpec - Globalization doesn't test for getPreferredLanguage > > > Key: CB-3487 > URL: https://issues.apache.org/jira/browse/CB-3487 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Priority: Minor > Labels: globalization, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Globalization doesn't test for getPreferredLanguage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3487) MobileSpec - Globalization doesn't test for getPreferredLanguage
Lisa Seacat DeLuca created CB-3487: -- Summary: MobileSpec - Globalization doesn't test for getPreferredLanguage Key: CB-3487 URL: https://issues.apache.org/jira/browse/CB-3487 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Priority: Minor MobileSpec - Globalization doesn't test for getPreferredLanguage -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3486) [BlackBerry10] Running scripts in Windows results in working directory change
[ https://issues.apache.org/jira/browse/CB-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-3486. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=commit;h=b42482ac4700f11231585879cac702a7fd3aadd2 > [BlackBerry10] Running scripts in Windows results in working directory change > - > > Key: CB-3486 > URL: https://issues.apache.org/jira/browse/CB-3486 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 2.8.0 >Reporter: Bryan Higgins >Assignee: Bryan Higgins > Fix For: 2.8.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3486) [BlackBerry10] Running scripts in Windows results in working directory change
Bryan Higgins created CB-3486: - Summary: [BlackBerry10] Running scripts in Windows results in working directory change Key: CB-3486 URL: https://issues.apache.org/jira/browse/CB-3486 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 2.8.0 Reporter: Bryan Higgins Assignee: Bryan Higgins Fix For: 2.8.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665420#comment-13665420
]
Braden Shepherdson commented on CB-3459:
Let's distinguish between changes that break the tools for plugin developers,
and changes that break the tools for application developers. This is the former
- it only matters if you're maintaining a plugin.xml somewhere. For that, I
think yes, we can break backwards compatibility in this not-yet-really-released
tools.
We seem to have fallen into the trap of "release early, discover when you try
to release often that people depend on your alpha crap you're trying to fix."
These tools should have had a nice big "alpha, under heavy development, expect
suffering" warning label on them from the beginning, that we removed with 3.0
and their official launch.
Now we're looking at the npm downloads and worrying about breaking things, with
tools that have evolved massively in the last few weeks already, quite apart
from this change. Plugin authors will have to update eventually - how much work
are we prepared to do to buy them two months of wiggle room for a 90-second
change to their plugin.xml files?
> plugman should handle configuration automatically
> -
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 2.7.0
>Reporter: Anis Kadri
>Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> string="MyPlugin" />
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665406#comment-13665406
]
Anis Kadri commented on CB-3459:
You are essentially saying that we should break backwards compatibility and
only target Cordova 3.0 ?
> plugman should handle configuration automatically
> -
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 2.7.0
>Reporter: Anis Kadri
>Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> string="MyPlugin" />
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3485) MobileSpec - Device test should include a check for model spec
[ https://issues.apache.org/jira/browse/CB-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665407#comment-13665407 ] Lisa Seacat DeLuca commented on CB-3485: fixed in my repos: https://github.com/ldeluca/cordova-mobile-spec/blob/CB-3485/autotest/tests/device.tests.js submitted pull request: https://github.com/apache/cordova-mobile-spec/pull/20 > MobileSpec - Device test should include a check for model spec > -- > > Key: CB-3485 > URL: https://issues.apache.org/jira/browse/CB-3485 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Priority: Minor > Labels: device, test, > Original Estimate: 24h > Remaining Estimate: 24h > > MobileSpec - Device test should include a check for model spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3485) MobileSpec - Device test should include a check for model spec
Lisa Seacat DeLuca created CB-3485: -- Summary: MobileSpec - Device test should include a check for model spec Key: CB-3485 URL: https://issues.apache.org/jira/browse/CB-3485 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Priority: Minor MobileSpec - Device test should include a check for model spec -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3484) MobileSpec - Camera test doesn't test for cleanup function
[ https://issues.apache.org/jira/browse/CB-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665382#comment-13665382 ] Lisa Seacat DeLuca commented on CB-3484: fixed in my git repos. https://github.com/ldeluca/cordova-mobile-spec/blob/CB-3484/autotest/tests/camera.tests.js pull request initiated: https://github.com/apache/cordova-mobile-spec/pull/19 > MobileSpec - Camera test doesn't test for cleanup function > -- > > Key: CB-3484 > URL: https://issues.apache.org/jira/browse/CB-3484 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Priority: Minor > Labels: camera,, test, > Original Estimate: 24h > Remaining Estimate: 24h > > The Mobilespec automated test for camera doesn't check for the cleanup > function -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3484) MobileSpec - Camera test doesn't test for cleanup function
Lisa Seacat DeLuca created CB-3484: -- Summary: MobileSpec - Camera test doesn't test for cleanup function Key: CB-3484 URL: https://issues.apache.org/jira/browse/CB-3484 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Priority: Minor The Mobilespec automated test for camera doesn't check for the cleanup function -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3456) InAppBrowser Causing Viewport Issues on iPad
[ https://issues.apache.org/jira/browse/CB-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665331#comment-13665331 ] Josh Dean commented on CB-3456: --- A-HA! Found this bit of code leftover in our MainViewController.m file's viewWillAppear method: // Set the main view to utilize the entire application frame space of the device. // Change this to suit your view's UI footprint needs in your application. self.view.frame = [[UIScreen mainScreen] applicationFrame]; This seems to have all but removed from 2.1 to 2.5. Removing this fixes the offensive error altogether. > InAppBrowser Causing Viewport Issues on iPad > > > Key: CB-3456 > URL: https://issues.apache.org/jira/browse/CB-3456 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.5.0 > Environment: iPad 6.1 >Reporter: Josh Dean >Assignee: Shazron Abdullah > > Pretty much what was described here > (https://issues.apache.org/jira/browse/CB-3065?focusedCommentId=13635379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13635379), > except on 2.5: > In landscape mode on iPad, when opening the InAppBrowser in landscape mode, > the moment you close the InAppBrowser the viewport of the app switches to > portrait mode. I can't make heads or tails of it. > For reference: here is my viewport meta tag: > > Images showing the issue visually here: http://imgur.com/a/KJMST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-160) history.back() not working on windows phone
[ https://issues.apache.org/jira/browse/CB-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665318#comment-13665318 ] Jesse MacFadyen commented on CB-160: Please post a brief sample demonstrating the issue. > history.back() not working on windows phone > --- > > Key: CB-160 > URL: https://issues.apache.org/jira/browse/CB-160 > Project: Apache Cordova > Issue Type: Bug > Components: WP7 >Affects Versions: 1.3.0 > Environment: emulator >Reporter: Donatas Simelis >Assignee: Jesse MacFadyen > > history.back() is not working at all on my WP7 phonegap application. > First noticed it by investigating why jquery mobile back button was not > working, but it seems that all calls to history.back() just do nothing. > It's all good on all other environments i've tested, so it must be windows > phone related stuff. > Can't find a related bug - what is the solution? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-3483) JQuery Mobile Back button doesn't work on WP
[ https://issues.apache.org/jira/browse/CB-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryna updated CB-3483: --- Attachment: CordovaWP7_2_4_0_Full3.rar > JQuery Mobile Back button doesn't work on WP > > > Key: CB-3483 > URL: https://issues.apache.org/jira/browse/CB-3483 > Project: Apache Cordova > Issue Type: Bug > Components: WP7 >Reporter: Maryna >Assignee: Jesse MacFadyen > Attachments: CordovaWP7_2_4_0_Full3.rar > > > The case was pressing buttons in app that causes call of > $.mobile.changePage() which must programmaticaly change page and leave a new > browser history entry (when 'changeHash' parameter is set to true which is by > default). While checking this fact elucidated that browser history is empty > and there is no programmaticaly changed entries. Pressing 'back' button > causes native window.history.back() call which come to be useless. > This is because the application navigation occurs entirely within a browser > control—hence, from the perspective of the Silverlight framework, the > application has a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3483) JQuery Mobile Back button doesn't work on WP
Maryna created CB-3483: -- Summary: JQuery Mobile Back button doesn't work on WP Key: CB-3483 URL: https://issues.apache.org/jira/browse/CB-3483 Project: Apache Cordova Issue Type: Bug Components: WP7 Reporter: Maryna Assignee: Jesse MacFadyen The case was pressing buttons in app that causes call of $.mobile.changePage() which must programmaticaly change page and leave a new browser history entry (when 'changeHash' parameter is set to true which is by default). While checking this fact elucidated that browser history is empty and there is no programmaticaly changed entries. Pressing 'back' button causes native window.history.back() call which come to be useless. This is because the application navigation occurs entirely within a browser control—hence, from the perspective of the Silverlight framework, the application has a single page. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-160) history.back() not working on windows phone
[ https://issues.apache.org/jira/browse/CB-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665307#comment-13665307 ] Maryna commented on CB-160: --- No, it doesn't work on devices too. The case was pressing buttons in app that causes call of $.mobile.changePage() which must programmaticaly change page and leave a new browser history entry (when 'changeHash' parameter is set to true which is by default). While checking this fact elucidated that browser history is empty and there is no programmaticaly changed entries. Pressing 'back' button causes native window.history.back() call which come to be useless because window.history is absolutely empty. > history.back() not working on windows phone > --- > > Key: CB-160 > URL: https://issues.apache.org/jira/browse/CB-160 > Project: Apache Cordova > Issue Type: Bug > Components: WP7 >Affects Versions: 1.3.0 > Environment: emulator >Reporter: Donatas Simelis >Assignee: Jesse MacFadyen > > history.back() is not working at all on my WP7 phonegap application. > First noticed it by investigating why jquery mobile back button was not > working, but it seems that all calls to history.back() just do nothing. > It's all good on all other environments i've tested, so it must be windows > phone related stuff. > Can't find a related bug - what is the solution? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3456) InAppBrowser Causing Viewport Issues on iPad
[ https://issues.apache.org/jira/browse/CB-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665297#comment-13665297 ] Josh Dean commented on CB-3456: --- Updates: after throwing my entire www folder from my current project into a brand new project, I am not seeing the issue anymore. This project has been updated several times over. Is it possible that it is a product of doing phonegap version upgrades? > InAppBrowser Causing Viewport Issues on iPad > > > Key: CB-3456 > URL: https://issues.apache.org/jira/browse/CB-3456 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.5.0 > Environment: iPad 6.1 >Reporter: Josh Dean >Assignee: Shazron Abdullah > > Pretty much what was described here > (https://issues.apache.org/jira/browse/CB-3065?focusedCommentId=13635379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13635379), > except on 2.5: > In landscape mode on iPad, when opening the InAppBrowser in landscape mode, > the moment you close the InAppBrowser the viewport of the app switches to > portrait mode. I can't make heads or tails of it. > For reference: here is my viewport meta tag: > > Images showing the issue visually here: http://imgur.com/a/KJMST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665296#comment-13665296 ] James Jong commented on CB-2905: Created JIRA issue for this https://issues.apache.org/jira/browse/CB-3482 > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3482) Allow image metadata to be saved to album on iOS
James Jong created CB-3482: -- Summary: Allow image metadata to be saved to album on iOS Key: CB-3482 URL: https://issues.apache.org/jira/browse/CB-3482 Project: Apache Cordova Issue Type: Improvement Components: iOS Reporter: James Jong Assignee: James Jong Priority: Minor The current iOS implementation loses GPS information when saving to photo album. Need to investigate if there are workarounds in iOS to save this info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665293#comment-13665293 ] James Jong commented on CB-2905: No problem. Glad to at least verify we're seeing the same thing. I agree, it would be great to have in the saved album too. It's definitely a limitation of the current iOS API implementation. Cordova is using UIImageWriteToSavedPhotosAlbum from UIKit which strips the GPS metadata away. I will create a improvement item to see if there is a way to improve on it. > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3481) MobileSpec - Compass test fails on all tests when device doesn't have compass support
[ https://issues.apache.org/jira/browse/CB-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665294#comment-13665294 ] Lisa Seacat DeLuca commented on CB-3481: Fixed here: https://github.com/ldeluca/cordova-mobile-spec/blob/CB-3481/autotest/tests/compass.tests.js > MobileSpec - Compass test fails on all tests when device doesn't have compass > support > - > > Key: CB-3481 > URL: https://issues.apache.org/jira/browse/CB-3481 > Project: Apache Cordova > Issue Type: Test >Reporter: Lisa Seacat DeLuca >Priority: Minor > Labels: compass, test > Original Estimate: 48h > Remaining Estimate: 48h > > When the compass hardware is not supported on a device all of the compass > related tests will fail. Rather than fail them all, fail the hardware check > and give the user a helpful message as to why the test failed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665283#comment-13665283 ] Kelly John Carney commented on CB-2905: --- Oh boy, hang on. Now that I'm checking, it seems saveToPhotoAlbum did not have the GPS data. Sorry about that. Seems that it should right? If it can be in the imageURL copy, why not the saveToPhotoAlbum? It's great to have the GPS info in the imageURL copy for sure! > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3481) MobileSpec - Compass test fails on all tests when device doesn't have compass support
Lisa Seacat DeLuca created CB-3481: -- Summary: MobileSpec - Compass test fails on all tests when device doesn't have compass support Key: CB-3481 URL: https://issues.apache.org/jira/browse/CB-3481 Project: Apache Cordova Issue Type: Test Reporter: Lisa Seacat DeLuca Priority: Minor When the compass hardware is not supported on a device all of the compass related tests will fail. Rather than fail them all, fail the hardware check and give the user a helpful message as to why the test failed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3456) InAppBrowser Causing Viewport Issues on iPad
[ https://issues.apache.org/jira/browse/CB-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665281#comment-13665281 ] Josh Dean commented on CB-3456: --- Interestingly enough, I am not able to repo this on a brand new project, even with my viewport. > InAppBrowser Causing Viewport Issues on iPad > > > Key: CB-3456 > URL: https://issues.apache.org/jira/browse/CB-3456 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.5.0 > Environment: iPad 6.1 >Reporter: Josh Dean >Assignee: Shazron Abdullah > > Pretty much what was described here > (https://issues.apache.org/jira/browse/CB-3065?focusedCommentId=13635379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13635379), > except on 2.5: > In landscape mode on iPad, when opening the InAppBrowser in landscape mode, > the moment you close the InAppBrowser the viewport of the app switches to > portrait mode. I can't make heads or tails of it. > For reference: here is my viewport meta tag: > > Images showing the issue visually here: http://imgur.com/a/KJMST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665279#comment-13665279 ] James Jong commented on CB-2905: Strange that we're seeing different results... I just tried Cordova 2.3.0 with the options above and do not see the GPS data in the saved album. It does show EXIF data, but not GPS info. Note that pictures taken with the iOS camera do contain GPS info. Just double checking, the picture you are referring to is from Cordova camera API? > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-3480) cordova-android/bin/update script needs update to remove VERSION
David Kemp created CB-3480: -- Summary: cordova-android/bin/update script needs update to remove VERSION Key: CB-3480 URL: https://issues.apache.org/jira/browse/CB-3480 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 2.8.0 Reporter: David Kemp Assignee: David Kemp the scripts previously used cordova-XXX.js, now should be cordova.js -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-285) Add property returning root path of PhoneGap files
[ https://issues.apache.org/jira/browse/CB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Woghiren updated CB-285: Assignee: Max Woghiren (was: Andrew Grieve) > Add property returning root path of PhoneGap files > -- > > Key: CB-285 > URL: https://issues.apache.org/jira/browse/CB-285 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaJS >Affects Versions: 1.4.0 > Environment: Both PhoneGap SDK and PhoneGap Build >Reporter: Ashley Gullen >Assignee: Max Woghiren > Labels: features > > There needs to be a property in PhoneGap that returns the root path to the > general files added to the PhoneGap project (i.e. the directory index.html is > in). For example, if I add 'music.mp3' to my project, in Android it will be > located in: > /android_asset/www/music.mp3 > On iOS after being built with PhoneGap Build it will be located in some path > like this: > /var/mobile/Applications//.app/www/music.mp3 > However, there does not appear to be a programmatic way to determine both > and .app. > This has two side effects: > 1. Paths to audio for Media must be hard-coded separately depending on the > platform, which is inconvenient. > 2. Paths to audio for Media cannot be known if developing a framework that > uses PhoneGap. Since a framework does not know the App ID or name in > advance, it's impossible for the framework to determine the correct path. > This is actively blocking audio from working on iOS in PhoneGap projects > exported by Construct 2 (www.scirra.com), a HTML5 game creator. Also, it > seems like kind of an important function to make available anyway, since > hard-coding paths for each platform is a pain. > This PhoneGap Support thread led to this issue: > http://phonegap.tenderapp.com/discussions/questions/208-android_asset-equivalent-for-ios -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[
https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665259#comment-13665259
]
Kelly John Carney commented on CB-2905:
---
Using the option "saveToPhotoAlbum" in Cordova-2.3.0.js will produce a photo
with all the normal EXIF meta data, including the GPS data. I've been waiting
for the GPS data to be saved in the Camera imageURL. That's now working in
snapshot cordova-ios-4b672e0 but the photo saved to the album is now missing
the GPS data.
navigator.camera.getPicture
(
getPhoto,
onFail,
{
quality: 50,
destinationType: Camera.DestinationType.FILE_URI, // // Return image
file URI
sourceType:Camera.PictureSourceType.CAMERA,
correctOrientation: 1,
saveToPhotoAlbum: 1
}
);
}
> GeoLocation Exif Data
> -
>
> Key: CB-2905
> URL: https://issues.apache.org/jira/browse/CB-2905
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 2.6.0
>Reporter: Lorin Beer
>Assignee: Lorin Beer
> Fix For: 2.8.0
>
>
> Geolocation metadata is not included in the metadata dictionaries provided by
> UIImagePickerController, if we want that data included, we'll need to
> manually add it ourselves.
> Add geotags to the metadata dict before passing it to the JpegHeaderWriter
> for writing and splicing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3456) InAppBrowser Causing Viewport Issues on iPad
[ https://issues.apache.org/jira/browse/CB-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665255#comment-13665255 ] Josh Dean commented on CB-3456: --- Currently making a new 2.5.0 project and adding in the InAppBrowser stuff. Will let you know where it goes from there. > InAppBrowser Causing Viewport Issues on iPad > > > Key: CB-3456 > URL: https://issues.apache.org/jira/browse/CB-3456 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.5.0 > Environment: iPad 6.1 >Reporter: Josh Dean >Assignee: Shazron Abdullah > > Pretty much what was described here > (https://issues.apache.org/jira/browse/CB-3065?focusedCommentId=13635379&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13635379), > except on 2.5: > In landscape mode on iPad, when opening the InAppBrowser in landscape mode, > the moment you close the InAppBrowser the viewport of the app switches to > portrait mode. I can't make heads or tails of it. > For reference: here is my viewport meta tag: > > Images showing the issue visually here: http://imgur.com/a/KJMST -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665251#comment-13665251 ] James Jong commented on CB-2905: [~jira_fossils] I have not seen the geolocation data before when saving to the photo album w Cordova. Which Cordova version did you see it in? > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3476) Tag CLI
[ https://issues.apache.org/jira/browse/CB-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665242#comment-13665242 ] Braden Shepherdson commented on CB-3476: Yes, please wait. Though since that depends on the spectacularly bikeshed-able app/ directory discussion, this might take some time. In the meantime, I have nearly-ready changes to add git refs support to dependency tags. > Tag CLI > --- > > Key: CB-3476 > URL: https://issues.apache.org/jira/browse/CB-3476 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI >Reporter: Andrew Grieve >Assignee: Filip Maj > > This should wait until all platforms are tagged. > Steps: > 1. Update snapshot of repos within cordova-cli > 2. Test that basic commands work properly (installing plugins, creating > project, edit / refresh cycle) > 3. Test that running CLI on a project created with a previous version of CLI > works as expected > 4. Tag -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CB-3384) Resource Loading API for Android
[ https://issues.apache.org/jira/browse/CB-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Braden Shepherdson resolved CB-3384. Resolution: Fixed Fix Version/s: 2.8.0 This is all committed and the issue can be closed. > Resource Loading API for Android > > > Key: CB-3384 > URL: https://issues.apache.org/jira/browse/CB-3384 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Reporter: Andrew Grieve >Assignee: Shravan Narayan > Fix For: 2.8.0 > > > Motivations: > 1. Many plugins do not handle URLs correctly when they are in the form > content: or file:///android_asset. > 2. For the cordova-app-harness, there needs to be a way to re-route resource > load requests so that the harness can load app resources while still > respecting the tag. > Short Description > All plugins can watch the loading of any uri's Eg: opening of files, the > browser making requests to load files etc etc. > In addition to watching they may assist in loading the uri's. > For example, a use case here is - suppose a mimetype for a hypothetical > extension ".abc" doesn't exist, a plugin could check the extension of a > loaded uri and set the mimetype. This would now be set for all files loaded > in the system. > Pseudo code of the mechanism: > 1. make a request 'R' to a uri. > 2. loop through all plugins to see if any plugins change the request > 3. if the request changes, set 'R' to this modified request and repeat step 3 > 4. load request 'R' and return result -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3459) plugman should handle configuration automatically
[
https://issues.apache.org/jira/browse/CB-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665225#comment-13665225
]
Braden Shepherdson commented on CB-3459:
I actually disagree with this. We've already talked about deprecation and the
plugin spec and tools. We agreed they don't have as strict a deprecation policy
as Cordova proper. These tools are not the official path until 3.0, so I'm not
at all convinced they should have logic to support the plugin.xml spec from 2.6
and 2.7, let alone the ancient form.
I think supporting these brief misadventures in plugin.xml format is more work
than it's worth when 95% of the new-style plugins that exist are owned by
Cordova developers on this list, who know about the change. Updating all of our
dozen plugins for Chrome-cordova took only a few minutes.
> plugman should handle configuration automatically
> -
>
> Key: CB-3459
> URL: https://issues.apache.org/jira/browse/CB-3459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugman
>Affects Versions: 2.7.0
>Reporter: Anis Kadri
>Assignee: Filip Maj
> Fix For: 3.0.0
>
>
> plugman should know how to handle configuration automatically no matter what
> cordova version a project uses.
> {code:xml}
>
>
>
> {code}
> OR
> {code:xml}
>
>
>
>
>
> {code}
> OR
> {code:xml}
> string="MyPlugin" />
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2905) GeoLocation Exif Data
[ https://issues.apache.org/jira/browse/CB-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665221#comment-13665221 ] Kelly John Carney commented on CB-2905: --- While this did fix the problem of missing GPS meta data in the photo, now that same data is missing from the optional copy saved to the iPhone photo album. It used to be there. > GeoLocation Exif Data > - > > Key: CB-2905 > URL: https://issues.apache.org/jira/browse/CB-2905 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 2.6.0 >Reporter: Lorin Beer >Assignee: Lorin Beer > Fix For: 2.8.0 > > > Geolocation metadata is not included in the metadata dictionaries provided by > UIImagePickerController, if we want that data included, we'll need to > manually add it ourselves. > Add geotags to the metadata dict before passing it to the JpegHeaderWriter > for writing and splicing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-3453) Retrieve the original picture from the library
[ https://issues.apache.org/jira/browse/CB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665166#comment-13665166 ] James Jong edited comment on CB-3453 at 5/23/13 1:28 PM: - Currently, the iOS behavior is always to rescale. I'll start looking into this. was (Author: wjamesjong): Currently, the iOS behavior is always to resize. I'll start looking into this. > Retrieve the original picture from the library > -- > > Key: CB-3453 > URL: https://issues.apache.org/jira/browse/CB-3453 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: Master, 2.6.0, 2.7.0 >Reporter: Abel Muiño >Assignee: James Jong >Priority: Minor > > Cordova iOS always re-encodes the picture, sometimes making it larger than > the original. > In order to be cross-platform, it should match Android's behavior, where > using default size, no orientation correction and 100% quality returns the > unmodified picture (alternatively Cordova could provide an explicit API for > reading the original pictures) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3453) Retrieve the original picture from the library
[ https://issues.apache.org/jira/browse/CB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665166#comment-13665166 ] James Jong commented on CB-3453: Currently, the iOS behavior is always to resize. I'll start looking into this. > Retrieve the original picture from the library > -- > > Key: CB-3453 > URL: https://issues.apache.org/jira/browse/CB-3453 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: Master, 2.6.0, 2.7.0 >Reporter: Abel Muiño >Assignee: James Jong >Priority: Minor > > Cordova iOS always re-encodes the picture, sometimes making it larger than > the original. > In order to be cross-platform, it should match Android's behavior, where > using default size, no orientation correction and 100% quality returns the > unmodified picture (alternatively Cordova could provide an explicit API for > reading the original pictures) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3453) Retrieve the original picture from the library
[ https://issues.apache.org/jira/browse/CB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665155#comment-13665155 ] Andrew Grieve commented on CB-3453: --- Nothing wrong. I agree that behaviour is fine. We should fix it for iOS. I agree the name resolveLocalFileSystemURI is weird. It's a part of the HTML5 FileSystem spec though, so that's why we're going with it. > Retrieve the original picture from the library > -- > > Key: CB-3453 > URL: https://issues.apache.org/jira/browse/CB-3453 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: Master, 2.6.0, 2.7.0 >Reporter: Abel Muiño >Assignee: James Jong >Priority: Minor > > Cordova iOS always re-encodes the picture, sometimes making it larger than > the original. > In order to be cross-platform, it should match Android's behavior, where > using default size, no orientation correction and 100% quality returns the > unmodified picture (alternatively Cordova could provide an explicit API for > reading the original pictures) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3364) README not up to date
[
https://issues.apache.org/jira/browse/CB-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664983#comment-13664983
]
Angela Fowler commented on CB-3364:
---
Thanks for the new version. I still have some questions about the README.
The "Cordova Android Developer Tools" section talks about installing the
dependencies however the package.json does not contain any dependencies. It
contains a "bin" which maps command names to local file names.
"bin": {
"create": "./create",
"bench":"./bench",
"autotest": "./autotest",
"BOOM": "./BOOM",
"test": "./test"
},
However the only command in the bin directory is create (and also update which
is not in package.json bin).
The autotest and test exist in the cordova-cli project but only for ios.
I could not find bench or BOOM.
Secondly, the create script is a bash script. There is also a create.js and
create.bat for Windows which does not appear to require npm.
Is there any use for npm on Windows in cordova-android?
Thirdly, is this how npm looks when correctly installed for cordova-android?
Could it have failed somehow because the repository is pointing to incubator?
c:\development\cordova-2.7.0\cordova-android\bin>npm list npm WARN package.json
cordova-android-cli@0.0.1 No README.md file found!
cordova-android-cli@0.0.1 c:\development\cordova-2.7.0\cordova-android\bin
└── (empty)
Note : I've used npm successfully in cordova-js which has several dependencies
installed and listed.
> README not up to date
> -
>
> Key: CB-3364
> URL: https://issues.apache.org/jira/browse/CB-3364
> Project: Apache Cordova
> Issue Type: Task
> Components: Android
>Affects Versions: 2.6.0, 2.7.0
> Environment: Windows
>Reporter: Angela Fowler
>Assignee: Joe Bowser
>Priority: Minor
> Labels: documentation
>
> Some of this also applies to the readme at
> https://github.com/apache/cordova-android
> 1. Instructions to move the codec jar to the libs folder but this is done in
> Windows create.js script. Maybe the bash script doesn't download it, perhaps
> split up the instructions for Windows and Linux/Unix?
> 2. Instructions to install node.js and npm to use the create script but I had
> problems with npm and uninstalled it. I created projects with create.bat
> (runs create.js) and use the emulator etc in Eclipse so it would be nice if
> the README gave more detail about what npm is really needed for.
> 3. Contains references to http://incubator.apache.org/cordova/ and
> https://github.com/KentBeck/junit which no longer exist
> Also the bin\package.json also refers to the incubator site which doesn't
> exist
> "url": "http://git-wip-us.apache.org/repos/asf/incubator-cordova-android.git";
> Should a separate issue be created for this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3453) Retrieve the original picture from the library
[ https://issues.apache.org/jira/browse/CB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664945#comment-13664945 ] Abel Muiño commented on CB-3453: BTW: what's wrong with the approach used in cordova-android? (which is something like _"unless you request some changes, I'll give you an exact copy of the original"_). > Retrieve the original picture from the library > -- > > Key: CB-3453 > URL: https://issues.apache.org/jira/browse/CB-3453 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: Master, 2.6.0, 2.7.0 >Reporter: Abel Muiño >Assignee: James Jong >Priority: Minor > > Cordova iOS always re-encodes the picture, sometimes making it larger than > the original. > In order to be cross-platform, it should match Android's behavior, where > using default size, no orientation correction and 100% quality returns the > unmodified picture (alternatively Cordova could provide an explicit API for > reading the original pictures) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-3453) Retrieve the original picture from the library
[
https://issues.apache.org/jira/browse/CB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664942#comment-13664942
]
Abel Muiño commented on CB-3453:
IIRC, we tried {{resolveLocalFileSystemURI()}} without success (but using
2.6.0) for NATIVE_URIs (and FILE_URI creates this altered copy of the original
that we want to avoid).
On a side note, I find the name {{resolveLocalFileSystemURI()}} would be
confusing if it could as well handle NATIVE_URIs. Maybe
{{resolveToLocalFileSystemURI}} (or just {{resolveURI}}) would be clearer? (I
know, it would break older apps when upgrading, but some kind of alias with a
deprecation warning could be put in place).
> Retrieve the original picture from the library
> --
>
> Key: CB-3453
> URL: https://issues.apache.org/jira/browse/CB-3453
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: Master, 2.6.0, 2.7.0
>Reporter: Abel Muiño
>Assignee: James Jong
>Priority: Minor
>
> Cordova iOS always re-encodes the picture, sometimes making it larger than
> the original.
> In order to be cross-platform, it should match Android's behavior, where
> using default size, no orientation correction and 100% quality returns the
> unmodified picture (alternatively Cordova could provide an explicit API for
> reading the original pictures)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
