This makes our include model match the include model on the CDN, and allows devs to make use of mobileinit for debugging some of the samples since that must be set up after jquery.js, but before jquery-mobile.
Added triggers for mousedown and mouse up in the delayed case because some of hte jqm components register handlers on those events to set the component states.
Note that the focus() trigger is commented out temporarily. It seems to cause the content within the scrollview clip to scroll to the point where item being focused sits in the flow .. unfortunately this screws up the rendering because we are using CSS3 translate, so the item clicked on is out of view.
Modified sv-test-02.html so that the clone event sets the target property on the fake event.
Modified sv-test-02.html so that you can dynamically switch the scrolling method used. This will allow us to test the performance of different methods on the different platforms.
Modified scrollview.js so that you can specify @data-scroll-method="translate|position|scroll".
Added a couple of tests that will help us figure out what events need to be handled special to disable native view port scrolling, and what events are necessary for form elements to function properly.
Fixed a typo/bug in scrollview.js that was causing the paging bool to be set improperly.
Turned on scrollview paging in scrollview-direction.html.
Items still left to do:
- Code refactoring/cleanup.
- Modify the code so that scroll offsets are stored as positive values. This will make it easier for folks to understand.
This version supports simulated scrolling via the CSS3 transform property by default, but also supports an option for positioning the old-fashioned way with top and left properties.
Still some code clean-up to do, but folks can start playing with it.
Some items/issues left to look into:
- Experiment with event delegation so we can implement nested scrollviews.
- Implement scroll direction locking.
- Decide whether to conditionally inject clip/view markup.
- Decide on final ui class names.
- Decide on how scrolling behavior is actually invoked. (data-* attribute or class)
- Decide on final set of notifications we'll need to fire off.
- Add an API so that scroll position can be adjusted after a resize/orientation change.
- Documentation that describes potential problems with performance, memory usage, etc, and workarounds.