Oh, I see. Yes, the Scriptaculous Control.Scrollbar does not respond to touch events.
You have a couple of options. First, you could extend that control to map touchStart and touchEnd at different coordinates to be same as mouseDown and mouseUp at different coordinates. This is going to be fussy, because you also need to track whether the touch start/end resulted in the viewport moving or not. You could also use feature detection to turn off your custom scroll area and use CSS to turn on the one that the platform gives you natively. Of the two, that would be my personal choice. Walter On Aug 23, 2013, at 4:40 AM, Peter Gavrilov wrote: > Sure thing, > > i have prepared the example: > > http://www.peteforpresident.cc/scroll > > -- > You received this message because you are subscribed to the Google Groups > "Prototype & script.aculo.us" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/prototype-scriptaculous. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/prototype-scriptaculous. For more options, visit https://groups.google.com/groups/opt_out.
