Ah now it is clear, thank you for explaining. You guys are amazing. I apologize for my ignorance :P
On Saturday, June 14, 2014 12:01:00 PM UTC-7, Scott Miles wrote: > > >> when used with "-webkit-overflow-scrolling: touch" > > The method used to make touch-scrolling smooth on iOS includes eliminating > the chance for JavaScript to do anything. So by definition, this flag is > incompatible with `core-list`, which is attempting to virtualize large > lists via JavaScript. > > >> should we expect any type of official scroller component in the future? > > Yes. > > >> "-webkit-overflow-scrolling: touch" has mostly eliminated the need for > fancy JS scrolling optimizations or simulations but that positioning, > snapping, pull to refresh, zooming, infinite scrolling, etc are common nice > to haves > > I believe that statement is in opposition to itself. As above, native > touch-scrolling disables JavaScript, and removes the ability to implement > any of the 'common nice to haves', and therefore requires 'fancy JS > scrolling' is required to have any custom behavior. > > Optimizing core-list and improving scroll behaviors is one of our major > goals, stay tuned for updates. > > Scott > > On Tue, Jun 10, 2014 at 11:44 AM, <[email protected] <javascript:>> wrote: > >> core-list appears to break on iOS (items stop being rendered) when used >> with "-webkit-overflow-scrolling: touch". Is enabling smooth mobile >> scrolling in the works for it? >> >> Also curious around the plan for mobile scrolling in general - should we >> expect any type of official scroller component in the future? I'm not >> completely current on the state of mobile scrolling/lists but my >> understanding is that "-webkit-overflow-scrolling: touch" mostly eliminated >> the need for fancy JS scrolling optimizations or simulations but that >> positioning, snapping, pull to refresh, zooming, infinite scrolling, etc >> are common nice to haves in a scroller widget. Or is this something we >> should plan to handle ourselves? >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 >> --- >> You received this message because you are subscribed to the Google Groups >> "Polymer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/4e6c892c-dbc3-4a71-aa50-7f2552dab1ba%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/4e6c892c-dbc3-4a71-aa50-7f2552dab1ba%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/601e111a-999d-4676-b27d-b367bfabfcf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
