[jira] [Created] (CB-7490) InAppBrowser manual tests crashes application on windows platform
Vladimir Kotikov created CB-7490: Summary: InAppBrowser manual tests crashes application on windows platform Key: CB-7490 URL: https://issues.apache.org/jira/browse/CB-7490 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Environment: Windows 8/8.1/WP8.1 device. Reporter: Vladimir Kotikov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7490) InAppBrowser manual tests crashes application on windows platform
[ https://issues.apache.org/jira/browse/CB-7490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-7490: - Description: Mobilespec application crashes when trying to start InAppBrowser plugin manual tests. When opened in Visual Studio, following error message is shown before failure: !https://raw.githubusercontent.com/MSOpenTech/winstore-jscompat/master/error.PNG?token=3019602__eyJzY29wZSI6IlJhd0Jsb2I6TVNPcGVuVGVjaC93aW5zdG9yZS1qc2NvbXBhdC9tYXN0ZXIvZXJyb3IuUE5HIiwiZXhwaXJlcyI6MTQwNjU3OTYyOX0%3D--101970399d1c4e94bbe251e71e78f8be6af6d7ba! Problem is that manipulating DOM using innerHtml property of elemets is considered unsafe on windows platform and may cause exceptions, when injected HTM is invalid or contains unsafe elements. was: Mobilespec application crashes when trying to start Camera plugin manual tests. When opened in Visual Studio, following error message is shown before failure: !https://raw.githubusercontent.com/MSOpenTech/winstore-jscompat/master/error.PNG?token=3019602__eyJzY29wZSI6IlJhd0Jsb2I6TVNPcGVuVGVjaC93aW5zdG9yZS1qc2NvbXBhdC9tYXN0ZXIvZXJyb3IuUE5HIiwiZXhwaXJlcyI6MTQwNjU3OTYyOX0%3D--101970399d1c4e94bbe251e71e78f8be6af6d7ba! Problem is that manipulating DOM using innerHtml property of elemets is considered unsafe on windows platform and may cause exceptions, when injected HTM is invalid or contains unsafe elements. InAppBrowser manual tests crashes application on windows platform - Key: CB-7490 URL: https://issues.apache.org/jira/browse/CB-7490 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Environment: Windows 8/8.1/WP8.1 device. Reporter: Vladimir Kotikov Mobilespec application crashes when trying to start InAppBrowser plugin manual tests. When opened in Visual Studio, following error message is shown before failure: !https://raw.githubusercontent.com/MSOpenTech/winstore-jscompat/master/error.PNG?token=3019602__eyJzY29wZSI6IlJhd0Jsb2I6TVNPcGVuVGVjaC93aW5zdG9yZS1qc2NvbXBhdC9tYXN0ZXIvZXJyb3IuUE5HIiwiZXhwaXJlcyI6MTQwNjU3OTYyOX0%3D--101970399d1c4e94bbe251e71e78f8be6af6d7ba! Problem is that manipulating DOM using innerHtml property of elemets is considered unsafe on windows platform and may cause exceptions, when injected HTM is invalid or contains unsafe elements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7490) InAppBrowser manual tests crashes application on windows platform
[ https://issues.apache.org/jira/browse/CB-7490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-7490: - Description: Mobilespec application crashes when trying to start Camera plugin manual tests. When opened in Visual Studio, following error message is shown before failure: !https://raw.githubusercontent.com/MSOpenTech/winstore-jscompat/master/error.PNG?token=3019602__eyJzY29wZSI6IlJhd0Jsb2I6TVNPcGVuVGVjaC93aW5zdG9yZS1qc2NvbXBhdC9tYXN0ZXIvZXJyb3IuUE5HIiwiZXhwaXJlcyI6MTQwNjU3OTYyOX0%3D--101970399d1c4e94bbe251e71e78f8be6af6d7ba! Problem is that manipulating DOM using innerHtml property of elemets is considered unsafe on windows platform and may cause exceptions, when injected HTM is invalid or contains unsafe elements. InAppBrowser manual tests crashes application on windows platform - Key: CB-7490 URL: https://issues.apache.org/jira/browse/CB-7490 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Environment: Windows 8/8.1/WP8.1 device. Reporter: Vladimir Kotikov Mobilespec application crashes when trying to start Camera plugin manual tests. When opened in Visual Studio, following error message is shown before failure: !https://raw.githubusercontent.com/MSOpenTech/winstore-jscompat/master/error.PNG?token=3019602__eyJzY29wZSI6IlJhd0Jsb2I6TVNPcGVuVGVjaC93aW5zdG9yZS1qc2NvbXBhdC9tYXN0ZXIvZXJyb3IuUE5HIiwiZXhwaXJlcyI6MTQwNjU3OTYyOX0%3D--101970399d1c4e94bbe251e71e78f8be6af6d7ba! Problem is that manipulating DOM using innerHtml property of elemets is considered unsafe on windows platform and may cause exceptions, when injected HTM is invalid or contains unsafe elements. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7491) Bridge manual tests page crashes mobilespec app on windows platform
Vladimir Kotikov created CB-7491:
Summary: Bridge manual tests page crashes mobilespec app on
windows platform
Key: CB-7491
URL: https://issues.apache.org/jira/browse/CB-7491
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Environment: Windows8/8.1/WP8.1 device
Reporter: Vladimir Kotikov
When user clicks on Non-plugin automatic tests - Run bridge tests in
mobilespec application on windows platform, app crashes.
Origin is {{reportSuiteResults()}} method in HtmlReporter, which tries to call
method of {{reporterView}} object which is undefined since Bridge tests suite
contains no specs (on windows) and due to this instance of {{reporterView}} is
not created.
Possible fix - add check for {{reporterView === undefined}} in
{{reportSuiteResults}} method
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-7491) Bridge manual tests page crashes mobilespec app on windows platform
[
https://issues.apache.org/jira/browse/CB-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-7491:
-
Component/s: (was: Plugin TestFramework)
Bridge manual tests page crashes mobilespec app on windows platform
---
Key: CB-7491
URL: https://issues.apache.org/jira/browse/CB-7491
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Environment: Windows8/8.1/WP8.1 device
Reporter: Vladimir Kotikov
When user clicks on Non-plugin automatic tests - Run bridge tests in
mobilespec application on windows platform, app crashes.
Origin is {{reportSuiteResults()}} method in HtmlReporter, which tries to
call method of {{reporterView}} object which is undefined since Bridge tests
suite contains no specs (on windows) and due to this instance of
{{reporterView}} is not created.
Possible fix - add check for {{reporterView === undefined}} in
{{reportSuiteResults}} method
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-7491) Bridge manual tests page crashes mobilespec app on windows platform
[
https://issues.apache.org/jira/browse/CB-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-7491:
-
Labels: bridge mobilespec windows (was: )
Bridge manual tests page crashes mobilespec app on windows platform
---
Key: CB-7491
URL: https://issues.apache.org/jira/browse/CB-7491
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Environment: Windows8/8.1/WP8.1 device
Reporter: Vladimir Kotikov
Labels: bridge, mobilespec, windows
When user clicks on Non-plugin automatic tests - Run bridge tests in
mobilespec application on windows platform, app crashes.
Origin is {{reportSuiteResults()}} method in HtmlReporter, which tries to
call method of {{reporterView}} object which is undefined since Bridge tests
suite contains no specs (on windows) and due to this instance of
{{reporterView}} is not created.
Possible fix - add check for {{reporterView === undefined}} in
{{reportSuiteResults}} method
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CB-7492) Plugman does not return error
John M. Wargo created CB-7492: - Summary: Plugman does not return error Key: CB-7492 URL: https://issues.apache.org/jira/browse/CB-7492 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 3.5.0 Environment: Microsoft Windows 7 64-bit, Node 0.10.30 Reporter: John M. Wargo I'm trying to use plugman for the first time and when I enter the command I'm experimenting with, no matter what I try on the command line, all plugman does is bring up the help file. For example, I'm using the following command: plugman --platform android --project plug1 --plugin org.apache.cordova.console Instead of telling me that there's an error with the command I've entered, it simply displays nothing except for the help file. This is not behavior I'm expecting - what I expect is an error message letting me know that I've done something wrong. Showing the help file should happen when no parameters are passed to the command or when help is requested. C:\Users\jwargo\dev\plugtestplugman -v 0.22.4 C:\Users\jwargo\dev\plugtestnpm uninstall -g plugman unbuild plugman@0.22.4 C:\Users\jwargo\dev\plugtestnpm install -g plugman C:\Users\jwargo\AppData\Roaming\npm\plugman - C:\Users\jwargo\AppData\Roaming\n pm\node_modules\plugman\main.js plugman@0.22.4 C:\Users\jwargo\AppData\Roaming\npm\node_modules\plugman +-- q@0.9.7 +-- underscore@1.4.4 +-- nopt@1.0.10 (abbrev@1.0.5) +-- rc@0.3.0 (ini@1.1.0, deep-extend@0.2.11, optimist@0.3.7) +-- cordova-lib@0.21.6 (osenv@0.0.3, properties-parser@0.2.3, bplist-parser@0.0. 5, mime@1.2.11, semver@2.0.11, dep-graph@1.1.0, plist-with-patches@0.5.1, npmcon f@0.1.16, shelljs@0.1.4, glob@3.2.11, xcode@0.6.6, elementtree@0.1.5, tar@0.1.19 , request@2.22.0, cordova-js@3.6.2) +-- npm@1.3.4 As you can see, plugman is reporting it's version 0.22.4, but JIRA won't let me select this as the version on this ticket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
Vladimir Kotikov created CB-7493: Summary: Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125512#comment-14125512 ] ASF GitHub Bot commented on CB-7493: GitHub user vladimir-kotikov opened a pull request: https://github.com/apache/cordova-windows/pull/43 CB-7493 Adds 'space-in-path' and 'unicode in name' tests for CI Fix for https://issues.apache.org/jira/browse/CB-7493 You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-windows CB-7493 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-windows/pull/43.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #43 commit a12a0f58820057f52976466385babe48c26d3b1c Author: Vladimir Kotikov v-vlk...@microsoft.com Date: 2014-09-08T14:02:44Z CB-7493 Adds 'space-in-path' and 'unicode in name' tests for CI Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125513#comment-14125513 ] ASF GitHub Bot commented on CB-7493: GitHub user vladimir-kotikov opened a pull request: https://github.com/apache/cordova-wp8/pull/57 CB-7493 Adds 'space-in-path' and 'unicode in name' tests for CI Fix for https://issues.apache.org/jira/browse/CB-7493 You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-wp8 CB-7493 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-wp8/pull/57.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #57 commit 08e99982c7284090e08761e442b89463cd107450 Author: Vladimir Kotikov v-vlk...@microsoft.com Date: 2014-09-08T14:05:05Z CB-7493 Adds 'space-in-path' and 'unicode in name' tests for CI Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125526#comment-14125526 ] Jason Chase commented on CB-7459: - See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Jason Chase Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125526#comment-14125526 ] Jason Chase edited comment on CB-7459 at 9/8/14 2:25 PM: - See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Tested changes on multiple Android devices (v4.4.3 and v4.1), and IOS simulator. Not tested on other platforms. was (Author: chasej): See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Jason Chase Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-7459: --- Assignee: Michal Mocny (was: Jason Chase) For your review. Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
Vladimir Kotikov created CB-7494:
Summary: cordova-windows fails to build app with unicode name
using cordova/build.bat script
Key: CB-7494
URL: https://issues.apache.org/jira/browse/CB-7494
Project: Apache Cordova
Issue Type: Bug
Components: Windows
Reporter: Vladimir Kotikov
Repro steps (in cordova-windows repo):
windows\bin\create testcreate 応用 com.test.app 応用
.windows\testcreate 応用\cordova\build
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest validation
failed. Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot
a valid ASCII Windows ID. It must contain one or more parts, separated with
periods, where each part contains only characters a-z, A-Z, 0-9, and does no t
start with a digit. [d:\cordova\cordova-windows\windows\testcreate
応用\CordovaApp.Windows80.jsproj]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[
https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-7494:
-
Description:
Repro steps (in cordova-windows repo):
windows\bin\create testcreate 応用 com.test.app 応用
.windows\testcreate 応用\cordova\build
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest validation
failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a valid
ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong places
at *.manifest files
was:
Repro steps (in cordova-windows repo):
windows\bin\create testcreate 応用 com.test.app 応用
.windows\testcreate 応用\cordova\build
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest validation
failed. Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot
a valid ASCII Windows ID. It must contain one or more parts, separated with
periods, where each part contains only characters a-z, A-Z, 0-9, and does no t
start with a digit. [d:\cordova\cordova-windows\windows\testcreate
応用\CordovaApp.Windows80.jsproj]
{noformat}
cordova-windows fails to build app with unicode name using cordova/build.bat
script
---
Key: CB-7494
URL: https://issues.apache.org/jira/browse/CB-7494
Project: Apache Cordova
Issue Type: Bug
Components: Windows
Reporter: Vladimir Kotikov
Repro steps (in cordova-windows repo):
windows\bin\create testcreate 応用 com.test.app 応用
.windows\testcreate 応用\cordova\build
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest
validation failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a
valid ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong
places at *.manifest files
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125582#comment-14125582 ] ASF GitHub Bot commented on CB-7493: Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-windows/pull/43#issuecomment-54827614 The test fails due to issue https://issues.apache.org/jira/browse/CB-7494. Will be fixed soon. Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7495) Docs. Add guide to embed CordovaView on WP8
Sergey Grebnov created CB-7495: -- Summary: Docs. Add guide to embed CordovaView on WP8 Key: CB-7495 URL: https://issues.apache.org/jira/browse/CB-7495 Project: Apache Cordova Issue Type: Improvement Components: Docs, WP8 Reporter: Sergey Grebnov Assignee: Sergey Grebnov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[
https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-7494:
-
Description:
Repro steps (in cordova-windows repo):
{{windows\bin\create testcreate 応用 com.test.app 応用}}
{{.windows\testcreate 応用\cordova\build}}
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest validation
failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a valid
ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong places
at *.manifest files
was:
Repro steps (in cordova-windows repo):
windows\bin\create testcreate 応用 com.test.app 応用
.windows\testcreate 応用\cordova\build
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest validation
failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a valid
ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong places
at *.manifest files
cordova-windows fails to build app with unicode name using cordova/build.bat
script
---
Key: CB-7494
URL: https://issues.apache.org/jira/browse/CB-7494
Project: Apache Cordova
Issue Type: Bug
Components: Windows
Reporter: Vladimir Kotikov
Repro steps (in cordova-windows repo):
{{windows\bin\create testcreate 応用 com.test.app 応用}}
{{.windows\testcreate 応用\cordova\build}}
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest
validation failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a
valid ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong
places at *.manifest files
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7495) Docs. Add guide to embed CordovaView on WP8
[ https://issues.apache.org/jira/browse/CB-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125631#comment-14125631 ] ASF GitHub Bot commented on CB-7495: GitHub user sgrebnov opened a pull request: https://github.com/apache/cordova-docs/pull/231 CB-7495 Docs. Add guide to embed CordovaView on WP8 https://issues.apache.org/jira/browse/CB-7495 Also updated links to Windows and Windows Phone 8 plugins development guides (to be consistent with new naming convention) : * Windows Phone - Windows Phone 8 * Windows 8 - Windows You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs CB-7495 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/231.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #231 commit 38a3ad396e8e081400166df50fbaa636265c7cfa Author: sgrebnov v-seg...@microsoft.com Date: 2014-09-08T14:16:34Z Windows Phone 8.0 WebViews commit a0a720de1206970ca38be073661d72e386c67e13 Author: sgrebnov v-seg...@microsoft.com Date: 2014-09-08T14:33:33Z refined links to Windows and WP8 plugins guides Docs. Add guide to embed CordovaView on WP8 --- Key: CB-7495 URL: https://issues.apache.org/jira/browse/CB-7495 Project: Apache Cordova Issue Type: Improvement Components: Docs, WP8 Reporter: Sergey Grebnov Assignee: Sergey Grebnov -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125635#comment-14125635 ] ASF GitHub Bot commented on CB-7493: Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-windows/pull/43#issuecomment-54829957 Already fixed in https://github.com/apache/cordova-windows/pull/44 Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[
https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125634#comment-14125634
]
ASF GitHub Bot commented on CB-7494:
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-windows/pull/44
CB-7494 Fixes wrong replacements in *.appxmanifest files
Fix for https://issues.apache.org/jira/browse/CB-7494
Fixes cordova/build script failure when project's name contain unicode and
config.xml is empty (e.g. when project created using bin/create script)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-windows CB-7494
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-windows/pull/44.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #44
commit fdce7411529e3630f6b7c17f9942a3113ba67c6e
Author: Vladimir Kotikov v-vlk...@microsoft.com
Date: 2014-09-08T14:36:40Z
CB-7494 Fixes wrong replacements in *.appxmanifest files
cordova-windows fails to build app with unicode name using cordova/build.bat
script
---
Key: CB-7494
URL: https://issues.apache.org/jira/browse/CB-7494
Project: Apache Cordova
Issue Type: Bug
Components: Windows
Reporter: Vladimir Kotikov
Repro steps (in cordova-windows repo):
{{windows\bin\create testcreate 応用 com.test.app 応用}}
{{.windows\testcreate 応用\cordova\build}}
Expected:
App builds successfully.
Actual:
{noformat}
package.windows80.appxmanifest(35,22): error APPX3032: App manifest
validation failed.
Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a
valid ASCII Windows ID.
It must contain one or more parts, separated with periods, where each part
contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
[d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
{noformat}
This doesn't affects CLI
The reason is that bin/create script write app name and app id in wrong
places at *.manifest files
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CB-7496) Plugman doesn't respect --link option
Martin Bektchiev created CB-7496: Summary: Plugman doesn't respect --link option Key: CB-7496 URL: https://issues.apache.org/jira/browse/CB-7496 Project: Apache Cordova Issue Type: Bug Components: Plugman Reporter: Martin Bektchiev There is support for a --link option for the install command which instead of copying the plugin should make a symbolic link to its original location but it's not working. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7383) [Release + 3.6.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125671#comment-14125671 ] ASF subversion and git services commented on CB-7383: - Commit 5dd6874c31c4821af8cda210549242e677b228e3 in cordova-lib's branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=5dd6874 ] CB-7383 Bump the platform version numbers to 3.6.1 [Release + 3.6.0] Parent Issue -- Key: CB-7383 URL: https://issues.apache.org/jira/browse/CB-7383 Project: Apache Cordova Issue Type: Task Components: Amazon FireOS, Android, App Hello World, BlackBerry, CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 Reporter: Steve Gill Assignee: Jesse MacFadyen Fix For: 3.6.0 Parent bug for the 3.6.0 Cordova Release. Workflow here: http://wiki.apache.org/cordova/CuttingReleases Release Master: ? Component Leads: Refer to assignee of Test Tag sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7496) Plugman doesn't respect --link option
[ https://issues.apache.org/jira/browse/CB-7496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125672#comment-14125672 ] ASF GitHub Bot commented on CB-7496: GitHub user mbektchiev opened a pull request: https://github.com/apache/cordova-lib/pull/85 CB-7496 Fix --link option for plugman install There is support for a --link option for the install command which instead of copying the plugin should make a symbolic link to its original location but it's not working. refs https://issues.apache.org/jira/browse/CB-7496 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Icenium/cordova-lib bektchiev/fix-install-link-option Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/85.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #85 commit 434c3abfc3561109b4391e439dc6afe86bffdc71 Author: Martin Bektchiev martin.bektch...@telerik.com Date: 2014-09-08T11:21:21Z CB-7496 Fix --link option for plugman install Plugman doesn't respect --link option - Key: CB-7496 URL: https://issues.apache.org/jira/browse/CB-7496 Project: Apache Cordova Issue Type: Bug Components: Plugman Reporter: Martin Bektchiev There is support for a --link option for the install command which instead of copying the plugin should make a symbolic link to its original location but it's not working. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7383) [Release + 3.6.0] Parent Issue
[ https://issues.apache.org/jira/browse/CB-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125674#comment-14125674 ] ASF subversion and git services commented on CB-7383: - Commit bc04dfb1f033c1858a76c01e8281ace371a91b68 in cordova-lib's branch refs/heads/rb_0.21.10 from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=bc04dfb ] CB-7383 Bump the platform version numbers to 3.6.1 (cherry picked from commit 5dd6874c31c4821af8cda210549242e677b228e3) [Release + 3.6.0] Parent Issue -- Key: CB-7383 URL: https://issues.apache.org/jira/browse/CB-7383 Project: Apache Cordova Issue Type: Task Components: Amazon FireOS, Android, App Hello World, BlackBerry, CLI, CordovaJS, CordovaLib, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 Reporter: Steve Gill Assignee: Jesse MacFadyen Fix For: 3.6.0 Parent bug for the 3.6.0 Cordova Release. Workflow here: http://wiki.apache.org/cordova/CuttingReleases Release Master: ? Component Leads: Refer to assignee of Test Tag sub-tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7497) Crash on open app from fresh
Miquel created CB-7497: -- Summary: Crash on open app from fresh Key: CB-7497 URL: https://issues.apache.org/jira/browse/CB-7497 Project: Apache Cordova Issue Type: Bug Components: Plugin SplashScreen Environment: ios7 iphone 4s Reporter: Miquel Everytime the app is fresh opened (not in the debugger) Error: *** Terminating app due to uncaught exception 'NSRangeException', reason: 'Cannot remove an observer CDVSplashScreen 0x15d6f010 for the key path frame from UIView 0x15e614b0 because it is not registered as an observer.' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7498) No method for vibrateWithPattern
Miquel created CB-7498: -- Summary: No method for vibrateWithPattern Key: CB-7498 URL: https://issues.apache.org/jira/browse/CB-7498 Project: Apache Cordova Issue Type: Bug Components: Plugin Vibration Environment: ios7 iphone 4s Reporter: Miquel The method is not present: vibrateWithPattern. It should just vibrate as in ios7 it is not possible to vibrateWithPattern. vibrateWithPattern exists in Android and moreover, vibrate it is marked as deprecated in the plugin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7497) Crash on open app from fresh
[
https://issues.apache.org/jira/browse/CB-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125763#comment-14125763
]
Miquel commented on CB-7497:
For the moment resolved with a @try {} @catch block in CDVSplashScreen.m:
Original:
[self.viewController.view removeObserver:self forKeyPath:@frame];
[self.viewController.view removeObserver:self forKeyPath:@bounds];
Patch:
@try {
[self.viewController.view removeObserver:self forKeyPath:@frame];
}
@catch (NSException *exception) {
NSLog(@frame observer was not attached);
}
@try {
[self.viewController.view removeObserver:self forKeyPath:@bounds];
}
@catch (NSException *exception) {
NSLog(@bounds observer was not attached);
}
Crash on open app from fresh
Key: CB-7497
URL: https://issues.apache.org/jira/browse/CB-7497
Project: Apache Cordova
Issue Type: Bug
Components: Plugin SplashScreen
Environment: ios7 iphone 4s
Reporter: Miquel
Everytime the app is fresh opened (not in the debugger)
Error: *** Terminating app due to uncaught exception 'NSRangeException',
reason: 'Cannot remove an observer CDVSplashScreen 0x15d6f010 for the key
path frame from UIView 0x15e614b0 because it is not registered as an
observer.'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7492) Plugman does not return error
[ https://issues.apache.org/jira/browse/CB-7492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125772#comment-14125772 ] John M. Wargo commented on CB-7492: --- I tried this on OS X and have the same issue - it clearly doens't like my command line arguments, but isn't telling me anything except to simply display the help file. When I try to create a new plugin, I get the following error: Object #Object has no method 'help' Plugman does not return error - Key: CB-7492 URL: https://issues.apache.org/jira/browse/CB-7492 Project: Apache Cordova Issue Type: Bug Components: Plugman Affects Versions: 3.5.0 Environment: Microsoft Windows 7 64-bit, Node 0.10.30 Reporter: John M. Wargo I'm trying to use plugman for the first time and when I enter the command I'm experimenting with, no matter what I try on the command line, all plugman does is bring up the help file. For example, I'm using the following command: plugman --platform android --project plug1 --plugin org.apache.cordova.console Instead of telling me that there's an error with the command I've entered, it simply displays nothing except for the help file. This is not behavior I'm expecting - what I expect is an error message letting me know that I've done something wrong. Showing the help file should happen when no parameters are passed to the command or when help is requested. C:\Users\jwargo\dev\plugtestplugman -v 0.22.4 C:\Users\jwargo\dev\plugtestnpm uninstall -g plugman unbuild plugman@0.22.4 C:\Users\jwargo\dev\plugtestnpm install -g plugman C:\Users\jwargo\AppData\Roaming\npm\plugman - C:\Users\jwargo\AppData\Roaming\n pm\node_modules\plugman\main.js plugman@0.22.4 C:\Users\jwargo\AppData\Roaming\npm\node_modules\plugman +-- q@0.9.7 +-- underscore@1.4.4 +-- nopt@1.0.10 (abbrev@1.0.5) +-- rc@0.3.0 (ini@1.1.0, deep-extend@0.2.11, optimist@0.3.7) +-- cordova-lib@0.21.6 (osenv@0.0.3, properties-parser@0.2.3, bplist-parser@0.0. 5, mime@1.2.11, semver@2.0.11, dep-graph@1.1.0, plist-with-patches@0.5.1, npmcon f@0.1.16, shelljs@0.1.4, glob@3.2.11, xcode@0.6.6, elementtree@0.1.5, tar@0.1.19 , request@2.22.0, cordova-js@3.6.2) +-- npm@1.3.4 As you can see, plugman is reporting it's version 0.22.4, but JIRA won't let me select this as the version on this ticket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CB-3071) App cache is invalidated after complete restart of an app
[ https://issues.apache.org/jira/browse/CB-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Grieve reopened CB-3071: --- Possible work-around is to keep the UA stable: http://markmail.org/thread/ibucv3jeyekk5vxo App cache is invalidated after complete restart of an app - Key: CB-3071 URL: https://issues.apache.org/jira/browse/CB-3071 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.5.0 Reporter: Shazron Abdullah Assignee: Shazron Abdullah Attachments: apache server 200 on GET requests from IOS Cordova client.pdf, apache server 304 on GET requests from cordova client.pdf, headers I have this report from a developer: We've recently upgraded from 2.2 to 2.5 on IOS. In 2.2, our application leveraged cached assets after a complete restart of the application. In 2.5 the same scenario always requests new assets from the web server. The web server has not changed, and it returns caching instructions with the content. Once the application is running, the cached assets are utilized as we expect. Is this by design? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CB-7439) Android Javascript androidExec online events callback messages delayed
[
https://issues.apache.org/jira/browse/CB-7439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve resolved CB-7439.
---
Resolution: Duplicate
Android Javascript androidExec online events callback messages delayed
--
Key: CB-7439
URL: https://issues.apache.org/jira/browse/CB-7439
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS
Affects Versions: 3.5.0
Environment: Android 4.2 + Android 4.4 (presumably others)
Reporter: Paul Maddox
I have an app where I'm calling:
{noformat}
navigator.notification.confirm
{noformat}
from org.apache.cordova.dialogs 0.2.9. The dialog is displayed fine, however
on my Android test devices upon pressing a dialog button my callback function
sometimes isn't executed. My iOS test devices are fine.
I believe I've tracked this down to an issue with Android's JS
implementation, however I don't have quite enough knowledge of Cordova to
ascertain the root cause or fix it properly.
Naturally, navigator.notification.confirm calls androidExec. This in turn
makes a native API call. The thing I'm unsure about is the following events:
{noformat}
// The network module takes care of firing online and offline events.
// It currently fires them only on document though, so we bridge them
// to window here (while first listening for exec()-releated
online/offline
// events).
window.addEventListener('online', pollOnceFromOnlineEvent, false);
window.addEventListener('offline', pollOnceFromOnlineEvent, false);
cordova.addWindowEventHandler('online');
cordova.addWindowEventHandler('offline');
document.addEventListener('online', proxyEvent, false);
document.addEventListener('offline', proxyEvent, false);
{noformat}
When I press one of the confirm dialog buttons the event listener
pollOnceFromOnlineEvent is called, which retrieves messages from the native
API and processes them accordingly. However it seems the online event doesn't
always work. I'm not sure why we're using the online event in the first place
though..
Now, there's a nasty side-effect as well. In androidExec itself, after making
the native API call, we actually call processMessages, so we may get our
callback, but delayed!
What should happen:
{quote}
call confirm() -- calls androidExec -- calls processMessages (no messages)
-- user button press -- online event -- calls pollOnceFromOnlineEvent --
calls processMessages -- calls callback
{quote}
What actually happens is:
{quote}
call confirm() -- calls androidExec -- calls processMessages (no messages)
-- user button press -- NO online event
.. time passes ..
call confirm() -- calls androidExec -- calls processMessages (got
message!!) -- calls callback -- user button press -- NO online event
.. and the bad cycle continues.
{quote}
I believe some points to consider are:
* Is the online event being used properly
* The android JS implementation seems to support polling mode - should we be
using this?
* Should androidExec be processing messages immediately after the native API
call?
I've put this as an issue with 3.5.0, as that's what my app is running and
can readily repro it, however it also existed on 3.4.x.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7447) createmobilespec.js should have an option to use global plugins when testing a platforms/tools release
[ https://issues.apache.org/jira/browse/CB-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126004#comment-14126004 ] ASF subversion and git services commented on CB-7447: - Commit 6acca3f978b9059137002e743fa1b41b17b20143 in cordova-mobile-spec's branch refs/heads/3.5.x from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=6acca3f ] CB-7447 Add --globalplugins option to 3.5.x ...to help test the released plugins with the 3.6.x platforms createmobilespec.js should have an option to use global plugins when testing a platforms/tools release -- Key: CB-7447 URL: https://issues.apache.org/jira/browse/CB-7447 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: 3.7.0 When doing tests for a platforms/tools release, since plugins aren't updated, the platforms/tools should be tested against the latest released plugins instead of the master branch of plugins. So the suggestion is to add a new option to createmobilespec.js to create a test project that uses the local git repo for platforms and tools, but downloads the plugins from the registry (latest). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126016#comment-14126016 ] Jason Chase commented on CB-7459: - I've added another commit to the pull request to address the review feedback. Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7499) Cordova dialogs should support BIDI text
Mike Billau created CB-7499:
---
Summary: Cordova dialogs should support BIDI text
Key: CB-7499
URL: https://issues.apache.org/jira/browse/CB-7499
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin Dialogs
Affects Versions: Master
Reporter: Mike Billau
Assignee: Mike Billau
Priority: Minor
Since API 19, Andorid has had the facilities to deal with bidirectional text,
however, current Cordova notification implementation does not correctly handle
bidirectional text in dialogs.
We can see this is the case by first setting the language to Hebrew and then
launching the following dialogs:
navigator.notification.confirm(Pure English !!!, function(){}, 7);
navigator.notification.confirm(עברית היא שפה מדוברת בIsrael !,
function(){}, 8);
Since we are in Hebrew, the base text direction will be RTL. This means that
when we see the second notification with the Hebrew text, it will be
right-justified. When we click and see the Pure English !!! notication,
because locale is RTL, we should expect to see: !!! Pure English and it
should be right-justified, however, we still see Pure English !!!, left
justified.
http://w3-03.ibm.com/globalization/page/publish/4353
Ideally you should be able to just add android:supportsRtl=true to the
manifest, however, this is doesn't seem to ne enough without setting the text
direction to the locale for all of the dialogs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7158) Geolocation not working when built with Xcode 6
[ https://issues.apache.org/jira/browse/CB-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126313#comment-14126313 ] ASF GitHub Bot commented on CB-7158: Github user shazron commented on the pull request: https://github.com/apache/cordova-plugin-geolocation/pull/21#issuecomment-54903964 @weili-feedhenry thanks for the patch! Just confirming that this is you on the list for ppl that have submitted an iCLA: http://people.apache.org/committer-index.html Geolocation not working when built with Xcode 6 --- Key: CB-7158 URL: https://issues.apache.org/jira/browse/CB-7158 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Affects Versions: Master Environment: Xcode 6, IOS 8 Beta 3 Reporter: Eric Weiterman When a project is built using Xcode 6 for IOS 8 the geolocation plugin seems to be failing. I created a mobilespec project from Master and first noticed that the geolocation automated tests were failing. I then tried the geolocadtion manual tests which also failed. I then created a sample plain Cordova project and tried to see if I could use getCurrentPosition(..). The first call to it did nothing but subsequent calls saw it returning the error callback. Geolocation works for both mobilespec and my sample project if I use Xcode 5.1.1 to build the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7158) Geolocation not working when built with Xcode 6
[ https://issues.apache.org/jira/browse/CB-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126317#comment-14126317 ] Shazron Abdullah commented on CB-7158: -- Ignore my previous comment -- should have read it better :P Geolocation not working when built with Xcode 6 --- Key: CB-7158 URL: https://issues.apache.org/jira/browse/CB-7158 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Affects Versions: Master Environment: Xcode 6, IOS 8 Beta 3 Reporter: Eric Weiterman When a project is built using Xcode 6 for IOS 8 the geolocation plugin seems to be failing. I created a mobilespec project from Master and first noticed that the geolocation automated tests were failing. I then tried the geolocadtion manual tests which also failed. I then created a sample plain Cordova project and tried to see if I could use getCurrentPosition(..). The first call to it did nothing but subsequent calls saw it returning the error callback. Geolocation works for both mobilespec and my sample project if I use Xcode 5.1.1 to build the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7158) Geolocation not working when built with Xcode 6
[ https://issues.apache.org/jira/browse/CB-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126358#comment-14126358 ] ASF subversion and git services commented on CB-7158: - Commit 4102a332b0c6b0c3513370a4c030a32e46a51e10 in cordova-plugin-geolocation's branch refs/heads/master from [~weilifeedhenry] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=4102a33 ] CB-7158 - Fix geolocation for ios 8 Signed-off-by: Shazron Abdullah shaz...@apache.org Geolocation not working when built with Xcode 6 --- Key: CB-7158 URL: https://issues.apache.org/jira/browse/CB-7158 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Affects Versions: Master Environment: Xcode 6, IOS 8 Beta 3 Reporter: Eric Weiterman When a project is built using Xcode 6 for IOS 8 the geolocation plugin seems to be failing. I created a mobilespec project from Master and first noticed that the geolocation automated tests were failing. I then tried the geolocadtion manual tests which also failed. I then created a sample plain Cordova project and tried to see if I could use getCurrentPosition(..). The first call to it did nothing but subsequent calls saw it returning the error callback. Geolocation works for both mobilespec and my sample project if I use Xcode 5.1.1 to build the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-6911) Geolocation fails in iOS 8 - deprecated attempt to access property errors
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126357#comment-14126357 ] ASF subversion and git services commented on CB-6911: - Commit 3bc05a423d064413d6d15e68e4f14417d823318c in cordova-plugin-geolocation's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=3bc05a4 ] Revert CB-6911 partially (keeping Info.plist key installation for iOS 8) Geolocation fails in iOS 8 - deprecated attempt to access property errors --- Key: CB-6911 URL: https://issues.apache.org/jira/browse/CB-6911 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Environment: iOS 8 beta 1 Reporter: Jeff Schilling Assignee: Shazron Abdullah Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot 2014-09-04 at 9.30.58 pm.png references to window.navigator.* (platform, geolocation) etc fail with Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CB-7158) Geolocation not working when built with Xcode 6
[ https://issues.apache.org/jira/browse/CB-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-7158. -- Resolution: Fixed Assignee: Shazron Abdullah Geolocation not working when built with Xcode 6 --- Key: CB-7158 URL: https://issues.apache.org/jira/browse/CB-7158 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Affects Versions: Master Environment: Xcode 6, IOS 8 Beta 3 Reporter: Eric Weiterman Assignee: Shazron Abdullah When a project is built using Xcode 6 for IOS 8 the geolocation plugin seems to be failing. I created a mobilespec project from Master and first noticed that the geolocation automated tests were failing. I then tried the geolocadtion manual tests which also failed. I then created a sample plain Cordova project and tried to see if I could use getCurrentPosition(..). The first call to it did nothing but subsequent calls saw it returning the error callback. Geolocation works for both mobilespec and my sample project if I use Xcode 5.1.1 to build the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7158) Geolocation not working when built with Xcode 6
[ https://issues.apache.org/jira/browse/CB-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126364#comment-14126364 ] ASF GitHub Bot commented on CB-7158: Github user shazron commented on the pull request: https://github.com/apache/cordova-plugin-geolocation/pull/21#issuecomment-54906754 Patched, thanks! Please close this PR. https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=4102a33 Geolocation not working when built with Xcode 6 --- Key: CB-7158 URL: https://issues.apache.org/jira/browse/CB-7158 Project: Apache Cordova Issue Type: Sub-task Components: Plugin Geolocation Affects Versions: Master Environment: Xcode 6, IOS 8 Beta 3 Reporter: Eric Weiterman Assignee: Shazron Abdullah When a project is built using Xcode 6 for IOS 8 the geolocation plugin seems to be failing. I created a mobilespec project from Master and first noticed that the geolocation automated tests were failing. I then tried the geolocadtion manual tests which also failed. I then created a sample plain Cordova project and tried to see if I could use getCurrentPosition(..). The first call to it did nothing but subsequent calls saw it returning the error callback. Geolocation works for both mobilespec and my sample project if I use Xcode 5.1.1 to build the project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
