Closed GoogleCodeExporter closed 8 years ago
Please upgrade to the latest version (2.0) and check if the problem still occurs
Original comment by diosla...@gmail.com
on 4 Jul 2012 at 11:22
We have upgraded to mobiscrol 2.0. But still the problem persists.
This prob doesn't come in iphone. Only in android s2
Original comment by fatemaka...@gmail.com
on 4 Jul 2012 at 11:25
Plzz suggest some solution for this the problem still persists
Original comment by fatemaka...@gmail.com
on 29 Aug 2012 at 7:55
Does it occur on demo.mobiscroll.com also?
I cannot test on galaxy s2, but it is working ok on galaxy s plus and galaxy s3
Original comment by diosla...@gmail.com
on 29 Aug 2012 at 8:49
its working fine on browser. Even in iphone its not having any problem only in
galaxy s2 the problem is occuring. i have seen the mobiscroll.js also and this
problem occurs only when the dw_cancel click function is not fired.
Original comment by fatemaka...@gmail.com
on 29 Aug 2012 at 10:59
We are encountering this issue as well - on some Android 2.2, 2.3 devices.
It appears to happen when mobiscroll is appearing on top of buttons.
The Set / Cancel actions are not firing.
Original comment by philipjo...@gmail.com
on 28 Sep 2012 at 3:13
I am encountering the same issue as well. - on ice cream device.
it is weird. if i added max 2 mobilescroll on a page, it works fine. but if i
added more than 2, then those set/cancel button doesn't work anymore... it
never gets fired.
Original comment by joseph.h...@gmail.com
on 24 Nov 2012 at 2:34
This might be related to Issue 96
If you are using position: fixed elements on the page, the Android ICS browser
mixes up the z-indexes.
Original comment by diosla...@gmail.com
on 26 Nov 2012 at 1:10
thanks for your quick reply. I just check through all CSS in my project and I
found that there's no any position:fixed element on the page. Even I create my
own customized button on the page, once the mobiescroll pops up, the button is
no longer working as well.
Original comment by joseph.h...@gmail.com
on 26 Nov 2012 at 7:01
i found a solution for it.
if you rewrite the button click event to touchstart/touchend, then it seems to
be working.
onShow:function(html, inst){
$('.dwb-s', html).on('touchend', function(){
// code here.
});
}
Original comment by joseph.h...@gmail.com
on 26 Nov 2012 at 7:42
Fixed in 2.4.4
Original comment by diosla...@gmail.com
on 23 Feb 2013 at 8:57
Original issue reported on code.google.com by
fatemaka...@gmail.com
on 4 Jul 2012 at 11:16