You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2022. It is now read-only.
Current behavior:
Having infinite scroll, calling content.scrollToTop() before last content.scrollToTop() resolves, throws an un-catchable error, and breaks the app.
ERROR TypeError: Cannot read property 'timeStamp' of null
at InfiniteScroll._onScroll (infinite-scroll.ts:233)
at SafeSubscriber.schedulerFn [as _next] (event_emitter.ts:121)
at SafeSubscriber.__tryOrUnsub (Subscriber.ts:254)
at SafeSubscriber.next (Subscriber.ts:204)
at Subscriber._next (Subscriber.ts:135)
at Subscriber.next (Subscriber.ts:95)
at EventEmitterProxy.Subject.next (Subject.ts:61)
at EventEmitterProxy.EventEmitter.emit (event_emitter.ts:80)
at ScrollView.scroll.onScroll (content.ts:437)
at ScrollView.setScrolling (scroll-view.ts:74)
Expected behavior:
Either be able to catch the error, or better yet don't error.
Ionic version: (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ... (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Having infinite scroll, calling
content.scrollToTop()
before lastcontent.scrollToTop()
resolves, throws an un-catchable error, and breaks the app.Expected behavior:
Either be able to catch the error, or better yet don't error.
Steps to reproduce:
Plunker: http://plnkr.co/edit/ptdHfTMhBxwvAOOUvizQ?p=preview
Steps:
scrollToTop
twice fastYou can do it only once though (per refresh), because it kills the thread.
Ionic info: (run
ionic info
from a terminal/cmd prompt and paste output below):The text was updated successfully, but these errors were encountered: