I've got a webview that I'm displaying that has a couple of Ratchet slider components. I'm noticing that they're nearly un-usable because they'll jerk and jump around as I'm trying to scroll through the options.
Has anyone seen this before? Does anyone have any suggestions on how to fix this?
I haven't seen this issue on iOS, only Android.
Here is a link to the Ratchet documentation.
Related
I am learning reactJS and encountered a weird issue in my web application. When I click a textarea/textfields, the page just randomly scrolls up. But this behavior only happens in android browsers and in android webView.
It looks okay in iOS devices.
Anyone knows why this happens? I have followed a number of suggestions like adding preventDefault() or return false; or even window.scrollTo(0) but none of these works for me.
By the way, I'm using the #react-spring/parallax library if that gives some clue.
Appreciate your ideas! and thank you in advance!
In recent months, I've been developing a Mobile App on Android using Xamarin and MvvmCross.
There is a current issue I've been trying to seek out without any luck.
It's a WebView with some javascript injected. On some devices when you start scrolling a nested list it will also scroll the entire page.
I've changed the website to include the overscroll-y on the elements for the list.
Here are some video examples. If someone could give some insight on why this is happening.
MOTO6: https://youtu.be/-DGOXW2lYOs
Lenovo:
https://youtu.be/ZuxUm1olTpY
I'm building a phonegap(cordova) application and it is working great for android, but there is some scrolling issue with iOS build i-e i cannot scroll pages from anywhere on the screen except the middle-right and middle-left of the screen and that area is very less, i want to scroll by swiping anywhere on the screen just like it works in Android.
Anyone else faces the same issue, share your knowledge and experience.
Although without a code sample it is difficult to advice.. I had similar experiences in ios phonegap development and you need to be sure that the css overflow attribute is correctly setup for all elements.
One major 'trick' that you need is to add
-webkit-overflow-scrolling: touch;
To the container you like to scroll.
See this page for info about the css property.
I'm having problems displaying my club's website, specifically on Android version 4.1 and 4.2's default browser:
http://www.manchesterhandballclub.co.uk/index.html
Everything loads as normal for a split second, before everything in the #maincontent div disappears, except for the Twitter and Facebook widgets on the homepage (/index.html), or the embedded Google Maps on the Training Info page (/training_info.html).
I wondered if there was maybe some sort of z-index issue on load, but there shouldn't be anything overlaying on top of the container div to my knowledge. Here's a preview of what the homepage looks like once the main div disappears:
http://tinypic.com/r/4l1zya/5
I don't have any experience designing for mobile devices, and whilst I do plan to build responsive device-friendly versions eventually, it'd be great if I could get the current site displaying as it does on all other Android versions for now. I'm not sure if there's any version-specific quirks or things I may have missed?
Thanks in advance, and apologies if I've not posted this in the correct way! Tried searching around but can't seem to find any help on the issue currently.
Does anyone have a clue what could cause this behavior? If you view this page on Android 2.3 or Blackberry, you should see the problem.
You can scroll straight past the end of the page to a yellow background that goes on forever. You can also scroll off the right side of the page to do the same thing.
It works fine on Android 4 and iOS 5.
See site with issue here:
http://wwwa1nbkclientsitecom.zippysites.com/
p.s. I asked about this yesterday but with less detail. And I've made some changes sense then, but those didn't fix the problem.
It was the dynamic google map in the footer. It had nothing to do with my page layout or style. Everything I did was fine. Removing the dynamic google map fixed it. SOLUTION: Replace with a STATIC google map. Its kind of bad to be using dynamic map embedded in page for a mobile device anyway.