Better "content is loading" view #749
Labels
No labels
Blocked
Bug
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Idea
In progress
Invalid
Major feature set
Packaging
Question
Soon
UI/UX
Upstream
You're dreamin'
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nostr/gossip#749
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When the user access a section that has not been cached, he faces an empty page with a "load more" button for some seconds, and of course the button is useless in this context:
We should remove the button and add a message / soft animation:
While the loading is operative, any element on the top bar or other parts of the view should be hidden.
done
This spinner hides the ability to load more. UNTIL we load a COUNT, we might have a date range with ZERO notes and the spinner goes forever, never giving me the option to load the earlier batch of notes. So I have reverted this.
See this thread: nostr:nevent1qqs2kln497095rxvc5ecwl5rmf23kv2z6p067x5dk2ywtheu4amdacsprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hse8mwaf
Why didn't you just show the buttons instead of removing the whole spinner?
The button should appears after we are sure we have zero results.
Of course, as you stated on the mentioned thread, the ideal solution is to simply see the last notes of a feed/profile.
I didn't dig into it, I just wanted it to work. It is probably a better idea.
I reworked the commit so that the buttons show if the user has waited more than 5 seconds.
Since @mikedilger has made feed loading so fast now, I needed to create an empty list to test this behavior.
This is fine. Once I solve the problem of feedback as to whether anything is ever going to load or not (starting from all the relays involved giving EOSE) then we can change the 5 second thing to when we actually know. But for now 5 seconds is good enough.