I'm trying to have two lists in a phonegap app on iOS that are scrollable, while there's no bounce, etc. I've set the UIWebBounce to false, and I've trapped the touch events so that only the relevant lists (via element ids) will respond to touch move, but if the list is empty or you're at about the last element of the list, then scrolling the list up scrolls the whole page up. iscroll did not seem to work for me, as it acted very weird in some quick tests.
So, the question is: has anyone gotten a single list or two to be scrollable in PhoneGap/ios while COMPLETELY avoiding scrolls of the whole page, and if so how?
Related
I want to implement a list of events like in the Google Calendar mobile app. When you open the application, the upcoming events are shown, but despite this, you can scroll up and see past events. Is it possible to somehow set an element in the List (i.e. the current date), which will be considered as the beginning of the list to display, but at the same time, when scrolling up, the previous elements of the list were shown?
Vaadin 7.6.2
It appears when you attempt to scroll within a ComboBox, the listing moves a page at a time instead of smoothly scrolling up or down one line at a time, I'd prefer it scroll smoothly one line at a time instead of paging. This possible?
It is not possible with this version of component. But ComboBox have filtering functionality which is useful when you have a lot items in a list.
Probably, solution is to create your own widget.
The bug is described in detail here https://bugs.webkit.org/show_bug.cgi?id=134596
Relevant part is this:
Without Scrolling you should be able to click any of the radio buttons
Now scroll down the page
Trying to click any of the radio buttons on the left results in an
offset click. One of the radio buttons below your click will receive
the event.
Expected: The radio button I clicked on gets focus
Actual: The click event is offset the amount the iframe was scrolled.
Main difference is im not using an iframe, just a div, but the same problem.
If I remove either overflow:auto (but it wont let me scroll then) or -webkit-overflow-scrolling property the correct clicks happen. It looks like it was fixed in a nightly, but this has to work now and for backwards compatibility. Is there a hack to get this to work? My best idea so far is to just not have that -webkit-overflow-scrolling prop for iOS until it works, but that kinda sucks because momentum scrolling is what makes it feel much more like an app.
I have a ons-page element that I want to customize the scrolling for. There are a few things I'd like to achieve, but mostly I want to understand what's going on.
By default, the page has -webkit-overflow-scrolling: touch. This is undesirable for two reasons:
The area "behind" the page shown during overflow is just plain white
I have no hooks to take action on over scroll. I'd like to add pull to refresh mechanics.
I've tried working with iScroll, but the behavior I'm seeing is that if I declare my scrollable element to be inside of the page, it calculates the full element height as the visible height. If I declare my scrollable element to be the page, I can move the page around, but not the content within the page.
I'm guessing some of this is related to "using native scrolling where it can", but I don't really understand how that's implemented, so I'm not really sure.
Any ideas?
Onsen UI doesn't support pull-to refresh as default.
How about using this library?
https://github.com/mgcrea/angular-pull-to-refresh
This is a library for angularJS.
P.S
Now Onsen UI support pull-to-refresh. http://onsen.io/reference/ons-pull-hook.html
I have an app with a ListView showing a list of summary items.
I've added print support, but I'm stuck on splitting my content into different pages.
I can add multiple pages, but I don't know how to split my content into pages based on page size.
Currently I have a xaml user control for my print content with a bound ItemsControl in it. I'd either like to bind to a list of just the items that will fit on the page, or move the top visible item position up based on the page number.
I'm not sure which is the best approach and I'm not sure how to do either.
The only paging example I could find in the docs was for a rich text block, which relies on the RichTextBlockOverflow control. I don't think that will help me.