lopespm / mobiscroll

Automatically exported from code.google.com/p/mobiscroll
1 stars 0 forks source link

MobiScroll is not compatible with jquery mobile 1.0 #95

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Using the demo code included with mobiscroll 2.0 download, replace jquery 
1.7 and jquery mobile 1.1 scripts and styles with jquery 1.6.4 and jquery 
mobile 1.0
2. Run in your favorite desktop browser
3. Try to use the control

What is the expected output? What do you see instead?
Expected: function as the live demo
Actual: not functional, button click invokes popup but +/-, save and cancel 
buttons are non responsive and a click anywhere dismisses the popup.

What version of the product are you using? On what operating system?
1.6, 2.0 rc1, 2.0

Please provide any additional information below.

Original issue reported on code.google.com by MyMinds...@gmail.com on 30 May 2012 at 12:21

GoogleCodeExporter commented 8 years ago
Thanks for the report!

The problem only occurs when using the 'jqm' theme.
It can be easily fixed with a few lines of css:

.jqm .dw {
    z-index: 1003;
}
.jqm .dwv {
    position: static;
    width: auto;
}​

Here is a live example: http://jsfiddle.net/E3rP7/1/

The fix will be included in the next bugfix release (2.0.1)

Original comment by diosla...@gmail.com on 30 May 2012 at 5:47

GoogleCodeExporter commented 8 years ago
I have verified that this fix works in my sample app. Thanks for the quick 
response, and thanks for reading my mind about which theme I was using!

Original comment by MyMinds...@gmail.com on 30 May 2012 at 11:43

GoogleCodeExporter commented 8 years ago
Thanks for that fix, it solves the problem straight away.  I'm using jQuery 
Mobile Splitview plugin, which is locked to jQM ver. 1 so this fix will solve 
the issue for any one using JQM splitview and mobiscroll with QM theme

Original comment by brown.j....@gmail.com on 20 Jul 2012 at 9:20

GoogleCodeExporter commented 8 years ago
Fixed in 2.0.1

Original comment by diosla...@gmail.com on 26 Jul 2012 at 9:54