- This topic has 6 replies, 3 voices, and was last updated 11 years, 1 month ago by support-octavio.
-
AuthorPosts
-
dabbeljuMemberHi all,
I am facing an interesting problem.
I have a native APP and build iOS and Android version of it.
In TestCenter and iOS everything works great! But on Android I have a problem (so far I can see an all Android versions):
Im am loading some htnl stuff and put it into an div. On top of the page I have a header bat and at the bottom a nav bar.
Between the two bars I have an html widget, where I put the loaded html in. And I am using iScroll to make the html page scrollable.
The problem on Androidf is: When I try to scroll, before the html is fully loaded, the whole page (including both bars) is scrolling. Once the html is loaded, it stops doing that. But if you have for example the nav bar in the middle of the screen, it will remain there, even if I switch sites.
The iScroller is not the problem. I tried already to disable it and I have the same problem. Obviously I can not scroll in the html anymore but the problem still exists.
Any thoughts from someone?
Thanks and best regards
Christian
support-michaelKeymasterPlease post a “small” example that demonstrates the problem. Then we can investigate and see what’s goofed.
dabbeljuMemberHi Wayne,
I did strip everything out quick and dirty, which is not interesting for the problem. The problem is reproducable on android.
Please find attached a zip file containing all project files.
Thanks and best regards.
Dabbelju
Attachments:
You must be logged in to view attached files.
support-michaelKeymasterwill give it a look shortly. In the meantime please share more details about your test environment:
1) what android device?
2) what android version?
dabbeljuMemberHi Wayne,
my Test Device is a HTC Desire S S510e.
Android Version 2.3.5.It also happens on other Devices with other Android Version.
Looking forward to your answer.
Best regards and a nice weekend.
Dabbelju
dabbeljuMemberAny news?
support-octavioMemberHi Dabbelju,
This is in the queue for deeper investigation. It is one of those special cases that stalled. Mainly our dev team has been over allocated getting core improvements and this got bumped way down on their priority list. I will bump it up again but based on current commitments I’m sure it will not be investigated until next week at the soonest after we roll out 2.5m3.
-
AuthorPosts