",[2895,2896],{"name":2882,"color":2883},{"name":2897,"color":2898},"s: pending triage","dddddd",1680,"Tag important for context is removed","2023-02-08T21:56:12Z","https://github.com/elk-zone/elk/issues/1680",0.7363175,{"description":2905,"labels":2906,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"# What I expect to happen\r\nWhen writing a post, or responding to someone else's post, the text box is only populated with the users input.\r\n\r\n# What is happening\r\nWhen I write a post, or reply to someone else's post, after a few seconds of writing something the text box starts getting populated with new lines to the point of making the PWA unresponsive.\r\n\r\n# Platform details\r\nI am using elk as an \"installed\" PWA on Android 13 through MS Edge v110.0.1587.41 which should be the latest version.\r\n\r\n# Additional information\r\nHere I am attaching one screen recording of the issue happening after deleting the browser cookies. You will notice how the scroll bar appears and starts to reduce is size as if I it had lots of text, but the count of characters is still the same.\r\n\r\n~~I tried replicating this using Firefox but couldn't replicate it there.~~ This is also happening on Firefox.\r\n\r\nhttps://user-images.githubusercontent.com/11972724/219093635-45fdb61e-f229-4dfa-91aa-12c86dee5d9a.mp4\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n",[2907,2908],{"name":2882,"color":2883},{"name":2897,"color":2898},1755,"Post text box gets filled with new lines","2023-02-20T11:19:05Z","https://github.com/elk-zone/elk/issues/1755",0.74428445,{"description":2915,"labels":2916,"number":2922,"owner":2871,"repository":2872,"state":2873,"title":2923,"updated_at":2924,"url":2925,"score":2926},"Right now when I'm on the home feed and compose a new post and send it, I cannot visually see my own post. Nothing happens. This creates this insecure feeling \"did I send it or not?\". This is perhaps will be solved with the live feed feature that does not (yet?) exist on Elk, but in the meantime the post could just be appended to the first post on home feed on Publish, right? Just a suggestion.",[2917,2918,2921],{"name":2882,"color":2883},{"name":2919,"color":2920},"c: feature","2878FF",{"name":2897,"color":2898},1800,"UX: Show your own post after sending it","2023-02-19T12:10:06Z","https://github.com/elk-zone/elk/issues/1800",0.7467721,{"description":2928,"labels":2929,"number":2932,"owner":2871,"repository":2872,"state":2873,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### 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_",[2930,2931],{"name":2882,"color":2883},{"name":2897,"color":2898},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.7515434,{"description":2938,"labels":2939,"number":2942,"owner":2871,"repository":2872,"state":2873,"title":2943,"updated_at":2944,"url":2945,"score":2946},"Using elk I replied to a post that had been boosted by a friend, removed the original poster from my reply and mentioned the friend.\r\n\r\nIn elk, this mention isn't visible, whereas in the mastodon UI it is. It looks like a reply to the original post with no indication that I mentioned the friend.\r\n\r\nConcrete example:\r\nhttps://hachyderm.io/@ross/110310075165327904\r\nhttps://elk.zone/hachyderm.io/@ross/110310075165327904\r\n",[2940,2941],{"name":2882,"color":2883},{"name":2897,"color":2898},2059,"Doesn't show mentions in reply","2023-05-04T11:05:34Z","https://github.com/elk-zone/elk/issues/2059",0.75311816,{"description":2948,"labels":2949,"number":2952,"owner":2871,"repository":2872,"state":2873,"title":2953,"updated_at":2954,"url":2955,"score":2956},"Reply to a post just entering the username of the person whose attention you want to draw to the thread. You cannot. You have to add some spurious character/whitespace for bonus points before it is allowed. Super annoying non-feature/bug\r\n\r\nSteps.\r\n1. Find a post.\r\n2. Reply to it with just the a username\r\n\r\nWhat I expect to happen: Hit Reply \r\nWhat happens instead of that: doh! YOU CAN'T \r\n",[2950,2951],{"name":2882,"color":2883},{"name":2897,"color":2898},2357,"Reply just tagging someone ","2023-08-21T22:59:55Z","https://github.com/elk-zone/elk/issues/2357",0.75482374,{"description":2958,"labels":2959,"number":2962,"owner":2871,"repository":2872,"state":2873,"title":2963,"updated_at":2964,"url":2965,"score":2966},"Look this gif:\r\n\r\n",[2960,2961],{"name":2882,"color":2883},{"name":2897,"color":2898},2549,"Can't expand two new items in notifications page","2024-01-07T09:11:36Z","https://github.com/elk-zone/elk/issues/2549",0.7572737,{"description":2968,"labels":2969,"number":2970,"owner":2871,"repository":2872,"state":2873,"title":2971,"updated_at":2972,"url":2973,"score":2974},"You're currently reusing the same color (border base) for all of the following:\r\n\r\n1. vertical lines connecting posts / replies (+ threads)\r\n2. horizontal separator lines between unrelated posts\r\n3. other UX elements\r\n\r\nThat super-subtle hue is probably appropriate for the latter two, but not the former. (Honestly, I can barely see it.) There should be a clear visual hierarchy which conveys that the connection threading posts together is stronger than those other UX elements. \r\n\r\nIf I'm reading https://github.com/elk-zone/elk/blob/main/components/status/StatusCard.vue correctly, then the simplest such fix would be to just `s/x base/x dark/` there. \r\n\r\n\r\n",[],1104,"Connected reply color is too subtle","2023-01-13T23:46:16Z","https://github.com/elk-zone/elk/issues/1104",0.7579737,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5RQ05R_DmIpnQ2M4oRF1r7kE6FdJiJ5TQyWETcXMcbo":-1},"/elk-zone/elk/742"]