ICEmobile
  1. ICEmobile
  2. MOBI-441

mobiRefresh breaks device integration with camera and other native activities.

          Details

          • Type: Bug Bug
          • Status: Resolved
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: 1.2 Beta
          • Component/s: Containers, Spring
          • Labels:
            None
          • Environment:
            Android container, icemobliespring

            Description


            A fix to the android container to properly call mobiRefresh() in native-interface.js has adverse side-effects on JSP-based applications, and particularly, calls to camera, camcorder, mic, and QR scan. For instance, when the camera is activated, and takes a picture, the resulting file name is stored in a hidden field, and the thumbnail is set. When returning from the camera activity to the container, onResume() runs, mobiRefresh() is called, and the page is reloaded, wiping out the hidden fields set by the camera interface.

              Activity

              Hide
              Permalink
              Steve Maryka added a comment - - edited

              Seems like maybe the best thing to do in non-icefaces cases is nothing. In android container we could detect returning from camera, etc.. and avoid the page reload in those conditions. Going into history or preferences will also cause onResume() to run, but should that force a page reload? The only time you really need to reload, is if an ajax push has occurred, and even then you don't want to toss away results of the camera activity.

              Show
              Steve Maryka added a comment - - edited Seems like maybe the best thing to do in non-icefaces cases is nothing. In android container we could detect returning from camera, etc.. and avoid the page reload in those conditions. Going into history or preferences will also cause onResume() to run, but should that force a page reload? The only time you really need to reload, is if an ajax push has occurred, and even then you don't want to toss away results of the camera activity.

                People

                • Assignee:
                  Steve Maryka
                  Reporter:
                  Steve Maryka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: