Response title
This is preview!
jqm 1.2 transition lag
in jQuery Mobile
•
7 months ago
Hey Guys.
I'm doing a bunch more device testing here and there and I notice a pretty good lag in page transition from the time the spinner disappears (i.e. the .ui-loading class removed off of HTML) and the actual paint of the page.
I'm testing on an IPhone 4 (not 4s) with 5.1 installed. I do have some script on these pages, but I've removed it all and I'm getting the same lag. The markup for each of these pages is about 10k and I do have a persistent footer bar. My transitions are left default which is fade.
Basically, I'm running this from localhost and on internal wifi, so I'm a little lost as to what to try next. From the time of click until the time the next page paints is usually between 4.5 and 6 seconds. But, the spinner goes away almost instantly usually which tells me the ajax requests are done instantly.
I don't see a similar delay when I look through sites on the jqm gallery. Though, it seems that almost all of those sites are running on 1.1.1.
Anyone have any idea what's going on from removal of ul-loading and the actual page show? Any ideas as to what might be hanging that for 2-3 seconds?
Also, I had a side question about why JQM is running script on every transition to add the min-height to the page element. Obviously, it's to have it be the full height of the viewport. But, that's not necessary on newer devices! Height: 100% works fine as long as it's containing elements (body and html) are also height 100%. I see alot of bugs around the height of the page being calculated slowly and the white strip you get at the bottom until the script can catch up. Doing this in CSS might also make persistent footers render cleaner (stay at the bottom of the page) for browsers that support fixed positioning.
Thanks for the info.
Steven
I'm doing a bunch more device testing here and there and I notice a pretty good lag in page transition from the time the spinner disappears (i.e. the .ui-loading class removed off of HTML) and the actual paint of the page.
I'm testing on an IPhone 4 (not 4s) with 5.1 installed. I do have some script on these pages, but I've removed it all and I'm getting the same lag. The markup for each of these pages is about 10k and I do have a persistent footer bar. My transitions are left default which is fade.
Basically, I'm running this from localhost and on internal wifi, so I'm a little lost as to what to try next. From the time of click until the time the next page paints is usually between 4.5 and 6 seconds. But, the spinner goes away almost instantly usually which tells me the ajax requests are done instantly.
I don't see a similar delay when I look through sites on the jqm gallery. Though, it seems that almost all of those sites are running on 1.1.1.
Anyone have any idea what's going on from removal of ul-loading and the actual page show? Any ideas as to what might be hanging that for 2-3 seconds?
Also, I had a side question about why JQM is running script on every transition to add the min-height to the page element. Obviously, it's to have it be the full height of the viewport. But, that's not necessary on newer devices! Height: 100% works fine as long as it's containing elements (body and html) are also height 100%. I see alot of bugs around the height of the page being calculated slowly and the white strip you get at the bottom until the script can catch up. Doing this in CSS might also make persistent footers render cleaner (stay at the bottom of the page) for browsers that support fixed positioning.
Thanks for the info.
Steven
1
