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

flickering page when number of transactions fluctuates #32

Open
MonsieurNicolas opened this issue Mar 2, 2018 · 2 comments
Open

flickering page when number of transactions fluctuates #32

MonsieurNicolas opened this issue Mar 2, 2018 · 2 comments

Comments

@MonsieurNicolas
Copy link
Contributor

The section "Recent operations: Live network" changes size based on the number of transactions, this causes the page to jump up/down based on the number of transactions in the previous ledger.

I would recommend picking a size (let's say 20 transactions) and have a fixed area for transactions (displaying empty space in that area if there are not enough transactions).

@bartekn
Copy link
Contributor

bartekn commented Mar 2, 2018

It's not about the number of transactions (we always display last 20). It's happening because summary of an operation sometimes takes 2 lines (instead of 1):

recent

We have another task to update the list of recent operation every 10-15 seconds instead of real-time as now. The flickering will still be there but won't be happening that often. We may also shorten long summaries.

@MonsieurNicolas
Copy link
Contributor Author

Yeah slowing the refresh rate doesn't seem to be the right fix... if anything I prefer it to move more. That said this is a policy choice.

All we need is to get a fixed width & height for that area, then the policy on what to display can be adjusted over time.... If we need the extra data, maybe a more horizontal format with scrolling may be more appropriate in the future

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

No branches or pull requests

2 participants