-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Start View at Bottom #9237
Comments
There are a good project that do it for angular 1: https://github.com/Luegg/angularjs-scroll-glue And another for angular 2, but seems to be unmaintained: |
I faced the same problem but I was able to solve it by displaying a placeholder view above the chat dialog until the view has finished loading the message items and until the scroll event has finished. |
Maybe you should use http://ionicframework.com/docs/v2/components/#toolbar-buttons |
Hello all! While this is an awesome feature request it is not something that we plan on doing anytime soon. Because of this I am going to move this to our internal feature tracking repo for now as it is just "collecting dust" here. Once we decide to implement this I will move it back. Thanks everyone for using Ionic! |
This issue was moved to driftyco/ionic-feature-requests#82 |
Good news: this feature will be added with PR #8099. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Hi everybody,
This feature would be extremely useful for a chat application, where the user should always see the most recent message first (i.e. the message that's rendered at the bottom of the page).
Currently, in order to workaround this, I have the following:
This isn't a very good workaround though. Sometimes, the user still sees the slight scroll (or rather, since I put
0
inscrollToBottom()
, the user sees a jump to the bottom of the page).Does anyone else have a better workaround at the moment?
The text was updated successfully, but these errors were encountered: