GNOME Bugzilla – Bug 713408
"rubberband" fetching older messages
Last modified: 2018-04-12 02:40:15 UTC
---- Reported by geary-maint@gnome.bugs 2012-03-23 16:31:00 -0700 ---- Original Redmine bug id: 4912 Original URL: http://redmine.yorba.org/issues/4912 Searchable id: yorba-bug-4912 Original author: Daniel Fore Original description: At the moment, Geary uses a cool infinite-scroll type method to fetch more (older) messages from the server. It would be cool to give this the kind of "rubberband" effect we see on iOS that would allow a user to see what will happen if they continue scrolling and give them the option not to fetch more mail. Related issues: related to geary - Feature #4911: Scroll up (rubberband) to fetch new mail (Open) ---- Additional Comments From geary-maint@gnome.bugs 2013-01-15 18:05:00 -0800 ---- ### History #### #1 Updated by Adam Dingle over 1 year ago * **Status** changed from _Open_ to _5_ * **Resolution** set to _duplicate_ This looks like a duplicate of #4911. #### #2 Updated by Eric Gregory over 1 year ago * **Status** changed from _5_ to _Open_ * **Resolution** deleted (<strike>_duplicate_</strike>) This isn't a dupe -- #4911 is for fetching new messages, this ticket is for older messages. #### #3 Updated by Daniel Fore over 1 year ago Ah sorry for the confusion. I thought it would be better to open separate bug reports than to group the two :p #### #4 Updated by Jim Nelson 10 months ago * **Subject** changed from _"rubberband" fetching more messages_ to _"rubberband" fetching older messages_ * **Category** set to _client_ --- Bug imported by chaz@yorba.org 2013-11-21 20:20 UTC --- This bug was previously known as _bug_ 4912 at http://redmine.yorba.org/show_bug.cgi?id=4912 Unknown version " in product geary. Setting version to "!unspecified". Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
*** This bug has been marked as a duplicate of bug 795181 ***