Commit graph

14 commits

Author SHA1 Message Date
Kin Blas
4c8d7237df Changed the default for the delayedClickEnabled option to false. It was experimental anyways, for Android based browsers, and was breaking link clicking on iOS. 2011-06-22 11:42:37 -07:00
scottjehl
fe3d0b537b updated to use new data method 2011-03-26 16:32:16 -04:00
scottjehl
f78e7b0a6a moved to :jqmData selector 2011-03-26 10:12:16 -04:00
John Bender
4fe0b29a0f Merge branch 'data-namespacing' 2011-03-25 18:46:00 -07:00
Kin Blas
6b7c82a1dc Updated the scrollupdate trigger call to pass an array for the data. Apparently trigger requires an array as its second argument if you want to pass data to a callback. 2011-03-18 13:37:22 -07:00
scottjehl
237db243dd updated the experiments dir to use data-jq namespaces 2011-03-09 20:59:28 -05:00
Kin Blas
49c9db9c49 Turning on delayedClick by default. <again>
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.
2010-12-16 11:04:48 -08:00
Kin Blas
8351f5496b Turn off delayedClickEnabled by default for now. We need to work out some kinks.
Modified sv-test-02.html so that you can dynamically turn on/off the delayedClick behavior.
2010-12-15 11:13:31 -08:00
Kin Blas
58506aeef4 Added code to defer the generation of a "click" event for form elements within a scrollview. This seems to keep form elements working on Android.
Added strict comparisons for strings as pointed out by jonathan in my previous checkin.
2010-12-15 08:06:07 -08:00
Kin Blas
aa1f94a81f Added support for scrolling via scrollTop/scrollLeft.
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".
2010-12-14 16:05:52 -08:00
Kin Blas
22d4f4f687 Removing some debug code I accidentally commited. 2010-12-13 15:34:19 -08:00
Kin Blas
33602a4dfd Implemented view paging for the scrollview. This feature is only enabled for horizontal and vertical scrollviews. To use, pass "xp" or "yp" for the @data-scroll attribute.
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.
2010-12-02 09:47:46 -08:00
Kin Blas
39a9681d55 Implemented support for nested scrollviews, scroll propagation, and direction locking. To make a div scrollable use:
data-scroll="x|y|true"
2010-12-01 14:04:54 -08:00
Kin Blas
dbdfd23541 Initial checkin of experimental support for momentum scrolling. We'd really like native browser support for sub-page scrolling, but until then, we need something.
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.
2010-11-18 15:12:27 -08:00