Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontend let account render in offline #2847

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

thisconnect
Copy link
Collaborator

No description provided.

shonsirsha and others added 4 commits August 5, 2024 16:02
to improve consistency & aesthetics, we'd like to use our
revamped Message component for our Status component.

Please note that our Banner component uses Status. Therefore,
with this change, Banner will also use Message component.
Using our new ContentWrapper in order for components that are
using Status and were outside of the content view,
to look like they are in the view.

It's done to improve aesthetics.

Also, they will be scrolling with the content instead of
"sticking on top" like it used to be.
created the new component `GlobalBanners`, extracting it out
from `app.tsx`. We use this component in `account.tsx`,
`accountsummary.tsx`, and all of the settings pages.

The reason for this is because we'd like to move them out of
`app.tsx` so they're in the document flow of the page instead of
living separately in `app.tsx` (visually placed above the page
view).
This would fix the flickering when changing accounts and could
allow the user to get a receive address in offline mode.

Unfortunatelly there are multiple issues with this:
- offline error only showing once
- receive probably does not know which address range to use and
  could lead to unwanted address-reuse
- backend seems to not play along well in offline mode but somewhat
  works

If we go this way we could add various skeletons to the account
view so that it is clear which elements are still loading.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants