3 ms·

Woke up to see my project here on HN, cool :) We just released the alpha, and there are some really important things on our roadmap for the next few weeks: And

• tehwebguy 13y ago
  Out of curiosity why not use standard scrolling on iOS?
  • yesimahuman 13y ago
    We do support it, you can set overflow-scroll="true" on a content area to use it(http://ionicframework.com/docs/angularjs/views/content/ http://ionicframework.com/docs/angularjs/views/content/) But -webkit-overflow-scrolling: touch has some limitations. For one, you don't receive scroll events after a flick when the finger has left the screen. There are also some very strange issues in the mobile browsers with it, it's a buggy solution right now. In order to build some of the more interesting UI things like pull to refresh, and then list virtualization (i.e. only rendering the active subset), it made sense to have more control over the scrolling operation. But that was a decision I made a few weeks back so I might be wrong, and I would love to use the browser scrolling if possible.
    • emilsjolander 13y ago
      Using custom scrolling behaviour makes the lists feel very out of place on android where a end of list bounce is not the correct visual cue
      • yesimahuman 13y ago
        Yea, I'm thinking we will apply a platform-specific rule to those certain components, because I agree with you. One Android-specific thing we added was left-aligned header bars, but it's only a start. Android support is probably 70% of the iOS support right now, just given time constraints for the alpha.