[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805139#comment-13805139 ] Piotr Zalewa commented on CB-4966: -- Old plugin style. Fixed with https://github.com/zalun/cordova-plugin-dialogs/commit/25e6a24d6c624efb91d83c5a308306028e1586e9 dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-3205) orientation
[ https://issues.apache.org/jira/browse/CB-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805140#comment-13805140 ] Piotr Zalewa commented on CB-3205: -- Brilliant! Thanks orientation --- Key: CB-3205 URL: https://issues.apache.org/jira/browse/CB-3205 Project: Apache Cordova Issue Type: Sub-task Components: FirefoxOS Reporter: Herm Wong Assignee: Herm Wong -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805187#comment-13805187 ] Piotr Zalewa commented on CB-4966: -- Just found out that the call to executed function changed as well. All arguments (title, message and buttonLabels) are now passed as an array in first argument. I'm changing that. dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805191#comment-13805191 ] Piotr Zalewa commented on CB-4966: -- Arguments fixed with https://github.com/zalun/cordova-plugin-dialogs/commit/77a73ece0fc90a8a60d12eabf0b7aa3db112f29d dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[
https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Higgins resolved CB-5196.
---
Resolution: Won't Fix
As Jeff stated, you'll need to use the plugin. Cordova is not compatible with
the WebWorks SDK as of 2.8.
BB10 invoke() plugin is shadowded by cordova.js
---
Key: CB-5196
URL: https://issues.apache.org/jira/browse/CB-5196
Project: Apache Cordova
Issue Type: Bug
Components: BlackBerry
Affects Versions: 3.1.0
Environment: Blackberry 10
Reporter: Mike Billau
Attachments: bbInvoke.html
Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to
call any BB API, webworks.js needs to be included in the html file.
The problem is that there does not seem to be a way to call invoke():
1. Create a simple BB10 app using the attached HTML file,
2. Add feature to the config.xml: feature id=blackberry.invoke
name=blackberry.invoke value=blackberry.invoke/
3. Run the app. Press the button; the browser window doesn't open.
4. Edit the HTML file and place the cordova.js script before webworks.js
script
5. Run the app again, and there is a popup saying: Error intializing
cordova:undefined. After dismissing the alert, you can press the button and
the browser opens just fine.
Analysis:
Internally blackberry.invoke.invoke() ('invoke' plugin) calls
*window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where
the problem is: *window.webworks* is defined in both cordova.js and
webworks.js.The one in cordova.js doesn't have 'event' function whereas it is
available in window.webworks of webworks.js. Hence when webworks.js is loaded
after cordova.js, it works fine and not if it is reversed.
Even though it works when we put webworks.js first we need to squash the
alert() and make sure cordova initializes correctly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-4931) Allow --params option to overwrite defaults
[ https://issues.apache.org/jira/browse/CB-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805287#comment-13805287 ] ASF subversion and git services commented on CB-4931: - Commit bf0ef2b0720a86b19b11b672eb88f7b2bc3b22dc in branch refs/heads/master from [~jeffheifetz] [ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=bf0ef2b ] [CB-4931] Updated signing process to allow passthrough of args - Allowed users to specify tool parameters through blackberry10.json - Fixed signer logic to default to user parameters Reviewed by Bryan Higgins bhigg...@blackberry.com Tested by Jenny Gee j...@blackberry.com Allow --params option to overwrite defaults --- Key: CB-4931 URL: https://issues.apache.org/jira/browse/CB-4931 Project: Apache Cordova Issue Type: Improvement Reporter: Jeffrey Heifetz Assignee: Jeffrey Heifetz Priority: Trivial -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (CB-4931) Allow --params option to overwrite defaults
[ https://issues.apache.org/jira/browse/CB-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-4931. --- Resolution: Fixed Allow --params option to overwrite defaults --- Key: CB-4931 URL: https://issues.apache.org/jira/browse/CB-4931 Project: Apache Cordova Issue Type: Improvement Reporter: Jeffrey Heifetz Assignee: Jeffrey Heifetz Priority: Trivial -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805313#comment-13805313 ] Braden Shepherdson commented on CB-5198: Whoa, hang on. The change to add the hash has been in plugman for a long time, since Sept. 3. It was in the 0.11, 0.12, and 0.13 Plugman releases. The 3.0.0 branch of the plugins very old. Remember that the plugins have their own unique semvers now. For file-transfer above, the 3.0.0 branch dates from July 18th, and the plugin has undergone many changes since, including the removal of the .core namespace. I'm not surprised it isn't working. Since the plugins have had registry dependencies for a while now, I think the right approach is to view this as not being a regression, and move forward with the change to registry deps. The conservative users are still on 2.9. The ones who moved to 3.0 are probably already on 3.1, and will shortly follow to 3.2. No one reported the bug when we introduced it without noticing weeks ago. Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805327#comment-13805327
]
Braden Shepherdson commented on CB-5201:
The WebView component on Android, which Cordova uses, is based on the old
Android Browser, which sucks. However, if you target at least Android 3.0, and
set hardwareAccelerated=true *in the right place* (the application
element), then it should accelerate properly, at least if you're not using
overflow: scroll (and maybe even if you do, not sure).
See
http://stackoverflow.com/questions/11653936/scrolling-performance-in-webview-for-android-jelly-bean-4-1-x
for a discussion of the problem. This is targeting an older version of
Cordova/Phonegap, but the necessary settings in the AndroidManifest.xml are the
same.
Scrolling produces artifacts on android
---
Key: CB-5201
URL: https://issues.apache.org/jira/browse/CB-5201
Project: Apache Cordova
Issue Type: Bug
Components: Android
Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
android:hardwareAccelerated=true
Reporter: Vunda Von
Fix For: 3.1.0
Real simple example here with a long list of items. As you scroll, you'll
notice that the items are blank at either end you are scrolling towards. On
a larger list with pictures and text, you can see so much tearing and
tiling as you scroll. This does not happen in chrome web browser, only
cordova apps.
{code}
!DOCTYPE html
html
head
titleFoo/title
/head
body
divHeader/div
ul id=foo style=height:300px; overflow:auto;
/ul
divFooter/div
script
for(var i=0; i 1000; i++){
var foo = document.createElement('li');
foo.innerHTML = i;
document.getElementById('foo').appendChild(foo);
}
/script
/body
/html
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Braden Shepherdson resolved CB-5201.
Resolution: Invalid
Not a Cordova problem, the WebView just requires handholding.
Scrolling produces artifacts on android
---
Key: CB-5201
URL: https://issues.apache.org/jira/browse/CB-5201
Project: Apache Cordova
Issue Type: Bug
Components: Android
Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
android:hardwareAccelerated=true
Reporter: Vunda Von
Fix For: 3.1.0
Real simple example here with a long list of items. As you scroll, you'll
notice that the items are blank at either end you are scrolling towards. On
a larger list with pictures and text, you can see so much tearing and
tiling as you scroll. This does not happen in chrome web browser, only
cordova apps.
{code}
!DOCTYPE html
html
head
titleFoo/title
/head
body
divHeader/div
ul id=foo style=height:300px; overflow:auto;
/ul
divFooter/div
script
for(var i=0; i 1000; i++){
var foo = document.createElement('li');
foo.innerHTML = i;
document.getElementById('foo').appendChild(foo);
}
/script
/body
/html
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[
https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805334#comment-13805334
]
Mike Billau commented on CB-5196:
-
Hmmm so all of the WebWorks API's were folded into the Blackberry plugins
listed in the repo above?
If the WebWorks SDK is not compatible with Cordova 3.X, does that mean the only
way to access the WebWorks API is to install these plugins?
Is this documented anywhere? I was looking on edge but can't find anything
talking about installing these new plugins in order to continue to use
functionality that was just there from the WebWorks SDK. I can help with this
documentation if needed...We could probably create a new guide like Using
WebWorks APIs (blackberry.invoke) and link to this guide in the Blackberry
Platform Guide [1] and BB10 Command Line Tools [2]?
[1]http://cordova.apache.org/docs/en/edge/guide_platforms_blackberry10_index.md.html#BlackBerry%2010%20Platform%20Guide
[2]http://cordova.apache.org/docs/en/edge/guide_platforms_blackberry10_tools.md.html#BlackBerry%2010%20Command-line%20Tools
BB10 invoke() plugin is shadowded by cordova.js
---
Key: CB-5196
URL: https://issues.apache.org/jira/browse/CB-5196
Project: Apache Cordova
Issue Type: Bug
Components: BlackBerry
Affects Versions: 3.1.0
Environment: Blackberry 10
Reporter: Mike Billau
Attachments: bbInvoke.html
Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to
call any BB API, webworks.js needs to be included in the html file.
The problem is that there does not seem to be a way to call invoke():
1. Create a simple BB10 app using the attached HTML file,
2. Add feature to the config.xml: feature id=blackberry.invoke
name=blackberry.invoke value=blackberry.invoke/
3. Run the app. Press the button; the browser window doesn't open.
4. Edit the HTML file and place the cordova.js script before webworks.js
script
5. Run the app again, and there is a popup saying: Error intializing
cordova:undefined. After dismissing the alert, you can press the button and
the browser opens just fine.
Analysis:
Internally blackberry.invoke.invoke() ('invoke' plugin) calls
*window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where
the problem is: *window.webworks* is defined in both cordova.js and
webworks.js.The one in cordova.js doesn't have 'event' function whereas it is
available in window.webworks of webworks.js. Hence when webworks.js is loaded
after cordova.js, it works fine and not if it is reversed.
Even though it works when we put webworks.js first we need to squash the
alert() and make sure cordova initializes correctly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5102) Memory leaks when resizing the photo on WP8
[
https://issues.apache.org/jira/browse/CB-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805347#comment-13805347
]
Jonathan Naguin commented on CB-5102:
-
It seems that saving to disk has memory leaks too, so I have rewritten the code
of SaveImageToLocalStorage as well. Notice that now it accepts a Stream. Also
I removed the code related with the rotation...
{code}
/// summary
/// Saves captured image in isolated storage
/// /summary
/// param name=imageFileNameimage file name/param
/// returnsImage path/returns
private string SaveImageToLocalStorage(Stream stream, string
imageFileName)
{
if (stream == null)
{
throw new ArgumentNullException(imageBytes);
}
try
{
var isoFile = IsolatedStorageFile.GetUserStoreForApplication();
if (!isoFile.DirectoryExists(isoFolder))
{
isoFile.CreateDirectory(isoFolder);
}
string filePath = System.IO.Path.Combine(/// + isoFolder +
/, imageFileName);
using (IsolatedStorageFileStream outputStream =
isoFile.CreateFile(filePath))
{
//use photo's actual width height if user doesn't provide
width height
if (cameraOptions.TargetWidth 0
cameraOptions.TargetHeight 0)
{
BitmapImage objBitmap = new BitmapImage();
objBitmap.SetSource(stream);
objBitmap.CreateOptions = BitmapCreateOptions.None;
WriteableBitmap objWB = new WriteableBitmap(objBitmap);
objBitmap.UriSource = null;
try
{
objWB.SaveJpeg(outputStream, objWB.PixelWidth,
objWB.PixelHeight, 0, cameraOptions.Quality);
}
finally
{
//Dispose bitmaps immediately, they are memory
expensive
DisposeImage(objBitmap);
DisposeImage(objWB);
GC.Collect();
}
}
else
{
//Resize
BitmapImage objBitmap = new BitmapImage();
objBitmap.SetSource(stream);
objBitmap.CreateOptions = BitmapCreateOptions.None;
WriteableBitmap objWB = new WriteableBitmap(objBitmap);
objBitmap.UriSource = null;
//Keep proportionally
double ratio =
Math.Min((double)cameraOptions.TargetWidth / objWB.PixelWidth,
(double)cameraOptions.TargetHeight / objWB.PixelHeight);
int width = Convert.ToInt32(ratio * objWB.PixelWidth);
int height = Convert.ToInt32(ratio * objWB.PixelHeight);
try
{
// resize the photo with user defined TargetWidth
TargetHeight
objWB.SaveJpeg(outputStream, width, height, 0,
cameraOptions.Quality);
}
finally
{
//Dispose bitmaps immediately, they are memory
expensive
DisposeImage(objBitmap);
DisposeImage(objWB);
GC.Collect();
}
}
}
return new Uri(filePath, UriKind.Relative).ToString();
}
catch (Exception)
{
//TODO: log or do something else
throw;
}
}
{code}
Memory leaks when resizing the photo on WP8
---
Key: CB-5102
URL: https://issues.apache.org/jira/browse/CB-5102
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera, WP7, WP8
Affects Versions: 3.1.0
Environment: Nokia Lumia 925 running WP8
Reporter: Jonathan Naguin
Assignee: Jesse MacFadyen
Priority: Critical
Labels: camera, memory-leak, wp7, wp8
I was testing the Camera on WP8 and I found memory problems using this code
several times (5 to 10):
{code}
var _options = {
quality: 50,
destinationType: Camera.DestinationType.DATA_URL,
sourceType: Camera.PictureSourceType.CAMERA,
allowEdit: false,
encodingType: Camera.EncodingType.PNG,
saveToPhotoAlbum: false,
correctOrientation:
[jira] [Commented] (CB-5196) BB10 invoke() plugin is shadowded by cordova.js
[
https://issues.apache.org/jira/browse/CB-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805375#comment-13805375
]
Bryan Higgins commented on CB-5196:
---
Yep, that would be great.
I've written up a post which should hit the bb developer blog soon. It has
links to all of the relevant API docs and would be a good source to base the
cordova docs on.
BB10 invoke() plugin is shadowded by cordova.js
---
Key: CB-5196
URL: https://issues.apache.org/jira/browse/CB-5196
Project: Apache Cordova
Issue Type: Bug
Components: BlackBerry
Affects Versions: 3.1.0
Environment: Blackberry 10
Reporter: Mike Billau
Attachments: bbInvoke.html
Our users need to invoke blackberry.invoke.invoke(). As per WebWorks doc, to
call any BB API, webworks.js needs to be included in the html file.
The problem is that there does not seem to be a way to call invoke():
1. Create a simple BB10 app using the attached HTML file,
2. Add feature to the config.xml: feature id=blackberry.invoke
name=blackberry.invoke value=blackberry.invoke/
3. Run the app. Press the button; the browser window doesn't open.
4. Edit the HTML file and place the cordova.js script before webworks.js
script
5. Run the app again, and there is a popup saying: Error intializing
cordova:undefined. After dismissing the alert, you can press the button and
the browser opens just fine.
Analysis:
Internally blackberry.invoke.invoke() ('invoke' plugin) calls
*window.webworks.event.isOn()* in blackberry.invoke/client.js. This is where
the problem is: *window.webworks* is defined in both cordova.js and
webworks.js.The one in cordova.js doesn't have 'event' function whereas it is
available in window.webworks of webworks.js. Hence when webworks.js is loaded
after cordova.js, it works fine and not if it is reversed.
Even though it works when we put webworks.js first we need to squash the
alert() and make sure cordova initializes correctly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805495#comment-13805495
]
Vunda Von commented on CB-5201:
---
When you say target 3.0, do you mean give targetSdkVersion a value of 11?
(http://en.wikipedia.org/wiki/Android_version_history#Android_3.0_Honeycomb_.28API_level_11.29)
Scrolling produces artifacts on android
---
Key: CB-5201
URL: https://issues.apache.org/jira/browse/CB-5201
Project: Apache Cordova
Issue Type: Bug
Components: Android
Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
android:hardwareAccelerated=true
Reporter: Vunda Von
Fix For: 3.1.0
Real simple example here with a long list of items. As you scroll, you'll
notice that the items are blank at either end you are scrolling towards. On
a larger list with pictures and text, you can see so much tearing and
tiling as you scroll. This does not happen in chrome web browser, only
cordova apps.
{code}
!DOCTYPE html
html
head
titleFoo/title
/head
body
divHeader/div
ul id=foo style=height:300px; overflow:auto;
/ul
divFooter/div
script
for(var i=0; i 1000; i++){
var foo = document.createElement('li');
foo.innerHTML = i;
document.getElementById('foo').appendChild(foo);
}
/script
/body
/html
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5201) Scrolling produces artifacts on android
[
https://issues.apache.org/jira/browse/CB-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805498#comment-13805498
]
Vunda Von commented on CB-5201:
---
That solution from stackoverflow did not work for me.
Just tested this with
{code}
uses-sdk android:minSdkVersion=9 android:targetSdkVersion=11 /
{code}
and
{code}
application android:debuggable=true android:hardwareAccelerated=true
android:icon=@drawable/icon android:label=@string/app_name
{code}
and the issue still occurs.
Scrolling produces artifacts on android
---
Key: CB-5201
URL: https://issues.apache.org/jira/browse/CB-5201
Project: Apache Cordova
Issue Type: Bug
Components: Android
Environment: Android Galaxy S4 Active, 4.2.2, Cordova 3.1 cli,
android:hardwareAccelerated=true
Reporter: Vunda Von
Fix For: 3.1.0
Real simple example here with a long list of items. As you scroll, you'll
notice that the items are blank at either end you are scrolling towards. On
a larger list with pictures and text, you can see so much tearing and
tiling as you scroll. This does not happen in chrome web browser, only
cordova apps.
{code}
!DOCTYPE html
html
head
titleFoo/title
/head
body
divHeader/div
ul id=foo style=height:300px; overflow:auto;
/ul
divFooter/div
script
for(var i=0; i 1000; i++){
var foo = document.createElement('li');
foo.innerHTML = i;
document.getElementById('foo').appendChild(foo);
}
/script
/body
/html
{code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CB-5198) Plugins with dependency's will fail with cordova 3.0
[ https://issues.apache.org/jira/browse/CB-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805524#comment-13805524 ] Steve Gill commented on CB-5198: Makes sense to me. Like you said no one reported it. So 3.0.0 is officially broken. We should leave a note on the docs telling people to update. Maybe a blog post? I will move forward with plugins release + tooling Plugins with dependency's will fail with cordova 3.0 Key: CB-5198 URL: https://issues.apache.org/jira/browse/CB-5198 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer, Plugin Media Capture Affects Versions: 3.0.0 Reporter: Steve Gill Fix For: 3.2.0 The two plugins above have a dependency tag that downloads from the registry. Cordova 3.0.0 doesn't have support for downloading from the registry. If someone with cordova 3.0.0 installs the file-transfer plugin (using the git url since that was the suggested way for 3.0), it will fail in installing the dependency due to lack of registry support. Suggestions Bump the major version of these plugins and set engine tag to 3.1.0 Change 3.0 docs to suggest downloading based of 3.0.0 tag instead of from master. Ex. cordova plugin add https://git-wip-us.apache.org/repos/asf/cordova-plugin-file-transfer.git#3.0.0 (I am having trouble with this right now, figuring out why) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5203) Using XmlHTTPRequest.open on WP8 raises a TypeError
Björn Andersson created CB-5203:
---
Summary: Using XmlHTTPRequest.open on WP8 raises a TypeError
Key: CB-5203
URL: https://issues.apache.org/jira/browse/CB-5203
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.1.0
Environment: Windows 8, MS Visual Studio Express 2012 for Windows
Phone version 11.0.60610.01 Update 3. .NET version 4.5.50709. Weinre
2.0.0-pre-HH0SN197
Reporter: Björn Andersson
Assignee: Jesse MacFadyen
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{/code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{/code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{/code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5203) Using XmlHTTPRequest.open on WP8 raises a TypeError
[
https://issues.apache.org/jira/browse/CB-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Andersson updated CB-5203:
Description:
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{/code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{/code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{/code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
was:
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{/code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{/code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{/code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
Using XmlHTTPRequest.open on WP8 raises a TypeError
---
Key: CB-5203
URL: https://issues.apache.org/jira/browse/CB-5203
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.1.0
Environment: Windows 8, MS Visual Studio Express 2012 for Windows
Phone version 11.0.60610.01 Update 3. .NET version 4.5.50709. Weinre
2.0.0-pre-HH0SN197
Reporter: Björn Andersson
Assignee: Jesse MacFadyen
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{/code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{/code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{/code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CB-5203) Using XmlHTTPRequest.open on WP8 raises a TypeError
[
https://issues.apache.org/jira/browse/CB-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Andersson updated CB-5203:
Description:
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
was:
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{/code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{/code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{/code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
Using XmlHTTPRequest.open on WP8 raises a TypeError
---
Key: CB-5203
URL: https://issues.apache.org/jira/browse/CB-5203
Project: Apache Cordova
Issue Type: Bug
Components: WP8
Affects Versions: 3.1.0
Environment: Windows 8, MS Visual Studio Express 2012 for Windows
Phone version 11.0.60610.01 Update 3. .NET version 4.5.50709. Weinre
2.0.0-pre-HH0SN197
Reporter: Björn Andersson
Assignee: Jesse MacFadyen
Using the {{cordova-app-hello-world}} code on a WP8 device, connected to the
device through weinre, trying to use XMLHTTPRequest like this:
{code:language=javascript}
var xhr = new XMLHttpRequest();
xhr.open('GET', 'js/index.js', true);
xhr.send();
console.log(xhr.responseText);
{code}
An error is raised at {{xhr.open}}: {{TypeError: Object doesn't support
property or method 'addEventListener'}}
The same code on iOS runs through and shows me the content of {{index.js}}.
Changing the call to:
{code:javascript}
var xhr = new XMLHttpRequest();
xhr._url = 'js/index.js';
xhr.send();
console.log(xhr.responseText);
{code}
Returns the expected result.
I also noticed that {{XMLHttpRequest.prototype.open}} does not match the code
in {{cordovalib\XHRHelper.cs}}:
{code:title=XMLHttpRequest.prototype.open|javascript}
function() {
var result;
callBeforeHooks(hookSite, this, arguments);
try {
result = func.apply(this, arguments);
} catch (e) {
callExceptHooks(hookSite, this, arguments, e);
throw e;
} finally {
callAfterHooks(hookSite, this, arguments, result);
}
return result;
}
{code}
GitHub repository with the code I used:
https://github.com/gaqzi/cordova-wp8-xhr-test
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CB-5204) remove extra FirefoxOS column header in compatibility table
Mike Sierra created CB-5204: --- Summary: remove extra FirefoxOS column header in compatibility table Key: CB-5204 URL: https://issues.apache.org/jira/browse/CB-5204 Project: Apache Cordova Issue Type: Bug Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Minor an extra column head got inserted, with no corresponding content in the rest of the table. Insert column comment it out throughout -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3808) Rework Documentation
[ https://issues.apache.org/jira/browse/CB-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sierra updated CB-3808: Issue Type: Task (was: Bug) Rework Documentation Key: CB-3808 URL: https://issues.apache.org/jira/browse/CB-3808 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Critical Labels: doc Metabug for doc re-org. Current doc is a combination of confusing, incomplete, disorganized, or outdated. Users need doc that details development alternatives such as the CLI, and clarifies high-level messages. Target audience is a web-aware developer potentially unfamiliar with details of native SDKs. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-4080) modify CSS to improve presentation
[ https://issues.apache.org/jira/browse/CB-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sierra updated CB-4080: Issue Type: Task (was: Bug) modify CSS to improve presentation -- Key: CB-4080 URL: https://issues.apache.org/jira/browse/CB-4080 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Minor Metabug for anything that improves the skin -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CB-3937) configure CSS for compatibility tables
[ https://issues.apache.org/jira/browse/CB-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Sierra updated CB-3937: Issue Type: Task (was: Bug) configure CSS for compatibility tables -- Key: CB-3937 URL: https://issues.apache.org/jira/browse/CB-3937 Project: Apache Cordova Issue Type: Task Components: Docs Reporter: Mike Sierra Assignee: Mike Sierra Priority: Minor For Overview section, format embedded HTML table cells classed y/n with green/red background, check/X mark, etc. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CB-5205) cordova command line help doesn't mention 4th argument for template override
Raymond Camden created CB-5205: -- Summary: cordova command line help doesn't mention 4th argument for template override Key: CB-5205 URL: https://issues.apache.org/jira/browse/CB-5205 Project: Apache Cordova Issue Type: Bug Reporter: Raymond Camden Priority: Minor At the command line, when you run cordova and get the printed help, the create command does not mention the new (supposedly, it isn't working for me but is documented as fixed) 4th argument to let you override the default template. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4967) device-motion
[ https://issues.apache.org/jira/browse/CB-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805704#comment-13805704 ] James Long commented on CB-4967: Hey, a few more commits were added to my repo. Zalun and I fixed a few small bugs and added the timestamp (that's why the test was failing). I got the mobilespec app up and running now and am making sure all tests pass for the plugins I work on. See this: http://jlongster.com/s/accel-tests.png This bug is officially resolved. Going through the other plugins now. device-motion - Key: CB-4967 URL: https://issues.apache.org/jira/browse/CB-4967 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Device Motion Environment: firefoxos Reporter: Piotr Zalewa Assignee: Steve Gill I started development of the Accelerator https://github.com/zalun/cordova-plugin-device-motion I've got issues on FxOS device, works on Android (via Firefox browser) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4967) device-motion
[ https://issues.apache.org/jira/browse/CB-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805705#comment-13805705 ] James Long commented on CB-4967: Mean to paste link to my repo: https://github.com/jlongster/cordova-plugin-device-motion device-motion - Key: CB-4967 URL: https://issues.apache.org/jira/browse/CB-4967 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Device Motion Environment: firefoxos Reporter: Piotr Zalewa Assignee: Steve Gill I started development of the Accelerator https://github.com/zalun/cordova-plugin-device-motion I've got issues on FxOS device, works on Android (via Firefox browser) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805721#comment-13805721 ] James Long commented on CB-4966: All the tests pass except one: https://github.com/apache/cordova-mobile-spec/blob/master/autotest/tests/notification.tests.js#L29 How do plugin dependencies work? Do we have to add the vibration plugin for this to work? Actually, I just noticed that vibration isn't even listed as a plugin in the documentation. Is vibration a part of the notification plugin? That seems weird. dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4966) dialog
[ https://issues.apache.org/jira/browse/CB-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805726#comment-13805726 ] Steve Gill commented on CB-4966: No need to worry about dependencies in this case. They used to be one plugin but have been broken out to two. You can easy plugin add the vibration plugin and then the tests would pass. I have merged this in onto the dev branch dialog -- Key: CB-4966 URL: https://issues.apache.org/jira/browse/CB-4966 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Dialogs Environment: firefoxos Reporter: Piotr Zalewa I started developing it - only the CSS is left - no idea how to conect it to main CSS (is it needed?) https://github.com/zalun/cordova-plugin-dialogs -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4967) device-motion
[ https://issues.apache.org/jira/browse/CB-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805727#comment-13805727 ] Steve Gill commented on CB-4967: Testing myself now device-motion - Key: CB-4967 URL: https://issues.apache.org/jira/browse/CB-4967 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Device Motion Environment: firefoxos Reporter: Piotr Zalewa Assignee: Steve Gill I started development of the Accelerator https://github.com/zalun/cordova-plugin-device-motion I've got issues on FxOS device, works on Android (via Firefox browser) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-4967) device-motion
[ https://issues.apache.org/jira/browse/CB-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805742#comment-13805742 ] Steve Gill commented on CB-4967: Strangely test 4 and 8 failed for me. Then I ran it again and they passed. I ran it again and only test 8 failed. Meh. I am merging in the changes now onto dev. Quick note for both [~jlongster] and [~zalun]. When you guys do commits on the repos, it would be super handy if you can prefix the commit with the issue number. So any commits you make on the device motion plugin, prefix the commit message with CB-4967. That way, when I merge the changes in, it will post comments on the issue itself linking to the commit. Very handy for tracking issues. device-motion - Key: CB-4967 URL: https://issues.apache.org/jira/browse/CB-4967 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Device Motion Environment: firefoxos Reporter: Piotr Zalewa Assignee: Steve Gill I started development of the Accelerator https://github.com/zalun/cordova-plugin-device-motion I've got issues on FxOS device, works on Android (via Firefox browser) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CB-5188) Plugins Release - Oct 24 2013
[ https://issues.apache.org/jira/browse/CB-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805761#comment-13805761 ] Steve Gill commented on CB-5188: This release has commits on all of the core plugins. Plugins Release - Oct 24 2013 - Key: CB-5188 URL: https://issues.apache.org/jira/browse/CB-5188 Project: Apache Cordova Issue Type: Task Reporter: Steve Gill Assignee: Steve Gill -- This message was sent by Atlassian JIRA (v6.1#6144)
