Skip to content

1.1.0-rc.1 showPageLoadingMsg demo does not work for android 2.3.3 #3786

bmurmistro opened this Issue Mar 9, 2012 · 9 comments

4 participants


Tried this on an emulator and my phone without success:
I upgraded my app to 1.1.0-rc.1 and some of my showPageLoadingMsg calls do work in android 2.3.3, but most do not. I haven't tried any other versions of android.



Are you sure it's just not showing up farther down the page? I had that issue when I was playing around with it. I'm actually only able to reproduce on the latest:

Obviously still an issue.

@johnbender johnbender closed this Mar 10, 2012
@johnbender johnbender reopened this Mar 10, 2012

Hi John,

I just tried it again and if I scroll down I do see it on the bottom. I could have sworn it wasn't working at all earlier so I did a little more testing.

Android 2.1 (emulator) - Seemed to work as expected
Android 2.2 (emulator) - Did not work. I did a refresh and it worked fine (including the location of the spinner)
Android 2.3 (htc mytouch) - Tried it again and it didn't work. I did a refresh and it worked fine. (the location of the spinner was at the bottom)
Kindle Fire - Did not work. I did a refresh and it worked fine (including the location of the spinner)

It appears that we have two issues here:

Location of the spinner in 2.3
Loader not showing up in 2.2 and 2.3 ( initial load ... does appear to be somewhat random )

Hope this helps!



It does indeed.


I think this issue may be related:

@johnbender johnbender was assigned Mar 15, 2012

[edit] useless



You can try out my proposed fix by including:

<script src=""></script>

for jquery mobile



That fixes at least part of the issue, and also might speed up our scrolling a bit but really requires your review just to be sure. My grasp of possible height calculation issues is very weak.



You can also test on your android devices by hitting:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.