",[3045,3046],{"name":3032,"color":3033},{"name":3047,"color":3048},"s: pending triage","dddddd",3335,"Thread editor: no UI to delete last toot","2025-07-20T12:17:13Z","https://github.com/elk-zone/elk/issues/3335",0.80069876,{"description":3055,"labels":3056,"number":3059,"owner":3021,"repository":3022,"state":3023,"title":3060,"updated_at":3061,"url":3062,"score":3063},"Hi,\ncurrently there seems to be no way to switch from the Home timeline to Notifications and back without losing the current position in the Home timeline:\n\n1. scroll Home timeline to some position a few screens down\n2. click Notifications\n3. click Home\n4. Home timeline jumps to top, losing its last reading position\n\nThere is no \"Back\" arrow in Notifications to get back to the Home timeline without this behaviour, like it exists in other views reachable by navigating through postings. It looks like all top navigation entries will reset Home timeline position once coming back there.\n\nI guess it's needless to say that this is a nuisance :)\n\nAnyway, thx a lot for this great Mastodon client!\n",[3057,3058],{"name":3032,"color":3033},{"name":3047,"color":3048},3212,"UX: Home timeline position lost after coming back from Notifications (or any other top navigation entry)","2025-02-25T11:48:37Z","https://github.com/elk-zone/elk/issues/3212",0.80755484,{"description":3065,"labels":3066,"number":3069,"owner":3021,"repository":3022,"state":3023,"title":3070,"updated_at":3071,"url":3072,"score":3073},"To reproduce, on mobile (Android, latest stable release), compose a new toot, add images, see that footer cuts through the images when you scroll down.\r\n",[3067,3068],{"name":3032,"color":3033},{"name":3047,"color":3048},1912,"Footer cuts through when uploading lots of images","2023-03-20T12:42:38Z","https://github.com/elk-zone/elk/issues/1912",0.8095231,{"description":3075,"labels":3076,"number":3080,"owner":3021,"repository":3022,"state":3023,"title":3081,"updated_at":3082,"url":3083,"score":3084},"Hello, I would like to propose that:\r\n\r\n- One feed remains chronological, as it is now.\r\n- The other feed would be \"Smart\" and also display entries chronologically, but only show entries that we haven't seen yet. This means that if we have viewed a certain number of entries and then closed the app, when we reopen the Smart feed, it will display only the entries that we haven't seen yet.",[3077],{"name":3078,"color":3079},"c: feature","2878FF",2883,"Smart feed — It only shows unread entries","2024-06-14T05:05:27Z","https://github.com/elk-zone/elk/issues/2883",0.8101293,{"description":3086,"labels":3087,"number":3093,"owner":3021,"repository":3022,"state":3023,"title":3094,"updated_at":3095,"url":3096,"score":3097},"Right now, when I press the \"load XXX new items\" link, the new toots are loaded, so I am still located at the newest toot (at the top of the list). \r\nI would like to read through the toots without having to go down the list and then back up to load more. To do so, all Elk has to do is to load the new toots above the reference point where I currently am and I could then scroll up towards the top to read the toots and eventually get to the link to load more. \r\n\r\nThis could be an option in settings as others might have different usage patterns than mine. \r\n\r\nAlternatively the \"load more items\" link could be replaced with two arrows (up/down) to indicate if I want to load the items above or below my current reference point in the list. ",[3088,3089,3092],{"name":3032,"color":3033},{"name":3090,"color":3091},"good first issue","7057ff",{"name":3035,"color":3036},1818,"Make it an option to \"go to top or not\" when loading in new toots","2023-10-08T03:41:00Z","https://github.com/elk-zone/elk/issues/1818",0.81164896,{"description":3099,"labels":3100,"number":3103,"owner":3021,"repository":3022,"state":3023,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Pre-Checks\n\n- [X] Check that there isn't [already an issue](https://github.com/elk-zone/elk/issues) that reports the same bug to avoid creating a duplicate.\n- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/elk-zone/elk/discussions) or join our [Discord Chat Server](https://chat.elk.zone).\n- [X] Providing a screenshot or video to reproduce the issue or show visually what was meant.\n- [ ] I am willing to provide a PR.\n\n### Describe the bug\n\nI (too often) end up trying to scroll up on a thread (or want to \"pull to refresh\" on the thread) and end up triggering the default Chrome (I'm on Android 13) pull-to-refresh on the thread. This breaks any backward navigation and context (timeline position, etc).\r\n\r\nIt would be great if there was an \"app\" implemented pull-to-refresh that wouldn't break the above or something. Related, because there are no spinners or other progress indicators when opening a thread, I end up triggering the above more often, because I think I should be able to scroll to get to the root thread, but it hasn't loaded yet.\n\n### Reproduction video or screenshot\n\n_No response_\n\n### Additional Context\n\n_No response_",[3101,3102],{"name":3032,"color":3033},{"name":3047,"color":3048},1187,"PWA: Refreshing when on a thread breaks back nav and loses timeline position","2023-01-17T00:48:39Z","https://github.com/elk-zone/elk/issues/1187",0.81400704,{"description":3109,"labels":3110,"number":3112,"owner":3021,"repository":3022,"state":3023,"title":3113,"updated_at":3114,"url":3115,"score":3116},"It would be useful to see search history when using the search bar.\r\n\r\nFor reference, here's some screenshots:\r\n\r\n## Elk (mobile)\r\n\u003Cimg width=\"393\" alt=\"Screenshot 2022-12-29 at 14 49 44\" src=\"https://user-images.githubusercontent.com/15892272/209969964-52beeba2-1759-4731-998e-01cd96c18ce0.png\">\r\n\r\n## Elk (desktop)\r\n\u003Cimg width=\"302\" alt=\"Screenshot 2022-12-29 at 14 51 51\" src=\"https://user-images.githubusercontent.com/15892272/209970382-e323f655-1b0e-49a0-8137-93a1ada2a562.png\">\r\n\r\n## Twitter (mobile)\r\n\u003Cimg width=\"354\" alt=\"Screenshot 2022-12-29 at 14 51 25\" src=\"https://user-images.githubusercontent.com/15892272/209970142-bcf7decb-046b-4b6d-82c6-6030d219ea25.png\">\r\n\r\n## Twitter (desktop)\r\n\u003Cimg width=\"531\" alt=\"Screenshot 2022-12-29 at 14 51 04\" src=\"https://user-images.githubusercontent.com/15892272/209970107-51349baa-9af0-4ab2-93f8-639caf110ecf.png\">",[3111],{"name":3078,"color":3079},633,"Search History","2023-01-30T18:21:26Z","https://github.com/elk-zone/elk/issues/633",0.8146116,{"description":3118,"labels":3119,"number":3120,"owner":3021,"repository":3022,"state":3121,"title":3122,"updated_at":3123,"url":3124,"score":3125},"I'm pretty sure there was a back button at the top of the page for an individual toot? Just like on twitter? I don't recall having to use the browser's back button to go to the timeline",[],622,"closed","Back button gone?","2022-12-28T22:36:43Z","https://github.com/elk-zone/elk/issues/622",0.729181,["Reactive",3127],{},["Set"],["ShallowReactive",3130],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNa6FWrJoSK8ng8M1iItWS_L-_5Q-97znYVcyX84a_IU":-1},"/elk-zone/elk/566"]