-
Notifications
You must be signed in to change notification settings - Fork 19
bug: Allow pull down to refresh on mobile #27
Comments
I wonder what happens if this line gets removed
|
remove it lets test what happens |
It should be the default to allow pulling down! |
Any updates on this? It'd be pretty poggers to have... |
It got a fix in upstream and will most likely be released next release |
Amazing news, thanks @Mar0xy :3 |
Heyy, so I just wanted to let you know this implementation isn't very good imo... it only really works on the homepage, which isn't very useful because it already refreshes by default with websockets... I would prefer this to be implemented with the default browser pull down to refresh because it would allow for refresh of any page. There are lots of places where sharkey / misskey does not refresh correctly via webhooks, like when you're the one posting a reply from the post details view or when posting normally from the user profile view. The notification page also doesn't refresh correctly via webhooks, only the notification widget does. In order to avoid implementing a pull down to refresh for each specific component, and fixing webhooks everywhere, I think it's MUCH easier to just let the user pull down... |
This is not possible with how the client is made which is why misskey went with a custom option if you need it on every page then add the component on every page but here we are currently waiting to see what misskey themself does before doing anything else with the pull to refresh. |
Uh that sucks... Alright, thanks for trying at least >~< |
Summary
either as a toggle, or as a default action, pulling to refresh is a fast and effective way to refresh the page, if anything goes wrong.
The text was updated successfully, but these errors were encountered: