Details
-
Type:
Task
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.2 Final
-
Fix Version/s: 1.3 Beta
-
Component/s: None
-
Labels:None
-
Environment:ICEmobile, BlackBerry Z10
Description
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Current Codebase of the Android container running in BB10 runtime has the following issues:
Geolocation - working now that the high precision mode is enabled by default.
MenuButtons - An issue with using absolute positions in the css has been identified. Without those constructs, the container menuButtons and select fields work properly.
CSS and markup - There are some trivial css issues in a few (< 5) pages.
Audio and Video media pages - Some serious issues listed above.
In the native integration pages
--------------------------------
Camcorder page records and uploads fine, but playback fails with the same exception outlined above.
microphone - records and uploads and plays fine, but after clip plays, app crashes with exception outlined above.
Cloud push - working fine.
The rest of the native integration pages all are working.
At this stage I'm convinced the Android-sx container approach in the BB runtime does not work.
https://developer.blackberry.com/cascades/documentation/device_platform/invocation/invocation_framework.html
Looking at the code in the native BB10 invocation target, there's a lot of connecting OS signals to SLOTs for event handling of the invocation. The BB10 plugin would have to interpret the Android Application Manifest where the intent filters are defined and jigger up a similar BAR based invocation scheme. Now that we have the "enable SX" button correctly sniffing OS10, the button shows up, but nothing is triggered in Android-sx when it's pressed.
That's not to say that the sx scheme is not going to work... I had modified the native invocation target manifest to be launched with the "icemobile:" scheme, and it was launched when I clicked the -sx button. The -sx notion is valid, it would have to work with a native bb10 -sx container, and not depend on the existing Android one.
I have found another issue with the Android container in BB runtime. In the Content Stack page, clicking the next and or previous buttons don't navigate anywhere. Clicking on the menuButton to directly select a page does, however.
I see the following in the console log:
Uncaught SyntaxError: Unexpected identifier at http://<ip address:port>/mobileshowcase/showcase.jsf:2
The resource registry problem was the cause of the media tags not working
Every issue with the Android Container in BB10 runtime has been resolved. The platform is not 100% ideal since the port operates on the 2.3 WebView and includes a few of the early bugs that you can see have been resolved in the bb10 native browser but I'm certain this process has been faster than trying to duplicate the Container as a native BB10 application
The BlackBerry Z10 is currently detected as a desktop browser.
User-Agent: Mozilla/5.0 (BB10; Touch) AppleWebKit/537.10+ (KHTML, like Gecko) Version/10.0.9.2372 Mobile Safari/537.10+
Fallback to <input type=file> displays an image picker with the choice to switch to the camera, upload an existing image, or browse other folders.
The upload, however, does not contain the image file. This may be due to existing BlackBerry detection that is no longer correct for BB10.
This is fixed as follows, however it will break FormData detection on the older BlackBerry. This can be retested on BB6 since the FormData bug may be fixed.
+++ jsf/components/component/resources/org.icefaces.component.util/component.js (working copy)
@@ -438,9 +438,7 @@
function () {
jsf.getViewState = html5getViewState;
if ((undefined !== window.FormData) &&
, false);
Push appears to be working well.
Screen width appears to be actual pixel width, resulting in very small text.
Header/footer in mobileshowcase remains attached to the window border, so appears better than iOS browser in that respect.
audio and video playback components cause browser crash. The crash does not occur with a simple test page containing a <video> element, and once the test page is loaded, mobileshowcase no longer crashes.
mobi:geolocation works well with default settings. google map also works.
A native date spinner is supported, but the JavaScript version is currently active. Both are functional, however double clicks on the JavaScript spinner result in page zooming.